Need help with magento2-vagrant-for-developers?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

454 Stars 177 Forks MIT License 315 Commits 50 Opened issues


Vagrant Box for Magento 2 Developers

Services available


Need anything else?

Contributors list

Vagrant project for Magento 2 developers (optimized for Mac, Windows and *nix hosts)

:warning: Current project is not supported anymore. Please check out which is under development and may become an official devbox for Magento 2 in the future.

Tests passing on OSX MIT License Semver Latest GitHub release

What You get

It's expected that the Magento 2 project source code will be located and managed on the host to allow quick indexing of project files by IDE. All other infrastructure is deployed on the guest machine.

Current Vagrant configuration aims to solve performance issues of Magento installed on Virtual Box for development. A custom solution is implemented for Windows hosts. See explanation of the proposed solution.

The environment for Magento EE development is also configured.

It is easy to install multiple Magento instances based on different codebases simultaneously.

The project initialization script configures a complete development environment:

  1. Adds some missing software on the host
  2. Configures all software necessary for Magento 2 using a custom Ubuntu vagrant box (Apache 2.4, PHP 7.0 or 5.6, MySQL 5.6, Git, Composer, XDebug, Rabbit MQ, Varnish)
  3. Installs Magento 2 from Git repositories or Composer packages (can be configured via
    option in etc/config.yaml)
  4. Configures PHP Storm project (partially at the moment)
  5. Installs NodeJS, NPM, Grunt and Gulp for front end development

:information_source: This box uses the n package manager to provide the latest NodeJS LTS version.

How to install

If you never used Vagrant before, read the Vagrant Docs first.


The software listed below should be available in PATH (except for PHP Storm).

  • Vagrant 1.8+
  • VirtualBox
  • Git - Ensure that SSH keys are generated and associated with your Github account. See how to check and how to configure, if not configured.
    :information_source: To obtain the codebase without cloning, just use the Magento 2 codebase instead of
    . Either method will produce a successful installation.

:information_source: On Windows hosts Git must be v2.7+. Also make sure to set the following options to avoid issues with incorrect line separators:

git config --global core.autocrlf false
git config --global core.eol LF
git config --global diff.renamelimit 5000

Installation steps

:information_source: In case of any issues during installation, please read FAQ section

  1. Open terminal and change your directory to the one you want to contain Magento project. On Windows use Git Bash, which is available after Git installation.

  2. Download or clone the project with Vagrant configuration:

    :warning: Do not open it in PhpStorm until
    has completed PhpStorm configuration in the initialize project step below.
     git clone [email protected]:paliarush/magento2-vagrant-for-developers.git vagrant-magento

    Optionally, if you use private repositories on GitHub or download packages from the Magento Marketplace using Composer

    1. Copy etc/composer/auth.json.dist to
    2. Specify your GitHub token by adding
      "": "your-github-token"
      to the
      section for GitHub authorization.
    3. Add the Magento Marketplace keys for Marketplace authorization to the
    4. Copy (optional) etc/config.yaml.dist as
      and make the necessary customizations.
  3. Initialize the project (this will configure the environment, install Magento, and configure the PHPStorm project):

    cd vagrant-magento
  4. Use the

    directory as the project root in PHP Storm (not
    ). This is important, because in this case PHP Storm will be configured automatically by If NFS files sync is disabled in config and on Windows hosts verify the deployment configuration in PHP Storm.

    Use the URL for accessing your Magento storefront in the browser as your Web server root URL. Typically this is the localhost, which refers to your development machine. Depending on how you've set up your VM you may also need a port number, like

  5. Configure the remote PHP interpreter in PHP Storm. Go to Preferences, then Languages and Frameworks. Click PHP and add a new remote interpreter. Select Deployment configuration as a source for connection details.

Default credentials and settings

Some of default settings are available for override. These settings can be found in the file etc/config.yaml.dist.

To override settings create a copy of the file under the name 'config.yaml' and add your custom settings.

When using, if not specified manually, random IP address is generated and is used as suffix for host name to prevent collisions, in case when two or more instances are running at the same time.

Upon a successful installation, you'll see the location and URL of the newly-installed Magento 2 application in console.

Web access: - Access storefront at

- Access admin panel at
- Magento admin user/password:
- Rabbit MQ control panel:
, credentials

:information_source: Your admin URL, storefront URL, and admin user and password are located in


Codebase and DB access: - Path to your Magento installation on the VM: - Can be retrieved from environment variable:

- On Windows hosts:
- On Mac and *nix hosts: the same as on host - MySQL DB host:
(not accessible remotely) - MySQL DB name:
- MySQL DB user/password:
. In CLI just use
with no user and password (
will be used by default)

Codebase on host - CE codebase:

- EE codebase will be available if path to EE repository is specified in

Getting updates and fixes

Current vagrant project follows semantic versioning so feel free to pull the latest features and fixes, they will not break your project. For example your current branch is

, then it will be safe to pull any changes from
. However branch
will contain changes backward incompatible with
. Note, that semantic versioning is only used for
branches (not for

:information_source: To apply changes run

vagrant reload

Day-to-day development scenarios

Reinstall Magento

Use commands described in Switch between CE and EE section with

flag. Before doing actual re-installation, these commands update linking of EE codebase, clear cache, update composer dependencies.

If no composer update and relinking of EE codebase is necessary, use the following command. It will clear Magento DB, Magento caches and reinstall Magento instance.

Go to the root of vagrant project in command line and execute:

bash m-reinstall

Clear Magento cache

Go to the root of vagrant project in command line and execute:

bash m-clear-cache

Switch between CE and EE

Assume, that EE codebase is available in

. The following commands will link/unlink EE codebase, clear cache, update composer dependencies and reinstall Magento. Go to 'vagrant-magento' created earlier and run in command line:
bash m-switch-to-ce
bash m-switch-to-ee

Force switch can be done using

flag even if already switched to the target edition. May be helpful to relink EE modules after switching between branches.

Upgrade can be performed instead of re-installation using


:information_source: On Windows hosts (or when NFS mode is disabled in config.yaml explicitly) you will be asked to wait until code is uploaded to guest machine by PhpStorm (PhpStorm must be launched). To continue the process press any key.

Sample data installation

Make sure that

are defined in config.yaml and point CE and optionally EE sample data repositories. During initial project setup or during
bash -fc
project will be re-created from scratch), sample data repositories willl be checked out to

To install Magento with sample data set

in config.yaml to
and run
bash m-switch-to-ce -f
bash m-switch-to-ee -f
, depending on the edition to be installed. To disable sample data, set this option to
and force-switch to necessary edition (using the same commands).

Basic data generation

Several entities are generated for testing purposes by default using REST API after Magento installation: - Customer with address (credentials

[email protected]
) - Category - Couple simple products - Configurable product

To disable this feature, set

in config.yaml to
and run
bash m-switch-to-ce -f
bash m-switch-to-ee -f
, depending on the edition to be installed.

Use Magento CLI (bin/magento)

Go to 'vagrant-magento' created earlier and run in command line:

bash m-bin-magento 
bash m-bin-magento list

Debugging with XDebug

XDebug is already configured to connect to the host machine automatically. So just:

  1. Set XDEBUG_SESSION=1 cookie (e.g. using 'easy Xdebug' extension for Firefox). See XDebug documentation for more details
  2. Start listening for PHP Debug connections in PhpStorm on default 9000 port. See how to integrate XDebug with PhpStorm
  3. Set beakpoint or set option in PhpStorm menu 'Run -> Break at first line in PHP scripts'

To debug a CLI script:

  1. Create remote debug configuration in PhpStorm, use
    as IDE key
  2. Run created remote debug configuration
  3. Run CLI command on the guest as follows (
    value might be different for you):
 php -d xdebug.remote_autostart=1 

To debug Magento Setup script, go to Magento installation script and find

php ${install_cmd}
. Follow steps above for any CLI script

:informationsource: In addition to XDebug support, config.yaml has several options in

section which allow storefront and admin UI debugging. Plus, desired Magento mode (developer/production/default) can be enabled using `magentomode` option, default is developer mode.

Connecting to MySQL DB

Answer can be found here

View emails sent by Magento

All emails are saved to 'vagrant-magento/log/email' in HTML format.

Accessing PHP and other config files

It is possible to view/modify majority of guest machine config files directly from IDE on the host. They will be accessible in etc/guest directory only when guest machine is running. The list of accessible configs includes: PHP, Apache, Mysql, Varnish, RabbitMQ. Do not edit any symlinks using PhpStorm because it may break your installation.

After editing configs in IDE it is still required to restart related services manually.

Upgrading Magento

Sometimes it is necessary to test upgrade flow. This can be easily done as follows (assuming that you have installed instance):

  • For git-based installation - check out codebase corresponding to the target Magento version. Or modify your
    in case of composer-based installation
  • Use commands described in Switch between CE and EE section with

Multiple Magento instances

To install several Magento instances based on different code bases, just follow Installation steps to initialize project in another directory on the host. Unique IP address, SSH port and domain name will be generated for each new instance if not specified manually in


Update Composer dependencies

Go to 'vagrant-magento' created earlier and run in command line:

bash m-composer install
bash m-composer update

Running Magento tests

See draft

Environment configuration

Switch between PHP versions

Switch between PHP versions using "php_version: " option in config.yaml. Supported versions are 5.6, 7.0, 7.1 and 7.2. PHP version will be applied after "vagrant reload".

Activating Varnish


use_varnish: 1
to use varnish along with apache in config.yaml. Changes will be applied on
. It will use default file etc/magento2defaultvarnish.vcl.dist generated from a Magento 2.1 instance. Magento 2.2+ supports additional Varnish features and you may need to provide custom version of VCL to enable them. Varnish Version: 4.1

Use the following commands to enable/disable varnish without reinstalling Magento:

m-varnish disable
m-varnish enable

Activating ElasticSearch

:information_source: Available in Magento EE only.


search_engine: "elasticsearch"
in config.yaml to use ElasticSearch as current search engine or
search_engine: "mysql"
to use MySQL. Changes will be applied on

Use the following commands to switch between search engines without reinstalling Magento:

m-search-engine elasticsearch
m-search-engine mysql

Redis for caching

:information_source: Available in Magento v2.0.6 and higher.

Redis is configured as cache backend by default. It is still possible to switch back to filesystem cache by changing

in config.yaml.

Reset environment

It is possible to reset project environment to default state, which you usually get just after project initialization. The following command will delete vagrant box and vagrant project settings. After that it will initialize project from scratch. Magento 2 code base (

directory) and etc/config.yaml and PhpStorm settings will stay untouched, but guest config files (located in etc/guest) will be cleared.

Go to 'vagrant-magento' created earlier and run in command line:

bash -f

It is possible to reset Magento 2 code base at the same time. Magento 2 code base will be deleted and then cloned from the repositories specified in etc/config.yaml

bash -fc

To reset PhpStorm project configuration, in addition to

bash -fp

Ultimate project reset can be achieved by combining all available flags:

bash -fcp

Switch NodeJS Versions

By default, the box will install the latest

version using the n package manager. If you need another version of
because of Magento's
requirements, simply run:

Note: See Working with npm if after switching versions with

is not working properly.


  1. To debug any CLI script in current Vagrant project, set
    option in config.yaml to
  2. Is Windows 10 supported? Yes, but you may face the same issue as described here or here. Also Virtual box may not work on Windows 10 in headless mode, see how to enable GUI mode
  3. On OSX and *nix hosts NFS will be used by default to sync your project files with guest. On some hosts Vagrant cannot configure NFS properly, in this case it is possible to deploy project without NFS by setting
    option in config.yaml to

  4. On Windows hosts you might face
    Composer Install Error: ZipArchive::extractTo(): Full extraction path exceed MAXPATHLEN (260)
    exception during
    composer install
    . This can be fixed in 2 ways: decrease path length to the project directory or set
    option in config.yaml to
  5. Make sure that you used
    directory as project root in PHP Storm (not
  6. If project opened in PhpStorm looks broken, close PhpStorm and remove
    . Run
    bash vagrant-magento/scripts/host/
    . After opening project in PhpStorm again everything should look good
  7. If code is not synchronized properly on Windows hosts (or when NFS mode is disabled in config.yaml explicitly), make sure that PhpStorm is running before making any changes in the code. This is important because otherwise PhpStorm will not be able to detect changes and upload them to the guest machine
  8. Please make sure that currently installed software, specified in requirements section, meets minimum version requirement
  9. Be careful if your OS is case-insensitive, NFS might break the symlinks if you cd into the wrong casing and you power the vagrant up. Just be sure to cd in to the casing the directory was originally created as.
  10. Cannot run unit tests from PHPStorm on Magento 2.2, see possible solution here
  11. Permission denied (publickey)
  12. If during a vagrant reload, the following message appears:

    There was a problem while downloading the metadata for your box to check for updates. This is not an error, since it is usually due to temporary network problems. This is just a warning. The problem encountered was: The requested URL returned error: 404 Not Found

    It is likely that your vagrant cli is caching an old url. Perform the following cli commands:

    sed -i -- 's/atlas.hashicorp/vagrantcloud/g' ~/.vagrant.d/boxes/{name of your paliarush/ubuntu image}/metadata_url
    mv ~/.vagrant.d/boxes/{name of your paliarush/ubuntu image}/metadata_url2 ~/.vagrant.d/boxes/{name of your paliarush/ubuntu image}/metadata_url

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.