Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to deploy same app but with a different .env file? #57

Open
chillbert opened this issue Nov 6, 2024 · 1 comment
Open

How to deploy same app but with a different .env file? #57

chillbert opened this issue Nov 6, 2024 · 1 comment

Comments

@chillbert
Copy link

chillbert commented Nov 6, 2024

Before I deployed with $sidekick launch my app with the .env file - now I created a .env.production file and want to deploy the same app but this time with the new .env.production file. How do I do that? Since $sidekick deploy does use the .env file. I think changing in sidekick.yml file to: file: .env.production doesn't do anything right?

and how can we delete an existing docker container already running on the VPS? Just by deleting the sidekick.yml file locally and re-init and re-launching?
(Beside loging into the vps via ssh and stopping, deleting, pruning the container manually; what I did... but then I get this error on deployment:

Please enter which env file you would like to load .env.production
8:23PM INFO Env File: Detected - Loading env vars from .env.production

                          Launching your application on your VPS 🚀                               

✔ VPS is reachable
✔ Latest docker image built
✔ Image saved successfully
⚠ Moving image to your server
└── error running command - mkdir myApp: - mkdir: cannot create directory ‘myApp’: File

@MightyMoud
Copy link
Owner

MightyMoud commented Nov 8, 2024

Hi dude,
This use case is not covered yet. It does make sense however. Let me try a couple of things and get back to you tonight

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants