Post-Installation Configuration

Last updated:
Edit on GitHub

This document provides guidance on advanced configuration and customization of your Spryker project after completing the initial setup. These steps help you optimize and adapt the Demo Shop to your specific project needs.

Manage modules

A Spryker module is a single-function unit that has well-defined dependencies and can be updated independently. Composer is used for installing and managing module dependencies. To define your strategy when implementing updates, learn about our module and feature release process.

To learn about the module versioning approach in Spryker, see Semantic Versioning: Major vs. Minor vs. Patch Release.

Clean up modules

  1. Go through the modules that came with the Demo Shop you’ve installed.
  2. Come up with the list of modules you actually need.
  3. Remove unnecessary modules by following module upgrade guides in a backwards fashion.

Configure services

  1. Define how to manage the settings in the configuration files with Configuration management.
  2. Configure services.
  3. Configure Elasticsearch.
  4. Configure queue.
  5. Configure stores.
  6. Set up cronjobs.

Clean up store configuration

If you chose to start with one store, clean up the configuration of the unneeded stores in the following files:

  • config/install/*
  • data/import/*
  • deploy.dev.yml
  • config_default.php
  • src/SprykerConfig/CodeBucketConfig.php

Clean up data import

  • In data/import, remove the files of the unneeded stores.
  • Change the default config in DataImportConfig::getDefaultYamlConfigPath().
  • Define the needed stores in CodeBucketConfig::getCodeBuckets().