Problems with environment variables

[hillary]

Hey there, @mustainer

It looks like you’re experiencing something similar to what we debugged in this thread below. Can you please take a look and follow the proposed steps?

Access of COMMIT_REF in Gatsby project

Hey there, @nord Apologies for the delay here, I appreciate you following up. I brought this up to our Gatsby pro and they are suggesting the following: what if you try "build": "GATSBY_COMMIT_REF=$COMMIT_REF npm run build" rather than setting the environment variable to GATSBY_COMMIT_REF=$COMMIT_REF The problem is that the env var isn’t being expanded as it’s currently declared because .env. files don’t handle env var expansion. Moving this outside of .env to the build script will work aroun…

Additionally, I want to dive into this point and hopefully clarify some differences between server-side variable and build time variables:

@mustainer

I only need them to used them at Build time (so, Server side, so to say).

Server-side variables are variables accessible to functions and defined in the UI. Build time variables are defined in your TOML and are not accessible to functions. Knowing this, could you save your variables in the Netlify UI rather than using .env files?

Let me know if this gets you on the right path!