Skip to content

Migrating from odoo.sh

Production moves from odoo.sh to an Odizy Production Server. The repository does not change: GitHub stays its home, and Odizy builds it as it is.

Before the move

Run Odizy beside odoo.sh first, as in Keeping Production on odoo.sh: Test Servers per branch, and a Staging Server restored from production. Rehearse the move on that Staging Server until it passes:

  • the backup loads;
  • the application starts and its upgrade log is clean;
  • your users validate it.

The move

  1. Create the Production Server: Muppy › Applications › Operations › Create App Server, on the Application Definition, with a production qualifier. For High Availability, add a standby; see High Availability Packs.
  1. Stop writes on odoo.sh, so that the last backup is the last state of production.
  2. Retrieve that backup with the script Muppy support provides, and load it on the Production Server, as on staging. Do not neutralize this one: it is production.
  3. Deploy the Production Server: Upgrade / Deploy, on the ref odoo.sh was running. See Deploying Staging and Production.
  4. Point your domain at the Production Server. See Custom Domains.

After the move

  • Schedule the backups of the production database. See Scheduled Backups.
  • Production is deployed by hand from now on. Each deployment backs the database up before upgrading it, and its record keeps the git indexes and the downtime.