Download the PHP package ibrostudio/laravel-multenv without Composer
On this page you can find all versions of the php package ibrostudio/laravel-multenv. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ibrostudio/laravel-multenv
More information about ibrostudio/laravel-multenv
Files in ibrostudio/laravel-multenv
Package laravel-multenv
Short Description Manage multiple Laravel env files
License MIT
Homepage https://github.com/ibrostudio/laravel-multenv
Informations about the package laravel-multenv
Laravel Multenv
Manage multiple .env files in Laravel with automatic encryption to embed and share your .env files in your repository.
- Installation
- Basic usage
- Encryption
- Automatic encryption
- Different env files per GIT branches
Installation
You can install the package via composer:
Publish the config file with:
This is the contents of the published config file:
You define which .env files you want to manage:
- a primary .env file, with all variables
- then, you can add one (or more) entries to override variables
Basic usage
At the root of your project, create all files defined in the config and populate them with variables.
Add them to your .gitignore:
or
Then run:
It generates the final .env file, merging variables from all configured .env files.
Encryption
You can encrypt some .env files to embed them securely in your repo.
Generate encryption key
Add it to your .gitignore:
Don't commit your .multenv key in your repo, it is a security risk.
If you work with people on the repo, share manually the key, IT HAS TO BE SAME for everyone.
Configure the files to encrypt
In config/multenv.php, define each file to encrypt with the setting to true
Encrypt
If you use .env in your .gitignore, add after:
Decrypt
Automatic encryption
You can define some git hooks to automate the processes:
1. Merge, encrypt and commit
Create (or modify) a file called pre-push in .git/hooks and add in it:
Make it executable:
2. Decrypt and merge
Create (or modify) a file called post-merge in .git/hooks and add in it:
Make it executable:
Different env files per GIT branches
Modify the configuration as following, adding a pattern entry:
Then, at the root of your project, create env branches files with names based on the pattern.
Example : .env.branch-main
Populate them with variables and use methods like described previously.
If you want/need to keep safe between branches, use a different multenv key for each branch.
Testing
Changelog
Please see CHANGELOG for more information on what has changed recently.
License
The MIT License (MIT). Please see License File for more information.
All versions of laravel-multenv with dependencies
illuminate/contracts Version ^10.0
spatie/laravel-package-tools Version ^1.14.0
vlucas/phpdotenv Version ^5.5