Working with a Project

Everything you do to a running instance happens on the project screen. The name, current state and provisioning progress sit at the top — those you always want visible — and the rest is split across eight tabs.

Overview

The landing tab, and where the details you need to actually reach Odoo live:

Field	What it is
URL	Where Odoo is reachable
IP address	The machine's address
Odoo master password	Needed to create the database
Monitoring password	For the monitoring endpoints
GitHub repository	The repository this project is linked to

Domains are managed here too: point your own hostname at the project and TLS certificates are issued for it automatically.

If the project uses your own machine rather than a provisioned one, the setup steps for connecting it appear here.

Code & updates

Three things, in the order you normally need them:

• Source — which repository and which commit the instance is running.
• Branch — which branch is deployed, and switching between them.
• Updates — applying a new version of your code to the running instance, and the automatic update schedule if you have one enabled.

This is the tab you return to after pushing changes. Provisioning clones the repository once; getting later commits onto the machine is a deploy from here.

AI Developer

An assisted terminal session against the instance — for asking for a change in words rather than working out the commands yourself.

Machine

The operational view of the server itself:

• Backups — taking them, and restoring from them. What you get depends on the backup extras on the project; see Plans and Extras.
• Restore a backup — upload an Odoo backup and load it into this instance (see below).
• Logs — what the instance is doing, without opening an SSH session.
• State — the machine's current condition.

Restoring an Odoo backup

Moving from another Odoo, or bringing an old state back: under Machine → Backups → Restore a backup you upload a backup and it replaces the data of the selected instance — production or a staging instance, whichever is selected at the top of the page.

• Format: the .zip that Odoo's database manager or odoo.sh produces, with dump.sql and filestore/ inside. Before anything is changed, the machine checks the file (odoo restore show-dump-type must report odoosh); a bare .dump or .sql is turned away and the instance stays as it was.
• Size: up to 1 GB per upload — the limit of our router in front of cloud.zebroo.de.
• What happens: the database of the instance is deleted and rebuilt from dump.sql, the files from filestore/ are copied in, then the instance starts again. If the restore fails halfway, the old database is already gone — restore the backup you took beforehand. Files that were only on the machine stay on disk but no longer belong to any record. The result appears in the update history.
• Confirmation: a red warning, a checkbox, and the machine name typed out. The server checks the name again against the selected instance.
• Who: project admins only (the same right as writing SQL).
• Staging in development mode: if the instance runs with zodoo's DEVMODE, zodoo also applies its development scripts after the restore (outgoing mail and cron jobs off, passwords reset) — as it does for every restore there.

caution

Restoring cannot be undone. Take a backup first with Back up now — it is the only way back.

Console

Direct access, for when the panels above are not enough:

• Code — browse and edit the source on the machine.
• SQL console — run queries against the Odoo database.
• Terminal — a shell on the server.
• Instance actions — start, stop and restart the instance.

caution

The SQL console writes directly to the production database, with no undo. Take a backup from the Machine tab before running anything that changes data.

Staging

A second instance alongside production, for trying changes before they reach live. From here you can create it, point it at a branch, and reset it back to a copy of production.

Staging is an extra on most sizes and included on larger ones — see Plans and Extras.

Team & settings

Who can reach the project, project-level settings, and the route to support when something needs a human.

Internals

Diagnostics about the project's own plumbing. Useful when something is wrong with the platform rather than with your Odoo — and the first thing to screenshot when you contact support.

Deleting a project

Deleting a project destroys the server and everything on it, and stops the billing. Take a backup first if anything on the machine still matters — the volumes go with it.