16 days ago
Hi there.
This happens 100% of the time now. Its really annoying.
Nothing seems wrong with the deploy. Its successful, but when I enter production all the data is loaded from the staging DB. How is this even possible?
I have to manually redeploy the exact same deployment to fix the issue.
3 Replies
16 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 16 days ago
16 days ago
Did you ever do an environment sync, or is your production service using staging environment variables?
0x5b62656e5d
Did you ever do an environment sync, or is your production service using staging environment variables?
16 days ago
This is running live and has been for a while. Staging and Production are two different environments. If the environment variables were wrong then a redeploy would not fix it I suppose?
joachimholseter
This is running live and has been for a while. Staging and Production are two different environments. If the environment variables were wrong then a redeploy would not fix it I suppose?
16 days ago
Set a cache-busting variable such as NO_CACHE=1 or RAILPACK_DISABLE_CACHE=1 in the Production service to force isolated builds.
also try Turning off GitHub auto-deploys for Production and deploy only after Staging completes.