Updating OwnMaily

Maintenance

Updating OwnMaily pulls the latest Docker images and restarts the stack. Database migrations run automatically on startup. The process takes about a minute and does not require any manual migration steps.

Run the update

SSH into your server and run:

cd ~/ownmaily
docker compose pull
docker compose up -d

That is it. Docker pulls the latest image versions defined in your docker-compose.yml, restarts the containers with the new images, and the app applies any pending database migrations during startup.

What happens to your data

Your data lives in a named Docker volume that is separate from the application containers. Pulling new images and restarting does not touch the volume. Your subscribers, campaigns, settings, and analytics are safe.

Verifying the update

After the restart, check that the app is running:

docker compose ps

All containers should show a status of Up. If the app container shows Restarting, check the logs:

docker logs ownmaily-app-1

Then open the app in your browser to confirm it is working. If the version number is shown anywhere in the UI, you should see the latest version reflected.

Staying up to date

You can watch the GitHub releases page for new versions. Releases include a changelog describing what changed.

There is no auto-update feature in OwnMaily. You need to run the pull/restart command manually when you want to update. Since you bought it outright, you choose when to update - you are never forced onto a new version.