process.env variables all empty
Not sure what has changed recently, but now, when I deploy, all of my references to
process.env.WHATEVER have empty values. The keys still appear if I throw a console log on process.env but have no value. The values are present in the railway admin. Please advise20 Replies
Project ID:
c1b075f0-cdf7-409e-8fc0-1f63f0e089cbc1b075f0-cdf7-409e-8fc0-1f63f0e089cb
show some examples if you can please
yea, so I throw a console log in my node app on
process.env and basically just see all my ENV vars as empty:
so build fails
never had an issue until recently
send the build table at the top of the build logs please
this?
oh wow, that explains it, you are still using buildpacks
Buildpacks was deprecated long ago
yea it's been a few minutes since I've deployed updates to this app lol
will need to tag in @jr here
Just following up. Anything I can do on my end to fix this?
Hey, sorry for taking so long to get back to you. Just taking a look at this now
no worries! Thanks jr
looks like it's working now. Thank you for fixing 
wanted to see if I upgrade to nixpacks through the settings tab, will it break things or require some code-level changes on my end?
wanted to see if I upgrade to nixpacks through the settings tab, will it break things or require some code-level changes on my end?Glad it is working! Sorry forgot to respond here when that fix was merged yesterday
It should just work, but depends a bit on dependencies that your application is using
You can try creating another service and building with Nixpacks there if you want to check first
excellent. My existing service has 3 environments (development, staging, prod) - if I upgraded on the dev environment, will affect staging and prod?
No, changes made to a staging env aren’t merged to prod unless you click ship it
isn't that forked environments?
They were wondering if they could use their forked environments instead