Upgrade 4.7 to latest, Self Hosted

I have…

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [ ] Bug report
  • [ ] Performance issue
  • [ x ] Documentation issue or request

Current behavior

More of a request on what steps to take to upgrade from 4.7.0 to latest

Expected behavior

Upgrade to the latest major version.
Steps to take to have a seamless upgrade/update

Minimal reproduction of the problem

Have a version 4.7.0 instance of mongoDB with assets and multiple apps.
Upgrade to latest major version

Environment

App Name: Webportal

  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ x ] Self hosted with other version
  • [ ] Cloud version

Version: 4.7.0

Browser:

  • [ x ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ x ] Firefox
  • [ x ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others:

  • [ x ] Some custom colours added also running on another port.
  • [ x ] Backup Squidex, Content & the assets folder.
  • [ x ] Rebuild options all set to true

Like to update to the latest version with minimal impact
Would we need incrementally upgrade to major versions example: 4.7.0 -> 5.x -> 6.x -> 7.x -> latest
Or can we upgrade to the latest version ?
appsettings.json

"rebuild": {
    "apps": true,
    "assets": true,
    "contents": true,
    "rules": true,
    "schemas": true,
    "indexes": true
  }

Am I missing something ?

  • [ x ] Some custom colours added also running on another port.

I have no idea what you mean with colors. The port does not matter.

In general:

  1. Do not change any of these rebuild settings. There are only needed if your data becomes corrupt in some way.
  2. Make a backup of the mongo database before the migration.
  3. Just update to the latest version. It is described here: https://docs.squidex.io/02-documentation/concepts/migrations#migration-steps
1 Like