Download the PHP package phower/config without Composer

On this page you can find all versions of the php package phower/config. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package config

Phower Config

Simplified methods to handle configuration data in PHP.

Requirements

Phower Config requires:

Instalation

Add Phower Config to any PHP project using Composer:

Getting Started

An associative array can be used as configuration data to be handled on any application.

Include configuration

Optionally configuration data can be read from a plain PHP script returning an array:

Interface methods

Because we implemented ArrayAccess Interface and Magic Methods it's also possible to access configuration data in different styles:

Normalized key names

Since key names are normalized internally it's possible to relax on naming conventions:

Note that normalized key names can ride to duplicates which should be avoided by using some sort of naming convention when Phower Config instances are created. E.g always use snake-case or camel case on array element keys.

Read-only mode

By default instances are created read-only which means they can't be changed after creation. However this behaviour can be changed in two ways:

Note the argument of readOnly method is optional. When omitted the method returns the state of read-only mode; otherwise it sets its state to TRUE or FALSE.

Allow-override mode

Like in read-only mode it's also possible to control overrides in Phower Config instances. Initially overrides are not allowed but this can be changed like previously:

Note the argument of allowOverride method is optional. When omitted the method returns the state of allow-override mode; otherwise it sets its state to TRUE or FALSE.

Obviously overrides can only be done with read-only mode set to FALSE.

Changing configuration

When required to change configuration after creation that can be done by setting or removing keys:

Like in getting key values from configuration array access interface and magic methods are also available:

Checking configuration

To check if a given key exists in configuration another method is available:

Advanced Usage

In some situations may be required to export a configuration instance to array or merge another config object into the current instance. To provide these needs methods toArray and merge are available:

Running Tests

Tests are available in a separated namespace and can run with PHPUnit in the command line:

Coding Standards

Phower code is written under PSR-2 coding style standard. To enforce that CodeSniffer tools are also provided and can run as:

Reporting Issues

In case you find issues with this code please open a ticket in Github Issues at https://github.com/phower/config/issues.

Contributors

Open Source is made of contribuition. If you want to contribute to Phower please follow these steps:

  1. Fork latest version into your own repository.
  2. Write your changes or additions and commit them.
  3. Follow PSR-2 coding style standard.
  4. Make sure you have unit tests with full coverage to your changes.
  5. Go to Github Pull Requests at https://github.com/phower/config/pulls and create a new request.

Thank you!

Changes and Versioning

All relevant changes on this code are logged in a separated log file.

Version numbers follow recommendations from Semantic Versioning.

License

Phower code is maintained under The MIT License.


All versions of config with dependencies

PHP Build Version
Package Version
Requires php Version ^5.6 || ^7.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package phower/config contains the following files

Loading the files please wait ....