Replies: 2 comments 2 replies
-
Hey @wlarch! Yes, we've considered multiple-environment support before. Would love to hear your thoughts...
|
Beta Was this translation helpful? Give feedback.
-
I also came across this and it's something that is in my opinion essential for how useful Envault is. In it's current state, Envault is a tool to manage and sync between multiple local environments. That's of course fine, but if Envaults supports multiple environments, it would turn into something way more useful: the nr. 1 tool to keep track of all your environment variables, in all your environments. I didn't dive too deep into the source code, but I did look at the migrations and I think it can be relatively simple to add support for it. Create a database (+ model) for managing Environments and relate it to If you add a migration for the
If the Slightly modify the What do you think? |
Beta Was this translation helpful? Give feedback.
-
Greetings, thank you for developing this wonderful tool for the Laravel community. We have previously developed a similar tool using AWS S3 Buckets and command line push/pull commands. Our tool allow pushing
.env
files to project S3 Buckets depending on the environment (local, staging, production) and pulling.env
files for different environments during deployment pipelines or manually using our local tool.We understand your tool help managing local
.env
files.Would you recommend using it for different environments (staging, production) ?
If yes, we would create an Envault project for every project environment (my-app-staging, my-app-prod) and add the
.envault.json
file to.gitignore
?If not, is it something you gave a thought ?
Beta Was this translation helpful? Give feedback.
All reactions