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

when running dotenvx convert write original .env* file to .env*.previous #221

Open
motdotla opened this issue May 19, 2024 · 2 comments
Open

Comments

@motdotla
Copy link
Contributor

this way if there is an edge case bug with encryptme (we haven't tested all edge cases yet), the user does not lose their important .env data.

@motdotla motdotla changed the title when running dotenvx encryptme write original .env* file to .env*.previous when running dotenvx protect write original .env* file to .env*.previous May 27, 2024
@motdotla
Copy link
Contributor Author

i think should be unnecessary if we get all edge cases covered. it adds so much noise.

@motdotla motdotla changed the title when running dotenvx protect write original .env* file to .env*.previous when running dotenvx convert write original .env* file to .env*.previous May 27, 2024
@bingtsingw
Copy link

Maybe we can make convert command more general to convert to or from encrypted data:
dotenvx convert --encrypt -f .env.xxx -o .env.xxx.encrypted
dotenvx convert --decrypt -f .env.xxx.encrypted -o .env.xxx

--encrypt and -o can be designed as optional to be compatible with current command

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

No branches or pull requests

2 participants