Environment tour

Three Odoo environments, each with a clear job.

The console keeps the configured branch, observed health and deployed image identity together, while treating development, staging and live as distinct operational contexts.

01

Development is the feedback loop

A push to the configured development branch can produce a private exact-commit build and deploy the verified digest to the development environment. Core cron and mail use conservative non-production defaults.

  • One configured development branch
  • Separate database and filestore
  • Customer-addon side effects still require review
02

Staging is the review room

Staging is a separately routed environment for customer review and integration checks away from live. The accepted model protects it with its own data boundary and Basic Auth.

  • One configured staging branch
  • Distinct database, filestore and domain
  • No claim of unlimited preview environments
03

Live is the customer-facing record

Later live updates pass the existing guarded path: pre-health, matched database-plus-filestore backup, isolated clone migration and smoke checks, cleanup, exact digest promotion and post-health.

  • Failed candidate stops before promotion
  • Clone testing reduces but does not eliminate concurrency risk
  • Current state remains evidence-driven