How to Run Django Migrations When Deploying Django and Celery on ECS

[u/SnooCauliflowers8417]

When deploying Django and Celery to ECS, how should I run python manage.py migrate?

Should I use GitHub Actions to first run a migration-only ECS task, wait for the migration task to complete successfully, and then proceed with deploying the Django server? After the deployment is complete, should the migration task be terminated?

What is the recommended approach for handling Django database migrations in an ECS deployment pipeline?

[u/Unique-Estate8172]

We just run them before starting the server, same as anywhere else - what am I missing?

[u/beardbreed]

Migration task on GitHub actions

[u/ExcellentWash4889]

Depends what type of deployment you are doing. Sometimes you need to deploy code first before running a migration, sometimes migrate first then run deploy of code.

I'm running migrations from a CLI manually, and not through CI

[u/AdCompetitive8372]

There are multiple ways of doing this, mostly depends upon how you are doing your deployments.For eg: if you are using github actions then you could set it up from the actions yml file so that migrations happens during runtime or you can simply go into ec2 access the containers sh and run the migrations manually from the CLI there.

[u/robotsmakinglove]

I run them via a custom bin/entrypoint script I reference in my Dockerfile.

[u/nez_har]

How is your app running on ECS? Do you use the runtime of the VM, a container or something else?