Skip to main content

Upgrading Daployi

This guide explains how to upgrade Daployi components safely.

If you used the install utility to install daployi, you can upgrade using the same command. Make sure to run it from the same directory as it stores configurations.

please see here for running the installer command

Check current versions

docker ps --format 'table {{.Names}}\t{{.Image}}'

Upgrade with Docker Compose

  1. Review release notes and update image tags in docker-compose.yml:
    • daployi/daployi-api:VERSION
    • daployi/daployi-worker:VERSION
    • daployi/daployi-web:VERSION
  2. Pull updated images:
docker compose pull
  1. Restart services with minimal downtime:
docker compose up -d
  1. Verify:
docker compose ps
docker logs --tail=200 daployi-server
# Then open the Web UI in your browser.

Upgrade with Standard Docker

  • Pull new images:
docker pull daployi/daployi-api:VERSION
docker pull daployi/daployi-worker:VERSION
docker pull daployi/daployi-web:VERSION
  • Restart container(s):
docker rm -f daployi-server && docker run ... # same args as before
  • Consider using a script or saved compose file to avoid losing flags.

MongoDB and Redis persistence

  • Data is stored in named volumes (mongodb_data, redis_data). Upgrades should not remove volumes.
  • Always verify backups before upgrading production.

Rolling back

  • Revert tags in docker-compose.yml to previous versions and rerun docker compose up -d
  • With docker run, re-create containers with previous tags.

Best practices

  • Test upgrades in a staging environment first.
  • Pin exact versions in production; avoid :latest.
  • Keep a changelog of environment changes required by new versions.