Configuration guide

In EverShop, some of the configurations can be done from the admin panel like Payment method, Shipment method, Taxes… We will learn more about these items in our user guide document.

In this section, we will focus on the configuration for development.

Under the hood, EverShop makes use of config package to handle the configuration.

Configuration file location

Configurations are JSON files stored in configuration files within a directory named ‘config’ located at the root level of your application.

Let’s take a look at an example

{
  "shop": {
    "title": "Amazing shop",
    "description": "Amazing shop",
    "currency": "usd",
    "language": "en",
    "timezone": ""
  },
  "catalog": {
    "product": {
      "image": {
        "thumbnail": {
          "width": 100,
          "height": 100
        },
        "listing": {
          "width": 300,
          "height": 300
        },
        "single": {
          "width": 500,
          "height": 500
        },
        "placeHolder": "/default/image/placeholder.png"
      }
    },
    "showOutOfStockProduct": false
  },
  "checkout": {
    "allowCountries": [
      "US",
      "VN"
    ],
    "shippingRate": [
      {
        "condition": {},
        "destimation": [
          "*"
        ],
        "rate": 10
      }
    ]
  },
  "order": {
    "shipmentStatus": [
      {
        "name": "Unfullfilled",
        "code": "unfullfilled",
        "badge": "warning",
        "progress": "incomplete"
      },
      {
        "name": "Fullfilled",
        "code": "fullfilled",
        "badge": "success",
        "progress": "complete"
      }
    ],
    "paymentStatus": [
      {
        "name": "Pending",
        "code": "pending",
        "badge": "default",
        "progress": "incomplete"
      },
      {
        "name": "Paid",
        "code": "paid",
        "badge": "success",
        "progress": "complete"
      },
      {
        "name": "Refunded",
        "code": "refunded",
        "badge": "critical",
        "progress": "complete"
      }
    ]
  },
  "customer": {
    "address": {
      "full_name": {
        "type": "text",
        "title": "Full name",
        "validarionRules": [
          "notEmpty"
        ]
      }
    }
  },
  "system": {
    "database": {
      "host": "localhost",
      "port": "3306",
      "database": "install",
      "user": "root",
      "password": "123456"
    }
  }
}

Configuration and deployment environment

Configuration files can be overridden and extended by environment variables.

For example, you can overwrite the configuration for your production store by below steps

• Create a new configuration file named ‘production.json’ in the ‘config’ directory.
• Add your configuration for production

{
  "system": {
    "database": {
      "host": "aws.production",
      "port": "3306",
      "database": "production",
      "user": "root",
      "password": "lsdjgdfhgoiwnm"
    }
  }
}

Working with configuration in your code

Let's take a look at the below code:

const config = require('config');
//...
const dbConfig = config.get('system.db');
db.connect(dbConfig, ...);

if (config.has('optionalFeature.detail')) {
  const detail = config.get('optionalFeature.detail');
  //...
}

The above example shows us how to get the configurable variables from the configuration file.

config.get() will throw an exception for undefined keys to help catch typos and missing values. You can use config.has() to test if a configuration value is defined.

You also can use the below method to get the configuration and provide a default value in case the configuration does not exist:

const {
  getConfig
} = require('@evershop/evershop/lib/util/getConfig');

let shopTitle = getConfig('shop.title', 'EverShop'),