Ansible provisioned Ubuntu 16.04 vagrant box for Magento2 development.

Definitely not full-featured but useful to bootstrap a dev project.

• Vagrant
• VirtualBox

This box uses Ansible Local Provisioner. As a result, Ansible do not need to be installed on the host.

geerlingguy/ubuntu1604

• Dev tools: git, vim, curl, htop
• PHP (7.0 + Composer + Xdebug)
• Nginx
• Redis (for session, full page cache and frontend cache)
• MariaDB 10.0 (dedicated user and database)
• Magento2 (automated project creation if directory is empty, installation and configuration)

git clone https://github.com/cedricblondeau/magento2-ansible-vagrant

Create a dev.yml conf file in ansible/group_vars:

cd magento2-ansible-vagrant
cp ansible/group_vars/dev.yml.sample ansible/group_vars/dev.yml

And configure your environment:

magento_account_public_key: YOUR_PUBLIC_KEY_HERE
magento_account_private_key: YOUR_PRIVATE_KEY_HERE
mysql_user: magento2
mysql_password: magento2
mysql_dbname: magento2
magento2_language: en_US
magento2_currency: USD
magento2_admin_user: admin
magento2_admin_password: admin2015
magento2_admin_email: [email protected]
magento2_admin_firstname: John
magento2_admin_lastname: Doe
magento2_crypt_key: YOUR_CRYPT_KEY
magento2_base_url: http://192.168.33.10

See syncing section. You can skip this step if you just want to try Magento2 and don't need to edit files.

vagrant up

Default base URL is: http://192.168.33.10

By default, Magento2 files live in the box.

It's up to you to configure your preferred sync solution. Here are some ideas:

You can find a commented out statement in Vagrantfile.

Example:

  config.vm.synced_folder "../magento2", "/home/vagrant/repos/magento2",
    type: 'nfs', mount_options: ['rw', 'async', 'fsc' ,'actimeo=2']

See vagrant-nfs_guest

You could also use your text editor/IDE in the VM. You may want to install a GUI or play with X11 forwarding to do so.

It's probably not frozen. Downloading dependencies can take time and it depends on multiple factors such as internet connection speed and syncing strategy.

It may happen if a step failed during the installation and fpm service did not start properly. As a result, nginx cannot communicate with fpm service. Restarting the VM or php-fpm (sudo service php7.0-fpm restart) may help.