Community mailing list archives

Re: Can I use Odoo to build a SaaS business apps? Can Odoo support multiple subdomains?

- 04/26/2016 07:56:09
I have to agree with Dominique here (and I think most people here will consider this as obvious), you never install two version of the same module on the same instance just to have two different version on two different database.

If you want to have two database on one instance, you want the code base to be the same for the two database. If you upgrade the code, you upgrade it for all databases linked to it. If you want a different version for a specific database, you create another instance.

Also renaming the module is a very bad idea. When you git pull a module from Github, an OCA repo for example, you don't want to make any change so you can easily git pull it in the future. If you change the name it means you fork it and it'll be more difficult to maintain. Not even mentioning the fact that changing the name of the module may and will create dependencies problem, bugs, etc... This is not an option.

Yannick Buron
+33 (0) 6 70 74 52 26 |
My blog :

Building the tools we need
98 Avenue du general pierre billotte BatD
94000 Creteil |
Le 26/04/2016 12:18, James Fox a écrit :


so why can't you simply rename the module as module(customised) install module on db1 and module(customised) on db2 - they will not conflict.


Alfa Industrial Components
Litton House, 
Tel 03333 441658   Fax 03333 441659

2016-04-26 11:30 GMT+02:00 James Fox <>:
> Dominique,
> when running multiple databases on a single odoo instance there is no
> requirement for all databases to use the same modules. Each database can
> have whatever modules they like, installed or uninstalled, and even
> datamodules can be installed that have never ever been anywhere near the
> server's file system or github.

you cannot have 2 different versions of a module,
a module specific to a customer is installable on other databases
if a module is broken, all databases are stopped,

By "different modules", I mean tailored modules directory.

> James Fox
> ====================
> Alfa Industrial Components
> Litton House,
> Tel 03333 441658   Fax 03333 441659
> ====================
> 2016-04-26 9:33 GMT+02:00 Ermin Trevisan <>:
>> Dominique
>>> This is not enough in your case. To use different modules for
>>> different customers you need multi-tenant, as already said.
>>> For other reasons, you'd rather not run several databases on a single
>>> service in production.
>> I remember reading a post of yours explaining your approach.
>> I do agree that this is not the optimum concerning separation of
>> customers.
>> If I remember it correctly, you do offer separate instances with
>> separate databases. But in this case, what does multi-tenancy mean, even
>> if you are using virtual servers?
> The point here is the requirement for different modules. If you put
> several databases on a single service, all databases use the same
> modules. So my answer.
> Now from a generic stand-point, the more separate Odoo services are,
> the more secure/stable it is.
> Some very demanding instances of mines, run a single database on a
> single service on a single virtual server on the customer's dedicated
> physical server.
> On the other end of the range, like, many customers
> use many databases on many services on many virtual servers on many
> dedicated servers.
> For education, evaluation, test, replay backups, it's OK. For
> production, users are invited (but not forced) to use separate
> services if they need several databases.
> Multi-tenant, aka multi-service, consists in running several Odoo
> services on the same server. For instance, a basic virtual server from
> SISalp runs three different copies of Odoo called production, taining
> and test. Multi-tenancy is a compromise to manage internal training
> and updates, but can also be used to save resources for a large number
> of services. For example, French University Mooc about ERPs in
> november 2015 needed 7000+ simulations for 7000+ students. System was
> designed for 10000 capacity, based on 25 virtual servers running 225
> Odoo services with 32 databases each.
> In SISalp's multi-tenant solution, every service must be isolated in
> its own system user, its own home directory and its own postgresql
> role. Critical files cannot be read from other users.
> If you wish to see it in action for a full virtual server running
> several services, all different and independent, you can check
> and connect with "admin"
> password "admin"
> This dashboard manages our demo center. You can try and click
> everywhere and break everything here ;-).
> If you are interested by a single service view (for example Odoo
> version 8.0 demo service), connect with "version80" password "admin"
> Clouder achieves similar functions but isolates services in Docker
> instances whose management is centralized at clouder level, while, at
> SISalp, every virtual server is an independent administration unit
> managed locally. The aim of SISalp's hosting is to be able to delegate
> administration of each virtual server to the user or his local service
> provider. I think it is the main point that differentiates the two
> approaches, more than old-school/new-school technology.
> _______________________________________________
> Mailing-List:
> Post to:
> Unsubscribe:
> _______________________________________________
> Mailing-List:
> Post to:
> Unsubscribe:

Dominique Chabord - SISalp
Logiciel libre pour l'entreprise Tryton et open-source Odoo, OpenERP
18 avenue Beauregard 74960 Cran Gevrier
145A rue Alexandre Borrely 83000 Toulon
tel(repondeur) +33(0)950274960 fax +33(0)955274960 mob +33(0)622616438

Post to:

Post to: