-
Hello. We have around 60 apps, running on staging and production servers, so I've been trying to be methodical and write up my process for switching a running server over from EnvKey 1 to EnvKey 2 but I can't get even the first one working. Importing the app environments into v2 worked fine (when I used JSON), but it's getting the remote servers running on v2 where it all falls down. This is what I've written up so far...
VERSION=$(curl https://envkey-releases.s3.amazonaws.com/latest/envkeysource-version.txt) && curl -s https://envkey-releases.s3.amazonaws.com/envkeysource/release_artifacts/$VERSION/install.sh | bash
The output from 6 and any edit: The output from |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 14 replies
-
Hi @drcongo, a few questions: 1 - Do you have an 2 - To narrow down the issue, does it work if you run it like this:
Replace 3 - If 2 doesn't work above on the server, does it work for you locally? |
Beta Was this translation helpful? Give feedback.
-
Hi @danenania
|
Beta Was this translation helpful? Give feedback.
-
Hi @danenania, any updates on the seamless transition? Thanks |
Beta Was this translation helpful? Give feedback.
Hi @danenania
.envkey
file which was generated by the desktop app, I've put that on the server too but with the same result.echo 'error: ENVKEY invalid'; false