devraj
commented
11 months ago I was making some headway on this on a client's project that uses this template. My initial approach was to make a Taskfile that would be suitable for production and make available a subset of operations like:
- Run alembic migration
- Attach the database to
headof the migrations, this can be useful if we are initialising a blank database but subsequently want to run migrations - Leave a task that allows the developer to run arbitrary alembic operations
Debian does not have an official go-task package but Apline linux does. These are the two Linux flavours published by the official Python base image.
Shifting to Apline would mean a massive move away from our general toolkit.
People have workarounds using tools like pacstall (in this instance on Ubuntu). Before we can provide this as part of the template we would have to figure out how we install task on Debian.
Failing everything task provides a binary
sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -dWe already have curl available on the pods to assist with other actions. I have tested this on our current images.
Extending #44 we should define how
alembicis configured in the production container and how you are expected to run the migration in production environments.We should also think about providing Task based scripts, Tasks is available as a Github action which would work well with the proposed CI/CD workflow.