https://docs.railway.com/guides/django mentions Django migrations, but it doesn't mention that migrations should be applied during each deployment, and there is no explanation about how to manage that. Without the missing "apply migrations" logic in the deployment process, the resulting Django deployment is not healthy and not usable for any serious workflow.
https://docs.railway.com/guides/django mentions Django migrations, but it doesn't mention that migrations should be applied during each deployment, and there is no explanation about how to manage that. Without the missing "apply migrations" logic in the deployment process, the resulting Django deployment is not healthy and not usable for any serious workflow.