https://docs.railway.com/guides/django mentions staticfiles and WhiteNoise, but it doesn't mention that collectstatic command should be applied during each deployment, and there is no explanation about how to manage that. Without the missing "collect static" 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 staticfiles and WhiteNoise, but it doesn't mention that
collectstaticcommand should be applied during each deployment, and there is no explanation about how to manage that. Without the missing "collect static" logic in the deployment process, the resulting Django deployment is not healthy and not usable for any serious workflow.