Deployment using Docker should use a "sidecar" restart: on-failure container to run migrations #548
Description
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
It can be useful to have 2 services in a docker-compose.yml, one of which is the actual app and one that reuses the same config but runs a single replica that restarts on error that only executes the migration command. This speeds up container start times, especially as the migrations grow and it separates the two responsibilities (migrations, web server) so that they can be tinkered with individually.
Describe alternatives you've considered
Leave it as is. It's fine for now and this isn't the highest of priorities. Just mentioning it here for now.