Configuring Spryker after installing with DevVM

Edit on GitHub

We will soon deprecate the DevVM and stop supporting it. Therefore, we highly recommend installing Spryker with Docker.

Configuring Git

If you want to commit from within the VM, it is recommended to set the right Git preferences:

git config --global ""
git config --global "Your Name"
git config --global push.default simple
git config --global pull.rebase true

Configuring VM

If you like to change the default configuration of the virtual machine, you can do this by following the example below.

export VM_CPUS=2
export VM_MEMORY=4192
export VM_NAME="My custom name"
export VM_IP_PREFIX="10.10.0."

Disabling a shared folder

For non-standard setups you have the option to disable shared folder with Spryker code.

If you decide not to use shared folders feature, it’s your responsibility to get Spryker code into the /data/shop/development/current directory of your VM. For example, you can use a file synchronization utility like Unison.

export VM_SKIP_SF=1

Using SSH instead of HTTPS

In case you already have your SSH keys set up on your host system, it can be more convenient to directly use them for downloading the repository:


Before proceeding with the installation, please make sure you have your SSH public key in GitHub.

To generate your SSH key, follow Generating SSH keys.

Filesystem layout

A common Spryker Project is like a typical web project. There is the project level code and the Spryker Commerce OS code. Spryker Commerce OS code is installed into the vendor folder. As you are running both Yves and Zed inside the VM, you will actually see the source code for both. They share a similar directory layout, but specific folders are indicated by the name of the application. So, a folder named Zed naturally belongs to Zed. A Shared folder belongs to Yves and Zed.

config configuration files
data log files and caches
src your project code
static static
vendor packages installed via composer. In particular vendor/spryker contains Yves and Zed bundles.

Services and ports

MySQL or MariaDB Server 3306 Username is development, password is mate20mg.
PostgreSQL Server 5432 Username is development, password is mate20mg.
Redis 10009 You can explore Redis with Redis Desktop Manager or a similar tool.
Mailcatcher 1080 Catches all the mails that are sent during development in the Dev VM.
Management UI 15672 See Default Queue Engine for more information.

Activating the Opcache module

To optimize the performance of the system, you can enable the Opcache. This is not recommend for development, because you may get strange results. To activate the Opcache, just put the following lines at the end of the php.ini and restart.php.

This configuration is not optimized for production environments!

sudo nano /etc/php7.2/fpm/php.ini
; configuration for php ZendOpcache module
; priority=05
; Determines if Zend OPCache is enabled
; Determines if Zend OPCache is enabled for the CLI version of PHP
; The OPcache shared memory storage size.
; The amount of memory for interned strings in Mbytes.
; The maximum number of keys (scripts) in the OPcache hash table.
; Only numbers between 200 and 100000 are allowed.
; The maximum percentage of "wasted" memory until a restart is scheduled.
; When disabled, you must reset the OPcache manually or restart the
; webserver for changes to the filesystem to take effect.
; How often (in seconds) to check file timestamps for changes to the shared
; memory storage allocation. ("1" means validate once per second, but only
; once per request. "0" means always validate)
; If enabled, a fast shutdown sequence is used for the accelerated code
sudo service php7.2-fpm restart

Setting VM name

It is advised to label your VM (especially when you have more than a single one):

set-vm-name my-project

This will display vagrant@my-project in your console starting with the next login.

Setting a domain name for the shop

To set a domain name for your Spryker shop, change values of the following keys in the shop configuration file:

$config[ApplicationConstants::HOST_ZED] = '';
$config[ApplicationConstants::HOST_YVES] = '';

The first key is responsible for proper call from Yves to Zed, while the second one is used for domain name used for session cookies.

Upgrading to a newer version

To check for newer released versions, we recommend that you follow the steps described in Core Updates.