Github actions and .env
Hey all,
Loving the T3 stack so far. I was wondering if anyone is deploying to fly?
The default fly deploy locally copies in my .env file to all the env vars I need are there.
On github actions obviously I haven't committed .env.
So I have a couple of questions:
How do people use github actions secrets? At the moment I've worked round the need for build time access to
.env with env > .env && ... but I'm not sure about this approach long term
How do you handle different env at build time vs run time? I think vercel does this all for you(?) but fly seems a bit different.1 Reply
I've had a bit of a poke through the code now. It looks like I might be able to turn on
SKIP_ENV_VALIDATION. That would leave me with only needing to know the subset of env vars actually needed for build time.
I guess DATABASE_URL for prisma migrate in the post install would be one - any others I'd absolutely need?