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
@@ -134,6 +135,7 @@ Note, that semantic versioning is only used for `x.0` branches (not for `develop
134
135
1. Make sure that you used `vagrant-magento` directory as project root in PHP Storm (not `vagrant-magento/magento2ce`)
135
136
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
136
137
1. Please make sure that currently installed software, specified in [requirements section](#requirements), meets minimum version requirement
138
+
1. If MySQL fails to start and Magento reinstallation fails with `ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (13)`, try to run login to virtual machine using `vagrant ssh` and then run `sudo dpkg-reconfigure mysql-server-5.6`, then `sudo service mysql restart.`
137
139
138
140
## Day-to-day development scenarios
139
141
@@ -212,6 +214,10 @@ To debug Magento Setup script, go to [Magento installation script](scripts/guest
212
214
213
215
Answer can be found [here](https://github.com/paliarush/magento2-vagrant-for-developers/issues/8)
214
216
217
+
### View emails sent by Magento
218
+
219
+
All emails are saved to 'vagrant-magento/log/email' in HTML format.
220
+
215
221
### Accessing PHP and other config files
216
222
217
223
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](etc/guest) directory only when guest machine is running. The list of accessible configs includes: PHP, Apache, Mysql, Varnish, RabbitMQ.
@@ -231,17 +237,15 @@ Unique IP address, SSH port and domain name will be generated for each new insta
231
237
232
238
### Reset environment
233
239
234
-
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, vagrant project settings and PhpStorm project settings. After that it will initialize project from scratch. Magento 2 code base (`magento2ce` directory) and [etc/config.yaml](etc/config.yaml.dist) will stay untouched, but guest config files (located in [etc/guest](etc/guest)) will be removed.
240
+
It is possible to reset project environment to default state, which you usually get just after project initialization. The following command will delete vagrant boxand vagrant project settings. After that it will initialize project from scratch. Magento 2 code base (`magento2ce` directory) and [etc/config.yaml](etc/config.yaml.dist)and PhpStorm settings will stay untouched, but guest config files (located in [etc/guest](etc/guest)) will be cleared.
235
241
236
242
Go to 'vagrant-magento' created earlier and run in command line:
237
243
238
244
```
239
245
bash init_project.sh -f
240
246
```
241
247
242
-
You can reset project settings and 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](etc/config.yaml.dist)
243
-
244
-
Go to 'vagrant-magento' created earlier and run in command line:
248
+
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](etc/config.yaml.dist)
245
249
246
250
```
247
251
bash init_project.sh -fc
@@ -251,6 +255,10 @@ To reset PhpStorm project configuration, in addition to `-f` specify `-p` option
251
255
252
256
```
253
257
bash init_project.sh -fp
254
-
OR
258
+
```
259
+
260
+
Ultimate project reset can be achieved by combining all available flags:
0 commit comments