Skip to content

Commit

Permalink
Add Magento Upgrade Support #101
Browse files Browse the repository at this point in the history
  • Loading branch information
Alex Paliarush committed Dec 16, 2016
1 parent d2a0bd2 commit 167bba2
Showing 1 changed file with 16 additions and 4 deletions.
20 changes: 16 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@
* [Connecting to MySQL DB](#connecting-to-mysql-db)
* [View emails sent by Magento](#view-emails-sent-by-magento)
* [Accessing PHP and other config files](#accessing-php-and-other-config-files)
* [Upgrading Magento](#upgrading-magento)
* [Multiple Magento instances](#multiple-magento-instances)
* [Update Composer dependencies](#update-composer-dependencies)
* [Environment configuration](#environment-configuration)
Expand Down Expand Up @@ -139,18 +140,20 @@ Note, that semantic versioning is only used for `x.0` branches (not for `develop
## Day-to-day development scenarios

### Reinstall Magento
To save some time and get clear Magento installation, you can skip installation of software like web server or php.
The following command will clear Magento DB, Magento caches and reinstall Magento instance.

Go to 'vagrant-magento' created earlier and run in command line:
Use commands described in [Switch between CE and EE](#switch-between-ce-and-ee) section with `-f` 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 'vagrant-magento' created earlier and run in command line:
Go to the root of vagrant project in command line and execute:

```
bash m-clear-cache
Expand All @@ -170,6 +173,8 @@ bash m-switch-to-ee

Force switch can be done using `-f` 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 `-u` flag.

:information_source: On Windows hosts (or when NFS mode is disabled in [config.yaml](etc/config.yaml.dist) 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
Expand Down Expand Up @@ -226,6 +231,13 @@ 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 `composer.json` in case of composer-based installation
- Use commands described in [Switch between CE and EE](#switch-between-ce-and-ee) section with `-u` flag

### Multiple Magento instances

To install several Magento instances based on different code bases, just follow [Installation steps](#installation-steps) to initialize project in another directory on the host.
Expand Down

0 comments on commit 167bba2

Please sign in to comment.