Upgrading
AlertifyPro releases new versions monthly. Follow this guide to upgrade your self-hosted instance safely.
Before upgrading
- Check the changelog for breaking changes and migration notes
- Back up your database
- Test in staging if you have one — upgrades that include database migrations cannot be easily rolled back
# Quick PostgreSQL backup before upgrading
pg_dump -Fc alertifypro > alertifypro-backup-$(date +%Y%m%d).dump
Docker Compose upgrade
# 1. Pull the latest images
docker compose pull
# 2. Restart containers (application will briefly restart)
docker compose up -d
# 3. Run database migrations
docker compose exec app bin/rails db:migrate
# 4. Verify health
curl http://localhost:8080/health
Migrations run automatically — but it's safest to run them explicitly so you can see any output.
Kubernetes upgrade
# 1. Update Helm repo
helm repo update
# 2. Check what's changing
helm diff upgrade alertifypro alertifypro/alertifypro \
--namespace alertifypro \
--values values.yaml
# 3. Apply the upgrade
helm upgrade alertifypro alertifypro/alertifypro \
--namespace alertifypro \
--values values.yaml
# 4. Watch rollout
kubectl rollout status deployment/alertifypro-app -n alertifypro
Migrations run as a pre-upgrade Job automatically with the Helm chart.
Rolling back
If an upgrade causes issues:
Docker Compose
# Pin to a previous version in docker-compose.yml
image: ghcr.io/crayon-alertifypro/alertifypro:2.0.5
# Restart
docker compose up -d
Note: If the new version ran database migrations, rolling back the app may require restoring the database from backup.
Kubernetes
helm rollback alertifypro 1 --namespace alertifypro
Version pinning
Always pin to a specific version in production (not latest):
# docker-compose.yml
image: ghcr.io/crayon-alertifypro/alertifypro:2.1.0
# Helm values.yaml
image:
tag: "2.1.0"
Getting notified of new releases
- ⭐ Watch the GitHub repo for release notifications
- 📧 Subscribe to release emails at alertifypro.com/changelog
- 🔔 Follow
@alertifyproon X / Twitter