Download the PHP package formigone/php-config without Composer
On this page you can find all versions of the php package formigone/php-config. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 php-config
PHP-CONFIG
This project is a loose port of node-config. I've only implemented enough of it to help me get going with an existing project.
What does it do?
The goal of this package is to help you manage configuration files separated by environment, but used as a single object.
How it works
Suppose your application exists in three environments: development, stage, and production. Each environment has its own unique configurations, and all three share some configuration in common.
As an organized developer, you'll create a config directory somewhere in your project, where you'll store the following files:
You'll then have a single config object for whatever environment you're in, where default.json and the environment-specific .json object are merged together, with the default values being overwritten by the environment values (using a shallow merge).
Why reinvent the wheel?
So this project essentially mimics ZF1's Zend_Config, which allows for inheritable configs. Why use this instead?
- Why use JSON?
- So configs can be shared across PHP and JavaScript/Node.js
- Why not use Zend_Config_Json?
- Because Zend_Config_Json only parses a single file. That works fine in PHP, but if you use something in Node.js like node-config (which is what I happen to use), the you can't reuse the same config files. Given my specific use case (where I'm reusing configs and starting off with node-config), this makes sense, and hence my need for this package.
