Trust me, erasing secret data from version control is open-heart surgery for your VCS you never want to perform. On the other hand, having secrets in version control is helpful to keep track of changes made, given that you do so carefully. Enter Laravel Credentials.
A couple of benefits include:
- Credentials are encrypted, so nobody can read them without the key (which you should not store in version control)
- Encrypted credentials are in version control, so you have a history of change
- You can deploy credential changes along with code changes
- Your secrets exist in one location
Since credentials are encrypted and require a key, how do you edit them with this package?
Editing Laravel Credentials
To edit your credentials, you use an artisan command provided by the Laravel Credentials package:
1php artisan credentials:edit
Once you update the credentials, the new encrypted version gets stored in the credentials file (by default the file lives at
config/credentials.php.enc. The credentials file is accessible via helpers.
To access encrypted credentials, you use the provided
credentials() helper function:
1$credential = credentials('api-password');
To install this package and start using it, install it via composer with:
1composer require beyondcode/laravel-credentials
You can optionally publish the config file with the following:
1php artisan vendor:publish --provider="BeyondCode\Credentials\CredentialsServiceProvider" --tag="config"
Learn more about the Laravel Credentials package and access the source code from beyondcode/laravel-credentials on GitHub.
You might already be familiar with the encrypted file approach for sensitive data if you’ve used Ansible Vault.