Upgrade

1. Back up before upgrading

Create a stopped full backup from the existing asp-compose/ deployment directory:

./scripts/backup.sh

2. Download and overlay the latest release

First installation and upgrades use the same release package. The following commands return to the parent directory, download the latest release, and overlay the official files in the existing asp-compose/ directory:

cd ..
curl -fL -o asp-compose.tar.gz https://github.com/FunnyWolf/agentic-soc-platform/releases/latest/download/asp-compose.tar.gz &&
tar -xzf asp-compose.tar.gz &&
rm asp-compose.tar.gz &&
cd asp-compose &&
./scripts/upgrade.sh

After extraction, the upgrade.sh from the latest release package is executed.

3. Upgrade script

The upgrade script:

1. Updates the existing .env with images from the new package's .env.example.
2. Validates the Compose configuration, pulls images, and stops the current application services.
3. Runs target-release upgrade operations and Django database migrations.
4. Starts services and runs doctor.sh.

Except for updating ASP_BACKEND_IMAGE and ASP_FRONTEND_IMAGE, the upgrade preserves the other settings in .env, along with compose.override.yaml, custom/, certs/, logs/, and Docker named volumes.

4. Upgrade failures

The upgrade script does not roll back automatically. Use the command output to identify the failed stage, then see Restart & Operations for service status and logs.

Use the backup created before upgrading when a full restore is required.

Next Steps

• Restart & Operations — Check service status and logs.