- Mailing Lists
- Contributors
- Re: Multi Tenant Self Hosted Enviroments
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: Multi Tenant Self Hosted Enviroments
Sorry for the extra noise, but I should have looked at the cloudpepper solution a little closer before responding. CPs approach is to manage multiple server instances on disparate cloud providers, I am looking to consolidate the functionality to a single cluster of servers and not deploy a unique server per client. I could do a lot of the same type of functionality by making use of Terraform providers and ansible or alternatively make use of multiple Docker containers, but a lot of the core functionality that I am looking for already exists within Odoo. I'm just trying to find out if somebody else has already harnessed it to perform multiple tenant deployments within the same Odoo instance. Thank you, Charles On Sat, May 20, 2023 at 2:21 PM Charles Gucker <cgucker@onestep.net> wrote: > > Let me respond inline. > > On Sat, May 20, 2023 at 2:02 PM Sven from Cloudpepper > <notifications@odoo-community.org> wrote: > > > > Hi Charles, > > > > > > Perhaps you can give our services a try? > > You can host as many Odoo instances (Community and Enterprise) on a server as you want, all automated. > > Also gives you test environments, GitHub deployment and automated backups. > > It also has the OCA marketplace built-in, so you can easily activate any OCA module on an instance. > > Yes, this is in short what I want to be able to provide to my clients, > but directly as in self-hosted. Glad to see that somebody has done > it. > > > We can also give clients access to your own branded dashboard so they can see and manage their instances (ie. see the logs, restart, create a backup, etc.) > > Would love to better understand the approach your company took to > achieve the multi-tenant design of Odoo. Just to be clear, I would > not be making any offers to the general public, unless tied to a brick > and mortar offering. > > Charles
by cgucker - 08:35 - 20 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