Package Data | |
---|---|
Maintainer Username: | jeylabs |
Maintainer Contact: | ratheep.ceymplon@jeylabs.com.au (jeylabs) |
Package Create Date: | 2017-04-12 |
Package Last Update: | 2017-04-17 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-12-19 03:17:48 |
Package Statistics | |
---|---|
Total Downloads: | 690 |
Monthly Downloads: | 0 |
Daily Downloads: | 0 |
Total Stars: | 3 |
Total Watchers: | 6 |
Total Forks: | 0 |
Total Open Issues: | 1 |
This package offers you the possibility to edit your .env dynamically through a controller or model.
The current version ships with a graphical user interface based on VueJS to offer you a very simple implementation of all features.
List of available functions:
Install the package via the composer require command:
composer require jeylabs/laravel-dotenv-editor
Add the following line to your composer.json require section:
"require": {
//other packages
"jeylabs/laravel-dotenv-editor": "1.*"
}
Then run the composer update command:
composer update
Add the following line to your config/app.php
providers:
Jeylabs\DotenvEditor\DotenvEditorServiceProvider::class,
Add the following line to your config/app.php
aliases:
'DotenvEditor' => Jeylabs\DotenvEditor\Facades\DotenvEditor::class,
Finally you have to publish the config file and view via:
php artisan vendor:publish --provider="Jeylabs\DotenvEditor\DotenvEditorServiceProvider"
After an Update, maybe you have to force publish:
php artisan vendor:publish --provider="Jeylabs\DotenvEditor\DotenvEditorServiceProvider" --force
Be careful, this will overwrite all your published files! It's always better to delete the config/dotenveditor.php
file manually and then run the php artisan vendor:publish
command than to run the force version.
Now you can edit the config file and put in your values.
Open the config/dotenveditor.php and fill it up with your values.
Note: I had an issue where I had to switch the web-middleware between middleware
and middleware_groups
. In Laravel 5.2, put the web-middleware in the middleware
array. For Laravel 5.1 put it in the middleware_groups
array.
The path to your .env should not be changed.
If you don't want to use the graphical interface, you could deactivate it in the config.
If you want to add more middlewares to the used routes, you could put them in the arrays.