I saw you working with the env files, please see: Environment Variables | RedwoodJS Docs
The .env is hidden, but …
Technically, we use dotenv-defaults, which is how we also supply and load .env.defaults.
Here’s how I use:
-
.env.example - All envars needed but with blank values. This informs the developer everything they may need. Sometimes I add comments here as to which are web and which are api (since for web you will need to set them in toml). Note this file is checked into GH so you do not want any values that exposed secrets etc.
-
.env.defaults - Just the envars from .example that I am OK with setting as public values, if this is important to share with others. This informs the developer everything they may need and a valid value. Sometimes I add comments here as to which are web and which are api (since for web you will need to set them in toml). Note this file is checked into GH so you do not want any values that exposed secrets etc.
-
.env. Secrets. Vars you do not want to share with anyone. This can mimic prod or staging if needed. This is a hidden file and should never be checked in to GH.
Recently I have been using Doppler to manage across environments (prod, dev, staging, previews).