Spryker Suite

License: MIT

Suite vs Demo Shops

Master Suite represents all Spryker OS modules and doesn't guarantee functional, business, and demo data consistency. Please consider B2B or B2C demo-shop when building standard E-Commerce use cases:

• https://github.com/spryker-shop/b2c-demo-shop/releases/
• https://github.com/spryker-shop/b2b-demo-shop/releases/
• https://github.com/spryker-shop/b2c-demo-marketplace/releases/
• https://github.com/spryker-shop/b2b-demo-marketplace/releases/

Vagrant Installation

In order to install the Shop Suite on your machine, you can follow the instructions described in the link below:

For DevVM based installation instructions, see About the Installation Guides.

If you encounter any issues during or after the installation, see Troubleshooting article.

Docker installation

For detailed installation instructions of Spryker in Docker, see Getting Started with Docker.

For troubleshooting of Docker based instances, see Troubleshooting.

Prerequisites

For the installation prerequisites, see Docker Installation Prerequisites.

Recommended system requirements for MacOS:

Macbook type	vCPU	RAM
15'	4	6GB
13'	2	4GB

Installation

Run the commands:

mkdir suite && cd suite
git clone https://github.com/spryker-shop/suite.git ./
git clone git@github.com:spryker/docker-sdk.git docker

Production-like environment

1. Run the following commands right after cloning the repository:

docker/sdk boot -s

Please, follow the recommendations in output in order to prepare the environment.

docker/sdk up

2. Git checkout with assets and importing data:

git checkout your_branch
docker/sdk boot -s
docker/sdk up --assets --data

Optional up command arguments:

• --assets - build assets
• --data - get new demo data

3. Light git checkout:

git checkout your_branch
docker/sdk boot -s

docker/sdk up

4. Reload all the data:

docker/sdk clean-data && docker/sdk up && docker/sdk console q:w:s -v -s

Developer environment

1. Run the commands right after cloning the repository:

docker/sdk boot deploy.dev.yml

Please, follow the recommendations in output in order to prepare the environment.

docker/sdk up

2. Git checkout:

git checkout your_branch
docker/sdk boot -s deploy.dev.yml
docker/sdk up --build --assets --data

Optional up command arguments:

• --build - update composer, generate transfer objects, etc.
• --assets - build assets
• --data - get new demo data

3. If you get unexpected application behavior or unexpected errors:

   1. Run the command:

   git status

   2. If there are unnecessary untracked files (red ones), remove them.

   3. Restart file sync and re-build the codebase:

   docker/sdk trouble
   docker/sdk boot -s deploy.dev.yml
   docker/sdk up --build --assets

4. If you do not see the expected demo data on the Storefront:

   1. Check the queue broker and wait until all queues are empty.

   2. If the queue is empty but the issue persists, reload the demo data:

   docker/sdk trouble
   docker/sdk boot -s deploy.dev.yml
   docker/sdk up --build --assets --data

Troubleshooting

No data on Storefront

Use the following services to check the status of queues and jobs:

• queue.spryker.local
• scheduler.spryker.local

Fail whale

1. Run the command:

docker/sdk logs

2. Add several returns to mark the line you started from.
3. Open the page with the error.
4. Check the logs.

MacOS and Windows - files synchronization issues in Development mode

1. Follow sync logs:

docker/sdk sync logs

2. Hard reset:

docker/sdk trouble && rm -rf vendor && rm -rf src/Generated && docker/sdk sync && docker/sdk up

Errors

ERROR: remove spryker_logs: volume is in use - [{container_hash}]

1. Run the command:

docker rm -f {container_hash}

2. Repeat the failed command.

Error response from daemon: OCI runtime create failed: .... \\\"no such file or directory\\\"\"": unknown.

Repeat the failed command.