Application Updates

Audience: Deployment Administrator, Developer Related: Raspberry Pi · Gcp · Environment And Secrets · Migrations

For an ordinary Blackcap application change, deploy or copy the changed files into the installed checkout, run idempotent migrations when the service pre-start step does not already do so, restart inky_admin.service, and validate the affected feature. Keep this procedure short for application-only changes.

Add infrastructure steps only when the change affects Nginx, stunnel, systemd units, certificates, database services, cron, cloud resources, or environment variables. Documentation-only changes require no application restart.

Normal update

cd /path/to/Blackcap
# Copy, deploy, or pull the reviewed changed files.
sudo systemctl restart inky_admin.service
sudo systemctl status inky_admin.service --no-pager

The installed service runs tools/run_database_migrations.py before Gunicorn starts. Run the migration command manually only when diagnosing or when the deployment does not use the supplied unit.

Infrastructure changes

Use direct unit-file editing where established:

sudo nano /etc/systemd/system/inky_admin.service
sudo systemctl daemon-reload
sudo systemctl restart inky_admin.service