Make pyinfra deployment idempotent and automatically create an admin user #16

New issue

Open

opened 2025-04-28 11:24:00 +00:00 by CSDUMMI · 0 comments

CSDUMMI commented

2025-04-28 11:24:00 +00:00

(Migrated from gitlab.com)

Before we can automate the upgrades of Babka, we must be able to automatically deploy and test new version to a staging server.

In babka/ there already is a basic deployment script for pyinfra, but it is not idempotent:

The docker compose is always restarted.
Migrations are always run.

By fixing these pyinfra can be run multiple times and not change the state.

Before we can automate the upgrades of Babka, we must be able to automatically deploy and test new version to a staging server. In `babka/` there already is a basic deployment script for pyinfra, but it is not idempotent: - [ ] The docker compose is always restarted. - [ ] Migrations are always run. By fixing these `pyinfra` can be run multiple times and not change the state.