Sync your .env file with .env.example as "template"?

[shineability]

I was checking out this package and I love how it works.

I synced/pruned an .env.example file and some variables were added. By default the new variables are added to the bottom. Typically I would reorder some of them if they belong to a "group" of related variables. Having the variables ordered and organized doesn't necessarily matter for the app to work, but it feels important to me, though. E.g. variables for an Azure AD are grouped together, variables for dev tools are grouped together, ...

At this point I have an updated and organised "template" of which environment variables are needed for this project which will be committed to the repo as a reference for other developers.

Now, instead of adding the .env to the environment_files config, which is probably not a good idea as mentioned in the docs, I would like to "sync" my current .env using the .env.example as a "template". The same way the .env.example is used to generate your .env file when installing a new Laravel project...

High level this would mean:

• Syncing/pruning your .env.example file and reorder if necessary
• Creating a backup of your current .env file
• Copy the exact .env.example file
• Override every variable that was already in the .env with its current value
• Save the file as .env

Does this idea have any merit? :)