I am managing several databases with a same Odoo instance. It is desirable to me, to have available an addons_path item, to one database, but not to the others. For example:
addons_path = /opt/odoo/old-addons,/opt/odoo/odoo/addons [...]
so that old-addons are only visible to one database but not to others. Is there a way to do this?
Right now the way to do that is creating multiple Odoo instances with different config files that hold different addons_path options. I know that Odoo will release in a few months a tool or something to be able to manage different addons_path using only one instance or at least that's what I understand from a chat with Fabien. If not I will build my solution for that but right now you need to create several instances to have different addons_path. A few good practices for that:
- Keep the code for each database only for that database, if you use git you could clone the git repo for every database to be sure that an update in one database doesn't corrupt the others
- Use the dbfilter option to match, show and manage only the database of the instance or create a PostgreSQL user for each Odoo instance if you don't wanna see all the other database in the Odoo instance
- If you are using Odoo 8 or 9 you need to configure the longpooling port different for every database.
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 2/11/16, 7:06 AM|
|Seen: 383 times|
|Last updated: 2/11/16, 3:00 PM|