servd

Follow Craft's upgrade guide to get everything upgraded and working on your local machine.

Commit and push all code and project config changes made as part of the upgrade to your git repository.

If you've had to increase your local PHP version during the upgrade, tweak the PHP version of your project in Servd. Note: this won't change the PHP version of your existing bundles, or immediately update the PHP version running in any of your environments. It just changes the version that's used for new bundles.

Create a bundle from your commit.

Check your post-deploy tasks contain the "./craft migrate/all --interactive=0" and "./craft project-config/sync --interactive=0" craft commands.

If they don't, either add them, or manually run the commands via SSH or the dashboard once the bundle is synced.

Once built, select and sync the new bundle to your staging or development environment.

Give your staging/development environment a thorough test to make sure it's working as you expect.

Select and sync the bundle to your production environment.

Give your production environment a test.

You're now running on Craft 4! 🎉

Go to your staging's Import page and clone production's assets, currently deployed bundle and database.

Once complete, create a bundle containing all your Craft 4 changes.

Deploy the upgraded bundle to staging.

Once it is deployed and post-deploy tasks have completed, perform any manual modifications to the data in the staging database as required.

Go to your production Import page and trigger an import into production from staging that includes the database and deployed bundle. If any assets have changes or new environment variables have been introduced, you may want to enable those options as well.

It's a good idea to enable Atomic Database Imports for this step, as we've found Craft 3 sometimes tries to populate plugin data into the database if it discovers that the table is empty. This can result in the correct Craft 4 plugin info not being populated correctly during the upgrade process.