Download the PHP package phpgt/config without Composer
On this page you can find all versions of the php package phpgt/config. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package config
Short Description Manage configuration with ini files and environment variables.
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 config
Manage configuration with ini files and environment variables.
Manage your project configuration by defining defaults, that can be overridden by ini files and environment variables.
Also provides functionality for generating ini files from the CLI.
Documentation: https://php.gt/docs/config
Example usage - loading project configuration:
A project's configuration can be split across multiple files. The following example shows how a secret can be supplied through the environment, which is used to override the default value defined within config.ini, and also shows how other named config files can be used.
nginx.conf:
config.ini:
config.dev.ini:
example.php:
Example usage - generating configuration files:
Sometimes it's useful to generate config files on-the-fly, such as from Continuous Integration scripts. Below shows a quick example of how to generate a config.deploy.ini file with a few key-values that will override the default.
The above command will create a config.deploy.ini file (note the first argument of "deploy") and provide overrides for two ini keys using dot notation. Note that because this command will be run within a continuous integration setting, we are expecting there to be a $BRANCH_NAME variable set for us, allowing us to use a schema name containing the current branch.
