Replies: 1 comment
-
The Currently my work around for your problem, is to create a separate repository containing my environment files and secrets that is private and have that repository checked out during the deploy and point to the env_file located in there. This is an example workflow that does exactly that: https://github.com/cssnr/django5-boiler/blob/master/.github/workflows/deploy.yaml Let me know if you have any more questions... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello and thanks for building this action! I was wondering if the
env_file
input variable is supposed to be a file that exists in the repo, because I was kinda hoping it could be a .env file living on my vps instead, which I don't want to commit to my repo as you can imagine.Beta Was this translation helpful? Give feedback.
All reactions