Download the PHP package jarnix/laravel-auto-environment without Composer
On this page you can find all versions of the php package jarnix/laravel-auto-environment. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download jarnix/laravel-auto-environment
More information about jarnix/laravel-auto-environment
Files in jarnix/laravel-auto-environment
Package laravel-auto-environment
Short Description Auto-detection and configuration of the environment with multiple env files
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-auto-environment
For Laravel 5+
Auto-detects the application environment with the hostname or http host
Allows for multiple environments and versioned "env" files.
Detects the application environment from a env file or the hostname or http host. A .env file will always overwrite any other file (default Laravel's behavior)
Use this code by adding this in bootstrap/app.php
Put your different configuration files in the app's "/config" folder, or another folder (specified as the 'envsFolder' parameter) :
- .env.local
- .env.testing
- .env.production
Parameters -- You can customize these parameters:
- envsFolder: where you put the .env files (local.env, production.env...)
- hostnameLocalRegexp: the regexp for the hostname in local mode (cli)
- urlLocalRegexp: the regexp for the http host in local mode (http)
- urlTestingRegexp: the regexp for the http host in testing mode (http)
- urlProductionRegexp: the regexp for the http host in prod mode (http)
You can force the environment everywhere
You can also force the environment you want by creating a file called "env" at the root of the app, containing the environment you want to load.
This code will then load the "env" file that you want in the "envsFolder" folder. For example: if the file's content is "local" => the file : /config/.env.local will be loaded
You can still force the environment in artisan
If you haven't created a env file, you can still obviously force the environment by using:
Or use a .env file
And you can use a .env file as usual, this will then bypass this code.
