Download the PHP package threatdatascience/envarray without Composer
On this page you can find all versions of the php package threatdatascience/envarray. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download threatdatascience/envarray
More information about threatdatascience/envarray
Files in threatdatascience/envarray
Package envarray
Short Description Automagically replace leaf values in a multidimensional array with env vars
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 envarray
EnvArray
Summary
EnvArray allows you to auto-magically fill array values with env vars. It's zero-dependency as well (outside of PHPUnit for development/your sanity).
Usage
Env String Pattern
Env Var Name
Env var names can be any combination of [A-Za-z0-9_-], however they cannot be only [-_]+.
Coercion Type
Supported types:
- Boolean via
bool - Integer via
int - Float via
float - String via
string(or no type, but useful as you need to define the type if you want to use a default value)
Default Values
Any value goes, given the limitation that there are no sanity checks for something like:
Default default
The default default is null.
Why not use \${.+}?
Using \${.+} introduces too many conflicts, as there are reasonable use cases for passing an env var as a literal in a
string. We agree that it would make things simpler from a basic use-case perspective, but the level of complexity of the
project jumps like crazy if we need to support denoting that we want to keep the literal string vs. parsing it.
"Hacking on the source"
Code is in ./src, and tests are in ./tests.
We welcome contributions, suggestions, and bug reports, however we do ask that if you open a ticket, please be as verbose as possible to keep things streamlined. We also maintain 100% code coverage, so PR's with tests are awesome.
