Magento2 Vagrant For Developers Versions Save

Vagrant Box for Magento 2 Developers

7 years ago

Magento EE and sample data directories are added to 'Exclude list' in PhpStorm
Redis is used as default cache backend instead of filesystem
After EE is linked, EE versions of composer.lock and composer.json are replaced back with CE versions (thus are not marked by git as modified)
Improved CLI scripts output formatting

Issue with some files marked as unversioned in git after EE linking
It is now possible to use spaces in path to vagrant project on Windows. On OSX and Linux hosts it works in non-NFS mode, in NFS mode it does not work because of bug in vagrant
Issue with MySQL being down after VM power off

Added ability to configure number of CPUs for virtual machine via etc/config.yaml
Added generation of basic sample data for testing purposes
Ability to upgrade Magento using m-switch-to-ce and m-switch-to-ee (when -u flag is specified)
Redis support for Magento caching
Access to Magento developer mode and storefront/admin UI debugging features via etc/config.yaml
Composer-based installation support
Magento cache warming up after re-install and clearing cache (when -w flag is specified)
Tests configuration files are generated during project initialization
Sample data support
ElasticSearch support
NodeJS, NPM, Gulp and Grunt are installed as part of the provisioning process

7 years ago

Removed requirement for public github token due to Composer limitations (issue is fixed on Composer side)
Changed requirement for minimum box version from 1.0 to 1.1
Upgraded PHP 5.5.9 to PHP 5.6
When init_project.sh is executed, EE will be installed by default, if EE repository is specified in etc/config.yaml.dist. Not supported on Windows hosts

Added setup and upgrade cron scripts to crontab
Added logging of all emails in HTML format to vagrant-magento/log/email
Added host wrapper script for bin/magento command on guest
Added ability to modify guest config files (PHP, Apache etc) directly from host IDE
Added ability to choose if PhpStorm configs should be removed during project reinitialization
Added ability to switch PHP version without destroying the project ("vagrant reload" is required)
Added ability to do force switch to CE or EE (even if already switched to target edition)
Added ability to use Varnish full page caching automatically. (Using "vagrant reload" or m-varnish script)

8 years ago

Moved provisioning scripts
Magento project directory moved to vagrant project root. Current structure is as follows: vagrant-magento/magento2ce/magento2ee
PHP 7.0 is installed by default instead of PHP 5.5.9 (can be configured in etc/config.yaml.dist)
Renamed configuration folder from local.config to etc
Set minimum Vagrant version as 1.8
Improved deployment speed in case of disabled NFS for folders sync
Used custom Vagrant box with pre-installed software necessary for Magento 2 development
Eliminated explicit dependency on PHP for Windows hosts (it can be downloaded and used locally for the project)
XSD URN generation is executed after Magento installation

Added project initialization script and host scripts for routine flows (compatible with OSX, *nix and Windows)
Implemented static value of forwarded SSH port to prevent necessity to reconfigure software accessing guest via SSH
Implemented collision prevention for IP address and host name (in case when several machines are created at once)
Added configuration file etc/config.yaml.dist
Added PHP 7.0 support
Added PHP Storm configuration during project initialization (particularly automatic deployment settings)
Added automatic vagrant plugins installation

8 years ago

With current configuration Vagrant will: