So, env vars are typically only available at build time, not once deployed:
These variables are made available primarily in the build environment
Ideally, you’ll make use of the key during the build process and parse it at this time. There may be ways to make this available once deployed but it’ll need a bit of thought and engineering!
I’m just trying to build something that lets me use Airtable (or Baserow or similar) as a back end. If there’s only a little bit of code I need to add to make the app work with a traditional PostgreSQL database or something similar, I’d be glad to try it.
Hi, @bgschust. It looks like you are trying to run a server. If so, the following support guide might be helpful:
It might be possible to adapt the server process to run as a serverless function but you cannot just “run a server” at Netlify. The Jamstack design philosophy doesn’t use a traditional application server.
Thanks for the reference, it looks thorough and well thought-out, but I was hoping there would be a simple solution to deploy an existing project just to see how much time I’d have to spend on DevOps tasks. It sounds like there will be a lot of steps if I take that route instead of basic API requests. Minimizing server tasks for a web project would be ideal.