Skip to Content
This question has been flagged
2 Respostes
8399 Vistes
Avatar
Jean-Michel Laliberté

Hello,

We have a partner helping us to implement Odoo in our company.


We are using Enterprise modules, and we are also using Odoo.sh. We have access to the Odoo.sh panel (but we have a limited access since we are not partners but clients).

We would like to do some custom development to our Odoo installation on our side (development that would be done by us, and not by our partner). Our partner agrees with this. However, we don't know how to properly replicate our production environment on a local installation.

We asked our partner, but they weren't able to answer our question.


We know we can download the Enterprise code with a proper subscription code (which we did). It works for the enterprise code, but it still doesn't replicate all the production environment, since other modules installed on the production environment cannot be downloaded this way. Building a functional local environment this way quickly becomes a fastidious operation.


Therefore, I would like to know what are the good practices to develop and test our developments on a local environment.


Thank you,

Avatar
Descartar
Avatar
Tariq Ahmed Khan
Best Answer

you need to have a GitHub account to upload your addon/changes to your odoo.sh instance.
as you say you have a partner who deployed that for you, ask them to add your GitHub profile to the project repo or ask for that GitHub account access (you are legally the owner of that GitHub account as you are the customer).

secondly, to setup up local instance, you need
1. odoo community codebase
2. odoo enterprise codebase
3. your custom addon codebase
[all those you can clone from github]

then in odoo.conf add those addon absolute path in [addons_path =]

now, after running up the project, you can create a new DB or restore the current DB from odoo.sh
to restore ask for the master password of your instance from your partner, then take a backup of your odoo instance.

{URL}/web/database/manager 

before this step please remember to enable DB listing in odoo.sh.

After restoring you are good to test & develop locally, remember for odoo enterprises you will have 30 days for local testing for each DB. Do not use your enterprise code in local DB because you can only run 1 instance under 1 subscription.

You can check odoo deployment guidelines to set up instances locally.

Avatar
Descartar
Nazim

Hi Tariq,

Your answer here is very helpful. However, I am confused a bit with your last note.

"Do not use your enterprise code in local DB because you can only run 1 instance under 1 subscription"... what does this mean specifically?

As in, after downloading the production db from odoo.com, and when I load it on to my local server, isn't it exactly that we would be doing. Running enterprise code? (cos I have enterprise repo clone on my addons path).

Thanks in anticipation.

Avatar
Jean-Michel Laliberté
Autor Best Answer

Hello Tariq,

Thank you for your detailed answer. I don't have 5 Karma so I can't upvote your answer (and can't comment it as well), but it was the correct answer that helped me.

Thank you,

Avatar
Descartar