a year ago
I have a nextjs service which during the build stage doesn't seem to have the correct environment variables available. In my staging environment I see NODE_ENV set to production and RAILWAY_ENVIRONMENT_NAME undefined.
Should variables normally be available during build? I saw a caveat that only applied to docker builds but this is building from a github repo.
4 Replies
a year ago
I've tracked this down to a misconfiguration in our turbo config.
Status changed to Awaiting User Response Railway • over 1 year ago
Status changed to Solved christian • over 1 year ago
a year ago
I ran into the same issue. Turns out you needed to specify in globalEnv in your turbo.json the environment variables that weren't getting picked up in the image. Hopefully that will save someone 30 minutes 🙂
Status changed to Awaiting Railway Response Railway • about 1 year ago
victorpatru
I ran into the same issue. Turns out you needed to specify in `globalEnv` in your `turbo.json` the environment variables that weren't getting picked up in the image. Hopefully that will save someone 30 minutes 🙂
a year ago
Or set turbo to loose mode!
Status changed to Awaiting User Response Railway • about 1 year ago
9 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 10 months ago