Download the PHP package machaven/laravel-cascading-config without Composer
On this page you can find all versions of the php package machaven/laravel-cascading-config. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download machaven/laravel-cascading-config
More information about machaven/laravel-cascading-config
Files in machaven/laravel-cascading-config
Package laravel-cascading-config
Short Description Multiple cascading environmental configuration files support for Laravel 5
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-cascading-config
Laravel 5 Cascading Config Files
Why? - The .env problem
When continously developing and extending a laravel application, you may find that your .env file becomes large and hard to maintain. When multiple branches with .env changes are deployed, it becomes a nightmare to consolidate all the .env changes and update the live .env file.
This forced me to rethink configuration and what is truly important inside an .env file.
What to keep in your .env file
- Standard laravel .env settings
- Sensitive information, like login credentials for other apis.
What to take out of your .env file
- All custom settings that might seldom change.
Why use cascading config files?
-
Cascading configuration files allow you to keep a set of config files for every environment. All environment configs override the base configs in the config folder. This allows you to setup a dynamic config for each environment.
- Settings changes can be recorded on pull requests. This prevents settings changes from being lost when only changed on the server .env file.
Furthermore if you use the env() function in your config files, it will allow you to override any defaults in the config file with variables from the .env file if they exist.
Install
Install the package through composer
After installing, add the ServiceProvider to the providers array in app/config/app.php (not required for laravel 5.5+)
How this works
The service provider will check if the directory exists for the environment configured in your .env file. If the environment folder exists, then all configuration files will be read from it and merged over the configurations from the config folder.
Example for cascading config files
Firstly, create your default config file in the standard laravel config/ folder.
Now create a folder to override the example config for an environment. A folder can be created for any environment defined in your APP_ENV. In this example, we use local:
Now create another example config in the local folder:
Example config file contents
config/example.php
config/local/example.php
In the local configuration above, we are not overriding the curlTimeout array key.
Example config results
When APP_ENV is local:
When APP_ENV is prod:
As you can see, the above file is not overridden by the one in the config/local/ folder.
When APP_ENV is prod and TEST='ENV FILE' is added to .env file:
The test key is overridden here by the TEST variable in the .env file. This is because we are using the env() helper in our config files to override settings for any environment; if they exit in the .env.
