Download the PHP package webgriffe/module-config-override without Composer

On this page you can find all versions of the php package webgriffe/module-config-override. 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?

Example code of webgriffe/module-config-override

Informations about the package module-config-override

Config Override Magento 2 Module

:warning:DEPRECATION:warning:

This module it is now useless, you can:

  1. Do composer require symfony/dotenv, take a look to these exaplanations to see the hierarchy;

  2. Create the file app/etc/EnvironmentVariablesLoader.php

  3. Load it throught composer modifing the composer.json file:

  4. Create the env files configuring variables as written on the magento docu.

    :warning:DEPRECATION:warning:

Build Status

A Magento 2 module that overrides default configuration from file which can be added to version control, inspired by this Magento 1.x extension: https://github.com/webgriffe/config-extension.

Installation

Add this extension as dependency using Composer:

composer require webgriffe/module-config-override
php bin/magento setup:upgrade

Config override

Magento configuration is driven by database. This, sometimes, is overkill and forces us to maintain upgrade script to keep Magento envorinment aligned with features development. So, this extension enables additional config source that loads several YAML files and overrides database configuration.

Loaded YAML files are (in this order):

Also, if the MAGE_ENVIRONMENT environment variable is defined, then two additiontal files are loaded. For example, if the MAGE_ENVIRONMENT variable value is dev, the following two files are loaded:

Configuration in YAML files must be specified with the same structure of Magento system configuration, for example:

Only default configuration scope is overridden.

CLI notes

Please note that if you use the MAGE_ENVIRONMENT variable then it should be always set when Magento is running. So is not enough to set it through your webserver (for example with a SetEnv "dev" in Apache) but it should also be set into your command line shell. Otherwise, if you have the Magento's configuration cache enabled and you clear the cache from the command line, the MAGE_ENVIRONMENT will not be applied and you'll get unexpected behaviours.

Remember to "export" you env variable when you run a command via shell:

alternative you can add the MAGE_ENVIRONMENT=dev in your shell configuration (ex. for bash):

file /home/<you user>/.bashrc:

Overridden config values are shown in backend

Overridden config values are shown in Magento's backend. Every config setting it's shown on its section. For example, if you have the following default.yml file:

When you'll go to Stores -> Configuration -> General -> Design you'll find the overridden config value shown and not editable.

This feature improves a lot the usability of this extension.

To Do

Credits

All versions of module-config-override with dependencies

PHP Build Version
Package Version
Requires php Version ~5.6.0|~7.0.0|~7.1.0
magento/framework Version ^100.0.0|^101.0.0
magento/module-backend Version ^100.0.0
magento/module-config Version ^100.1.1|^101.0.0
symfony/yaml Version ^2.0|^3.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 webgriffe/module-config-override contains the following files

Loading the files please wait ....