You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
-117
Original file line number
Diff line number
Diff line change
@@ -4,128 +4,11 @@ All notable changes to this project will be documented in this file.
4
4
This project adheres to [Semantic Versioning](http://semver.org/).
5
5
6
6
*[\[Unreleased\]](#unreleased)
7
-
*[\[v2.2.0\] - 2017-02-25](#v220---2017-02-25)
8
-
*[\[v2.1.0\] - 2016-06-22](#v210---2016-06-22)
9
-
*[\[v2.0.0\] - 2016-02-05](#v200---2016-02-05)
10
-
*[\[v1.0.0\] - 2016-01-11](#v100---2016-01-11)
11
7
12
8
## [Unreleased]
13
9
14
10
### Changed
15
11
16
-
- Verified compatibility with Vagrant 2.x and loosened Vagrant version requirement
17
-
- Config option 'php_version' should now be used for PHP version selection instead of 'use_php7'
18
-
- Upgraded Varnish to v4.1
19
-
- Improved Magento re-installation speed by avoiding unnecessary cache cleaning
20
-
- Custom code sniffer rules replaced with PSR2
21
-
- MessageQueue module will now be installed with CE if using Magento v2.3+
22
-
23
12
### Added
24
13
25
-
- PHP 7.1 and PHP 7.2 support
26
-
- Support for new location of `generated` directory in Magento 2.2.0
27
-
- Basic data generation can be turned off. Added configurable product and customer address generation
28
-
- Documentation in config.yaml.dist for choosing specific composer package versions
29
-
30
-
### Fixed
31
-
32
-
- Magento 2.2.0 EE installation from composer
33
-
34
-
## [v2.2.0] - 2017-02-25
35
-
36
-
### Changed
37
-
38
-
- Magento EE and sample data directories are added to 'Exclude list' in PhpStorm
39
-
- Redis is used as default cache backend instead of filesystem
40
-
- 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)
41
-
- Improved CLI scripts output formatting
42
-
43
-
### Fixed
44
-
45
-
- Issue with some files marked as unversioned in git after EE linking
46
-
- 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](mitchellh/vagrant#7540)
47
-
- Issue with MySQL being down after VM power off
48
-
49
-
### Added
50
-
51
-
- Added ability to configure number of CPUs for virtual machine via [etc/config.yaml](etc/config.yaml.dist)
52
-
- Added generation of basic sample data for testing purposes
53
-
- Ability to upgrade Magento using `m-switch-to-ce` and `m-switch-to-ee` (when `-u` flag is specified)
54
-
- Redis support for Magento caching
55
-
- Access to Magento developer mode and storefront/admin UI debugging features via [etc/config.yaml](etc/config.yaml.dist)
56
-
- Composer-based installation support
57
-
- Magento cache warming up after re-install and clearing cache (when `-w` flag is specified)
58
-
- Tests configuration files are generated during project initialization
59
-
- Sample data support
60
-
- ElasticSearch support
61
-
- NodeJS, NPM, Gulp and Grunt are installed as part of the provisioning process
62
-
63
-
## [v2.1.0] - 2016-06-22
64
-
65
-
### Changed
66
-
67
-
- Removed requirement for public github token due to Composer limitations (issue is fixed on Composer side)
68
-
- Changed requirement for minimum box version from 1.0 to 1.1
69
-
- Upgraded PHP 5.5.9 to PHP 5.6
70
-
- When [init_project.sh](init_project.sh) is executed, EE will be installed by default, if EE repository is specified in [etc/config.yaml](etc/config.yaml.dist). Not supported on Windows hosts
71
-
72
14
### Fixed
73
-
74
-
- Permissions during Magento installation on Windows hosts
75
-
- Issue with Magento compiler on Windows hosts
76
-
- "stdin: is not a tty" warning
77
-
78
-
### Added
79
-
80
-
- Setup and upgrade cron scripts to crontab
81
-
- Logging of all emails in HTML format to `vagrant-magento/log/email`
82
-
- Host wrapper script for bin/magento command on guest
83
-
- Ability to modify guest config files (PHP, Apache etc) directly from host IDE
84
-
- Ability to choose if PhpStorm configs should be removed during project reinitialization
85
-
- Ability to switch PHP version without destroying the project ("vagrant reload" is required)
86
-
- Ability to do force switch to CE or EE (even if already switched to target edition)
87
-
- Ability to use Varnish full page caching automatically. (Using "vagrant reload" or m-varnish script)
88
-
89
-
## [v2.0.0] - 2016-02-05
90
-
91
-
### Changed
92
-
93
-
- Moved provisioning scripts
94
-
- Magento project directory moved to vagrant project root. Current structure is as follows: `vagrant-magento/magento2ce/magento2ee`
95
-
- PHP 7.0 is installed by default instead of PHP 5.5.9 (can be configured in [etc/config.yaml](etc/config.yaml.dist))
96
-
- Renamed configuration folder from `local.config` to `etc`
97
-
- Set minimum Vagrant version as 1.8
98
-
- Improved deployment speed in case of disabled NFS for folders sync
99
-
- Used custom Vagrant box with pre-installed software necessary for Magento 2 development
100
-
- Eliminated explicit dependency on PHP for Windows hosts (it can be downloaded and used locally for the project)
101
-
- XSD URN generation is executed after Magento installation
102
-
103
-
### Added
104
-
105
-
- Added [project initialization script](init_project.sh) and host scripts for routine flows (compatible with OSX, *nix and Windows)
106
-
- Implemented static value of forwarded SSH port to prevent necessity to reconfigure software accessing guest via SSH
107
-
- Implemented collision prevention for IP address and host name (in case when several machines are created at once)
Everyone is welcome to contribute improvements and fixes to this project. There are no specific requirements, just create a pull request with proposed modifications and try to run [tests](https://github.com/paliarush/magento2-vagrant-for-developers-tests) on your local environment.
1
+
Everyone is welcome to contribute improvements and fixes to this project. There are no specific requirements, just create a pull request with proposed modifications and try to run [tests](https://github.com/paliarush/magento2-devbox-for-developers-tests) on your local environment.
-[Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - Ensure that SSH keys are generated and associated with your Github account. See [how to check](https://help.github.com/articles/testing-your-ssh-connection/) and [how to configure](https://help.github.com/articles/generating-ssh-keys/), if not configured.<br />
71
-
:information_source: To obtain the codebase without cloning, just use the Magento 2 codebase instead of `vagrant-magento/magento2ce`. Either method will produce a successful installation.<br />
71
+
:information_source: To obtain the codebase without cloning, just use the Magento 2 codebase instead of `devbox-magento/magento2ce`. Either method will produce a successful installation.<br />
72
72
73
73
<!-- :information_source: On Windows hosts  Git must be [v2.7+](http://git-scm.com/download/win). Also make sure to set the following options to avoid issues with incorrect line separators:
74
74
@@ -163,7 +163,7 @@ Upon a successful installation, you'll see the location and URL of the newly-ins
163
163
164
164
### Getting updates and fixes
165
165
166
-
Current vagrant project follows [semantic versioning](http://semver.org/spec/v2.0.0.html) so feel free to pull the latest features and fixes, they will not break your project.
166
+
Current devbox project follows [semantic versioning](http://semver.org/spec/v2.0.0.html) so feel free to pull the latest features and fixes, they will not break your project.
167
167
For example your current branch is `2.0`, then it will be safe to pull any changes from `origin/2.0`. However branch `3.0` will contain changes backward incompatible with `2.0`.
168
168
Note, that semantic versioning is only used for `x.0` branches (not for `develop` or `master`).
<!--Switch between PHP versions using "php_version: <version>" option in [config.yaml](etc/config.yaml.dist). Supported versions are 5.6, 7.0, 7.1 and 7.2.
332
-
PHP version will be applied after "vagrant reload".
332
+
PHP version will be applied after "devbox reload".
333
333
-->
334
334
335
335
### Activating Varnish
@@ -396,29 +396,29 @@ Note: See [Working with npm](https://www.npmjs.com/package/n#working-with-npm) i
396
396
-->
397
397
### FAQ
398
398
<!--
399
-
1. To debug any CLI script in current Vagrant project, set `debug:vagrant_project` option in [config.yaml](etc/config.yaml.dist) to `1`
400
-
1. Is Windows 10 supported? Yes, but you may face the same issue as described [here](https://github.com/paliarush/magento2-vagrant-for-developers/issues/36) or [here](https://github.com/paliarush/magento2-vagrant-for-developers/issues/173). Also Virtual box may not work on Windows 10 in headless mode, see how to [enable GUI mode](https://www.vagrantup.com/docs/virtualbox/configuration.html)
401
-
1.  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 `use_nfs` option in [config.yaml](etc/config.yaml.dist) to `0` <br />
399
+
1. To debug any CLI script in current Devbox project, set `debug:devbox_project` option in [config.yaml](etc/config.yaml.dist) to `1`
400
+
1. Is Windows 10 supported? Yes, but you may face the same issue as described [here](https://github.com/paliarush/magento2-devbox-for-developers/issues/36) or [here](https://github.com/paliarush/magento2-devbox-for-developers/issues/173). Also Virtual box may not work on Windows 10 in headless mode, see how to [enable GUI mode](https://www.devboxup.com/docs/virtualbox/configuration.html)
401
+
1.  On OSX and \*nix hosts NFS will be used by default to sync your project files with guest. On some hosts Devbox cannot configure NFS properly, in this case it is possible to deploy project without NFS by setting `use_nfs` option in [config.yaml](etc/config.yaml.dist) to `0` <br />
402
402
1.  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 `composer_prefer_source` option in [config.yaml](etc/config.yaml.dist) to `1`
403
403
1. Make sure that you used `magento2-devbox` directory as project root in PHP Storm (not `magento2-devbox/magento`)
404
404
1. If project opened in PhpStorm looks broken, close PhpStorm and remove `magento2-devbox/.idea`. Run `bash magento2-devbox/scripts/host/configure_php_storm.sh`. After opening project in PhpStorm again everything should look good
405
405
1. If code is not synchronized properly on Windows hosts (or when NFS mode is disabled in [config.yaml](etc/config.yaml.dist) 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
406
406
1. Please make sure that currently installed software, specified in [requirements section](#requirements), meets minimum version requirement
407
-
1. 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.
408
-
1. Cannot run unit tests from PHPStorm on Magento 2.2, see possible solution [here](https://github.com/paliarush/magento2-vagrant-for-developers/issues/167)
1. If during a vagrant reload, the following message appears:
407
+
1. Be careful if your OS is case-insensitive, NFS might break the symlinks if you cd into the wrong casing and you power the devbox up. Just be sure to cd in to the casing the directory was originally created as.
408
+
1. Cannot run unit tests from PHPStorm on Magento 2.2, see possible solution [here](https://github.com/paliarush/magento2-devbox-for-developers/issues/167)
Copy file name to clipboardExpand all lines: etc/config.yaml.dist
+5-5
Original file line number
Diff line number
Diff line change
@@ -28,15 +28,15 @@ guest:
28
28
use_nfs: 1
29
29
# [To apply changes: init_project.sh -f] The placeholder IP will be replaced with auto-detected value, unless modified manually before execution of "init_project.sh" script.
30
30
nfs_server_ip: "0.0.0.0"
31
-
# [To apply changes: vagrant reload] Default is 2Gb, around 3Gb is necessary to run functional tests.
31
+
# [To apply changes: devbox reload] Default is 2Gb, around 3Gb is necessary to run functional tests.
0 commit comments