Updating Strawly

Strawly updates are distributed as new Docker images. You do not need to modify any source code to update — just pull the latest images and restart.

Standard update

Pull the latest images for all enabled services and restart:

docker compose -f docker-compose.generated.yml pull
docker compose -f docker-compose.generated.yml up -d

Docker Compose only recreates containers whose image has changed, so unchanged services stay running.

Check current image versions

docker compose -f docker-compose.generated.yml images

Update a specific service

To pull and restart only one service:

docker compose -f docker-compose.generated.yml pull backend
docker compose -f docker-compose.generated.yml up -d backend

After a deployment config change

If a new version of Strawly introduces changes to strawly-deployment.yml or the deployment scripts, also pull the latest deployment repository:

git pull
npm install
npm run generate-compose
docker compose -f docker-compose.generated.yml pull
docker compose -f docker-compose.generated.yml up -d

Rollback

To roll back to a previous image version, update the image tag in strawly-deployment.yml:

modules:
  optimizations-azure:
    image: codeberg.org/${CODEBERG_USERNAME}/strawly-optimizations-azure:v1.0.0

Then regenerate and redeploy:

npm run generate-compose
docker compose -f docker-compose.generated.yml up -d

Database migrations

Migrations run automatically via the migrations container that starts before the backend on every deployment. You do not need to run migrations manually. If a migration fails, the backend will not start — check the logs:

docker compose -f docker-compose.generated.yml logs migrations