You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When populating an env file with either new content or updates the keys are stored in whatever order. This is annoying and difficult to find keys if you have many. Order the keys in ascending order and then populate back the file
The text was updated successfully, but these errors were encountered:
If we add this, it will need to be a setting. I personally don't want the order to change at all. I usually have grouped together keys that make sense and don't want them changed.
I think we should have the file match the example file... replacing the .env.example values with the values from the .env... it's part of a new issue I'm posting, for new functionality.
When populating an env file with either new content or updates the keys are stored in whatever order. This is annoying and difficult to find keys if you have many. Order the keys in ascending order and then populate back the file
The text was updated successfully, but these errors were encountered: