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
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.
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
.envenv > .env && ...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.
Similar Threads
Was this page helpful?
