Upgrade

Upgrades come in two kinds: shipping your own changes, and moving to a new platform version.

Ship your own changes

When you change code that touches installed apps, update those apps on each workspace database so the changes apply. Always back up first (Back up & restore), then update the affected apps per database.

New apps you've added to the codebase are installed where their dependencies are met; existing apps are updated in place. A safe routine:

  1. Back up every workspace database.
  2. Deploy the new code.
  3. Update apps per database.
  4. Health-check a workspace.

Move to a new platform version

A major version bump can change data structures. Test it on a copy first:

  1. Restore a recent backup into a staging environment.
  2. Run the upgrade there.
  3. Verify your workspaces and custom apps.
  4. Only then upgrade production, with a fresh backup in hand.

Never upgrade production without a tested backup

Restore-and-test on staging is the difference between a routine upgrade and a bad day.

← Domain names Command-line reference →

Need a hand with this? company@everjust.co — a human answers.