Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Re: Multi Tenant Self Hosted Enviroments

Archives

Contributors

Re: Multi Tenant Self Hosted Enviroments

Re: Multi Tenant Self Hosted Enviroments

Re: Multi Tenant Self Hosted Enviroments 

In case Cloudpepper is not what you want, Ivan Yelizariev has made a 
package to help multi tenant Odoo hosting (see its modules on 
apps.odoo.com). There is also some bash scripts from the french provider 
Sisalp that you can download from http://download.sisalp.net/scripts/. 
You might also use the Yunohost solution, there is a good Odoo package 
(any version).

But beware, self-hosting require work. While it's easy for personal 
projects, it require a lot of time when it comes professional. I ran a 
hosting company in the 90's, I know what I am talking about. I didn't 
knew about Cloudpepper, but it looks very good.


---
Librement,
Xavier Brochard xavier@alternatif.org
La liberté est à l'homme ce que les ailes sont à l'oiseau
(Jean-Pierre Rosnay)

Le 20.05.2023 19:47, Charles Gucker a écrit :

> Greetings,

> I have been struggling to set up a multi-tenant, self hosted

> Odoo environment.  The purpose of multi-tenant in my deployment, I am

> referring to having multiple clients, who will each want to "own" and

> manage their instance / database of Odoo.  That is, being able to set

> up multiple websites, shops, with consolidated invoicing and services

> already provided by Odoo.

> I understand that I can set up separate VMs which would each

> point to a specific database.  But it would require additional

> resources to deploy each VM to maintain the OS instances required.

> As a result, I am looking to consolidate the deployments as much as

> possible.  This way I can configure clients and then break them out

> if/when it's needed.

> I am running Odoo 16, self hosted.  I started to go down the

> path to try and force clients to use their specific domain name, but

> that became an issue because dbfilter can associate between a fully

> qualified hostname, or just the hostname itself.  It wasn't built to

> go the other direction.  Then I ran into the problem of a client

> needing to use multiple domains and how to associate them to their

> respective databases.  I tried to do much of this logic within nginx,

> but even then I ran into problems with modifying HTTP headers and then

> losing the desired outcome.

> Does anybody know if I'm missing something, or would I really

> have to kickoff an Odoo instance for each client with their own

> distributed TLS/SSL cert, DB and front-end server ?  I would really

> like to find a solution that would scale and I know a lot of people

> have made it scale. I'm just missing some pieces to do the same.

> Thank you,

> Charles

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [1]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]

> 

> 

> 

> [1] https://odoo-community.org/groups/contributors-15

> [2] https://odoo-community.org/groups?unsubscribe
by xavier - 06:20 - 21 May 2023

Reference

  • Multi Tenant Self Hosted Enviroments 
    Greetings,

      I have been struggling to set up a multi-tenant, self hosted
Odoo environment.   The purpose of multi-tenant in my deployment, I am
referring to having multiple clients, who will each want to "own" and
manage their instance / database of Odoo.   That is, being able to set
up multiple websites, shops, with consolidated invoicing and services
already provided by Odoo.

      I understand that I can set up separate VMs which would each
point to a specific database.   But it would require additional
resources to deploy each VM to maintain the OS instances required.
As a result, I am looking to consolidate the deployments as much as
possible.   This way I can configure clients and then break them out
if/when it's needed.

     I am running Odoo 16, self hosted.   I started to go down the
path to try and force clients to use their specific domain name, but
that became an issue because dbfilter can associate between a fully
qualified hostname, or just the hostname itself.   It wasn't built to
go the other direction.   Then I ran into the problem of a client
needing to use multiple domains and how to associate them to their
respective databases.   I tried to do much of this logic within nginx,
but even then I ran into problems with modifying HTTP headers and then
losing the desired outcome.

     Does anybody know if I'm missing something, or would I really
have to kickoff an Odoo instance for each client with their own
distributed TLS/SSL cert, DB and front-end server ?   I would really
like to find a solution that would scale and I know a lot of people
have made it scale.  I'm just missing some pieces to do the same.

Thank you,
Charles
    by cgucker - 07:46 - 20 May 2023