Upgrade

This page describes how to update a PteroCloud installation safely. It documents the process, not a promise that any particular release exists.

Before you update

1. Take a database backup.
2. Save the pre-update reports:

php artisan pterocloud:diagnose --json > pre-update-diagnostics.json
php artisan pterocloud:compatibility --json > pre-update-compatibility.json

1. Confirm the target version's compatibility status. A component reported UNTESTED or UNSUPPORTED should be resolved before upgrading.

Apply the update

1. Replace the extension files with the new release.
2. Run migrations (never migrate:fresh on a live install):

php artisan migrate

1. Clear caches:

php artisan config:clear && php artisan cache:clear && php artisan view:clear

1. Rebuild the frontend assets if the release includes them:

yarn install --frozen-lockfile && yarn build:production

1. Re-run verification:

php artisan pterocloud:verify
php artisan pterocloud:health
php artisan pterocloud:compatibility

Version drift

Diagnostics compare the extension version, the compiled frontend version and (when pinned) the Blueprint version. A mismatch is reported as a warning or error with a documentation link; it never silently proceeds. See PC-SYS-### codes in the error reference.

Rollback

There is no automated rollback of a schema migration. Restore the database backup taken before the update and reinstall the previous extension files.

Migrations are one-way

Never run migrate:fresh or migrate:rollback on a live installation. Restore the backup instead.

Related

• Repair
• Troubleshooting: updates