Download the PHP package jchook/dotenv-to-php without Composer
On this page you can find all versions of the php package jchook/dotenv-to-php. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download jchook/dotenv-to-php
More information about jchook/dotenv-to-php
Files in jchook/dotenv-to-php
Package dotenv-to-php
Short Description Convert dotenv files to PHP
License MIT
Homepage https://github.com/jchook/dotenv-to-php
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 dotenv-to-php
dotenv-to-php
Convert dotenv files to PHP.
Why use it?
Storing configuration in the environment is a tenant of a Twelve Factor App and has many advantages. For example, it allows you to keep your passwords separate from your code.
However, it's not always practical to set environment variables on development machines or continuous integration servers where multiple projects are run. In these scenarios, we can load variables from a .env as needed.
Instead of parsing a .env at runtime with complex PHP dependencies, we can use dotenv-to-php to compile our .env to native PHP.
-
It's fast. The conversion is instantaneous. At runtime, simply load your env vars using the generated PHP. You can even use it in production.
- It's simple. No runtime dependency. The transpiler is only phpdotenv.
1. Install
You can just download the one file -OR- add it as a dev dependency via composer:
composer require --dev jchook/dotenv-to-php2. Create .env
If you don't already have one, create a .env file in the root directory of your project. Add all environment-specific variables (anything likely to change between servers or deployments) on individual lines like so:
Notice that you should quote values with spaces, etc. and that it's possible to reference previously defined variables as in normal shell environments. Comments beginning with # are ignored.
Do not commit your .env file to source control. Instead, store it somewhere secure, or use a tool like vault.
3. Build .env.php
Simply call bin/dotenv-to-php via command-line to convert your .env file to PHP.
Usage is roughly dotenv-to-php [infile] [outfile]. If no infile or outfile is specified, they default to .env and $infile.php respectively. You can also specify - (hyphen) for stdin or stdout... respectively.
4. Integrate
In your PHP application, simply include the compiled .env.php file. Your loaded environment variables will be available via $_SERVER, $_ENV, and getenv().
Ideally you can integrate the .env.php file generation into your existing build process (either for CI or local development). All examples below assume that your dotenv file is saved in the current working directory as .env.
Composer
If you installed via composer, you can integrate it as a script in your composer.json file:
Then invoke via:
Node JS
Many folks are using node js to compile their static assets such as javascript. If you want to plug-in to this existing build process, you can use the built-in child_process module.
Webpack 4+
You can easily incorporate the above into an ad-hoc webpack plugin. In your webpack.config.js file:
License
MIT.
