Deploy, start, stop and restart
All of these are at the top of the environment’s page: the Deploy button and the More menu next to it.
Deploy
Section titled “Deploy”Press Deploy. A task drawer opens with the live log. A deploy:
- fetches the code of the environment’s branch, the addon repositories and the uploaded modules on the server;
- writes the environment’s files (
docker-compose.yml,odoo.conf); - creates the database, the first time only;
- starts Odoo;
- asks for Odoo’s login page through the server’s proxy. When it answers, the deploy is done.
Afterwards the Overview tab shows the commits that were deployed.
Changes made in Settings, Advanced or to the variables take effect at the next deploy.
Deploy and update modules
Section titled “Deploy and update modules”Odoo modules whose code changed need an update inside Odoo.
- Open More and choose Deploy and update modules….
- In Modules to update, enter
all, or module names separated by commas, for examplesale,stock. - Start the deploy.
Start, stop, restart
Section titled “Start, stop, restart”Open More and choose Start, Stop or Restart. Each runs as a task. They are greyed out until the environment was deployed once.
Sync status
Section titled “Sync status”More → Sync status reads what really runs on the server and corrects the status shown here. Use it if someone changed containers on the server by hand.
Who can do it
Section titled “Who can do it”Developers can deploy dev and staging environments. Production needs an admin or the owner. Viewers can only look.
Deploy without pressing a button
Section titled “Deploy without pressing a button”- On every push to the branch: Deploy on push.
- At set times: Scheduled actions.
- By asking Claude: Using Claude.

