Dennis
Someone asked to keep revisions of the .env contents. Obviously, that would require us to save those .env files (encrypted and a custom security layer).
Robin
Not really a fan of it, I know Forge saves root passwords and I'm not a fan of that either.. It can be handy to have a "changelog" of the .env, true, but I think the most 'privacy respected' way would be to just store "User X has changed the .env" as a log. Maybe you can add an opt-in for a full log? Then the user decides.
dcxweb
I'm also not a fan, I'm not sure really what the benefit is - for external servs especially - if the rightful owner has access to their services they can get the keys easily enough and should have them somewhere safe if they need to spin up new instances. The suggestion of @Robin in my opinion makes sense as an opt-in, but never should be the default. Maybe wait and see how many actually want this before going to all the effort :)
Dennis
Item authorRoger, closed, I've received more replies via Discord and other channels, no go! 🥰
.env revisions
-
Dennis moved item to board Closed
5 days ago -
Dennis moved item to board Under review
1 week ago -
Dennis moved item to project Panel Requests
1 week ago -
Dennis created the item
1 week ago