Download the PHP package diarmuidie/envpopulate without Composer
On this page you can find all versions of the php package diarmuidie/envpopulate. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download diarmuidie/envpopulate
More information about diarmuidie/envpopulate
Files in diarmuidie/envpopulate
Package envpopulate
Short Description Tool to interactively populate a `.env` file based on an `.env.example` file whenever Composer installs or updates.
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 envpopulate
diarmuidie/envpopulate
PHP tool to interactively populate a .env file based on an .env.example file whenever Composer installs or updates.
Based on the similar package Incenteev/ParameterHandler. Go check that out if you need to save parameters to a YAML file instead of a env file :+1:.
Developed by Diarmuid.
Installation
You can install EnvPopulate through Composer:
To trigger the EnvPopulate script on composer install and updates you have to add the following scripts to your composer.json file:
Optional
If you want to change the location of the example or generated env file, or add multiple files you can also add an extra section to the composer.json file:
You can also specify if you want to not run the env populate scripts when in non-interactive mode (automated systems):
Usage
Make sure you have an .env.example file in the root of your project (or in a different location by setting the extra options.
The script will run every time you do a composer install or composer update. Press enter to accept the default value or type to overwrite it.
See it in action:
Disabling in Automated Environments
You can disable the EnvPopulate script in automated environments (CI Server like Travis or Jenkins for example). You have two options to do this:
-
Run composer with
--noscriptsoption. This will stop any scripts from being run (including EnvPopulate). - Run Composer in non interactive mode (
--no-interaction). This will cause EnvPopulate to take the default values from.env.example, when generating the.envfile, without asking for user input.
Contributing
Feel free to contribute features, bug fixes or just helpful advice :smile:
- Fork this repo
- Create a feature branch
- Submit a PR ...
- Profit :sunglasses:
Running Tests
You can run the tests through Docker:
Changelog
See the CHANGELOG.md file.
Authors
License
The MIT License (MIT)
Copyright (c) 2016 Diarmuid
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
