Odoo Configurations (docker)

Sub-Domain or Exposing Port for Odoo

Odoo cannot be routed through proxy on the same domain as other Bahmni services. So either it can be accessed directly on port 8069 or through a sub-domain mapping to the same public IP address as Bahmni. The index page of Bahmni detects the URL by which you access the server and if it an IP or localhost, the redirection happens to http://<ip/localhost>:8069 and if it is a FQDN, the redirection happens to erp-<your-fqdn>. The prefix erp is a configuration and it can be configured from here. Based on the prefix, you can create a A record that maps the domain to the server IP address in your DNS provider. For a production system accessed over internet it is recommended to setup the domain based routing and add an SSL certificate.

One Time Setup for Odoo 16:

As Bahmni Standard ships with metadata configured and the data being synced with sub-systems, Odoo DB by default boots up with a database backup image. In some hosts Odoo 16 might fail to start throwing a permission denied error . Run the following command the first time.

docker compose exec -it --user root odoo chown -R odoo:odoo /var/lib/odoo/filestore && docker compose restart odoo

Setting up Odoo 10:

Bahmni releases on docker will ship with Odoo 16 as the default version as part of bahmni-standard profile. Odoo 10 is out of support from the Odoo community, so it is expected that the support for bug fixes or security patches will be very limited. It is recommended to migrate to Odoo 16. You can read more the Odoo upgrade initiative from here.

If you would want to run Odoo 10 along with bahmni custom modules and integration, it is possible to start it up with a custom profile which can be enabled from .env files.

• In bahmni-docker/bahmni-standard repository, you will find that there are three services odoo-10, odoo-10-db, odoo-10-connect tagged with profile odoo-10.

• You can start these services by adding the odoo-10 profile to the COMPOSE_PROFILES variables in the .env file.

• The profile can also be passed from the command line using the --profiles option docker compose --profile odoo-10 up -d

• Note: Odoo 10 by default starts up on port 8070. If you want to still run it on 8069, you can update the port mapping for the odoo-10 service in docker-compose.yml

One-time Setup for Odoo 10

The below steps needs to be performed only once when Odoo is created and is applicable only if you are running Odoo 10

1. Once the container spins up, login to the application.

2. Navigate to Apps from the menu bar.

3. Click on Bahmni Account app and then click on Upgrade.

4. Wait for the upgrade to complete and you will redirected to home page.

5. After redirection, refresh your page once.

Now Odoo should be working fine. If you don't see old patient data coming into Odoo in 10 mins, please read Odoo not synchronizing old patient data.

Environment Configurations

Odoo Variables

Note: The same set of above variables are available for configuring Odoo 10 as well. Those variables are prefixed with ODOO_10 instead of ODOO.

Odoo Connect Configurations

Odoo not synchronizing old patient data

Perform the followinng steps if older patient data is not being sent to Odoo. This likely happened because the ATOM Feed reader has already exhausted its max retry limit for failed events (by default set to 5 times). You can set the Failed events retry back to 1, and that should sync them immediately. Steps to fix this:

1. Open terminal in your local machine, in bahmni-docker folder.

2. Execute docker ps to see the list of running containers.

3. Connect to the Odoo postgres DB container by executing the command: docker container exec -it bahmni-docker_odoodb_1 /bin/bash where bahmni-docker_odoodb_1 is the name of the odoo postgres container. You should now be within the container.

4. Connect to the postgres console using command: psql -Uodoo odoo. For more info on how to connect to Bahmni Databases, refer to this wiki page: Connecting to various databases.

5. In the psql prompt type: select count(*) from failed_events; This will show you the number of failed events.

6. If 1 or more events are there, then you can fire the query: select id,retries from failed_events;. You should see all failed events have reached their retry limit.

7. Fire an update statement to reset the retry count for all failed events: update failed_events set retries=1;

8. Now in about a minute, all failed events should be processed and old patient data should get synced to Odoo.

9. To exit the container, first type \q to exit postgres shell, and then type exit to exit bash shell without stopping the postgres container.

Loading Additional Addons to Odoo

When you want to load additional addons to Odoo instance, you can set the EXTRA_ADDONS_PATH with the directory that contains your modules.

1. Bring down Odoo if it is already running by doing docker-compose down .

2. Set the path of your root directory of modules to EXTRA_ADDONS_PATH variable.

3. Restart Odoo instance by running docker-compose up

4. Login to the application

5. Navigate to Settings page in the web and enable Developer Mode

6. Navigate to Apps page and Click on Update Apps List

7. Your new module will be listed and you can install it.

Note: If you want to add additional addons for Odoo 10, update value for EXTRA_ODOO_10_ADDONS_PATH in the .env files

Development setup for Bahmni Odoo Modules

Note: Do these steps only if you need to development setup and update Bahmni Odoo modules.

1. Clone the Bahmni/bahmni-odoo-modules repo at https://github.com/Bahmni/bahmni-odoo-modules

2. Bring Bahmni down by running docker-compose down -v from bahmni-docker/bahmni-standard directory.

3. Update the BAHMNI_ODOO_MODULES_PATH variable in .env file with the cloned directory path. Also update COMPOSE_PROFILE=odoo so that only odoo services start.

4. Now in docker-compose.yml uncomment the volume commented under odoo service.

5. Start Odoo services by running docker-compose up

6. Enable developer mode in Odoo by navigating to Settings page in Odoo Web and click Activate the Developer Mode

7. After you perform a change, do the following steps to reflect the changes.

8. Run docker-compose restart odoo (if using odoo 16) or docker compose restart odoo-10 (if using odoo-10)

9. Now in the browser navigate to Apps menu. Click on the app that is updated and click Upgrade.

10. Now you should see the changes reflected. If not try from Step 8 & 9 once again.

Note: The development setup can be done by following the same steps except that the bahmni/odoo-modules needs to be cloned and its path to be updated in BAHMNI_ODOO_10_MODULES_PATH variable