PHPackages                             alaa/magento2-store-config - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. alaa/magento2-store-config

AbandonedArchivedMagento2-module

alaa/magento2-store-config
==========================

Magento 2 Store Configuration Setup

1.0.0(7y ago)01MITPHPPHP ~7.1.3||~7.2.0

Since Mar 28Pushed 7y ago1 watchersCompare

[ Source](https://github.com/alaa-almaliki/magento2-store-config)[ Packagist](https://packagist.org/packages/alaa/magento2-store-config)[ RSS](/packages/alaa-magento2-store-config/feed)WikiDiscussions master Synced 2mo ago

READMEChangelog (1)Dependencies (5)Versions (2)Used By (0)

Magento Store Configurations
============================

[](#magento-store-configurations)

Installation
------------

[](#installation)

```
composer install alaa/magento2-store-config
php -f bin/magento module:enable Alaa_StoreConfig
php -f bin/magento setup:upgrade

```

How it works
------------

[](#how-it-works)

### Dumping the data

[](#dumping-the-data)

you would first run the following command:

`php -f bin/magento store-config:dump`

The above command will dump the data in the `core_config_data` table to the config files. The data will be broken into the following sections:

- The folder `app/etc/store-config`
- Deploy mode`developer` resulting in paths `app/etc/store-config/developer`
- Scopes which will be resulting into:
    - `app/etc/store-config/developer/default`
    - `app/etc/store-config/developer/stores`
    - `app/etc/store-config/developer/websites`
- Then into default, store-code and website-code such as:
    - `app/etc/store-config/developer/default/default.php`
    - `app/etc/store-config/developer/stores/default.php`
    - `app/etc/store-config/developer/websites/base.php`

Sensitive Data will not be dumped as setting sensitive data should not be done via version control - click [here](https://devdocs.magento.com/guides/v2.3/extension-dev-guide/configuration/sensitive-and-environment-settings.html) to find out more about sensitive configurations.

The command `php -f bin/magento store-config:dump` will dump the data initially so development can start from that point. Then configurations can be added as needed and thus these configurations can be shared among the team to keep the same configuration across local environments. The breakdown into development and production modes will help keep the configurations separate in case configurations in production vary from the development environment.

You have to be in production mode to generate configs for the production, however you can create them manually to `app/etc/store-config/production`.

Sample configuration file: `app/etc/store-config/developer/default/default.php`

```
