In a Laravel app most sensitive configuration values, like a db password, are being saved in an
.env file. This file usually does not get committed in a git repo. In this way you can share the repo with collaborators without having them to know the sensitive values of your production environment.
The keys of the
.env are often saved in an
.env.example file that is saved in the repo. This helps you and your collaborators get up to speed quickly when installing the app locally. They can immediately see which environment variables are needed to run the app.
Over time however you might add a variable to
.env and forgetting to add it to
.env.example. It’s a mistake that is easily made, and I have made that mistake many times in the past (sorry co-workers).
A couple of days ago Julien Tant released laravel-env-sync. This package makes sure the
.env file is in sync with
.env.example. After having installed the package you can run this artisan command to perform the sync:
php artisan env:sync
Thanks Julien for that awesome little package.