|
10 | 10 | * [Installation steps](#installation-steps)
|
11 | 11 | * [Default credentials and settings](#default-credentials-and-settings)
|
12 | 12 | * [Getting updates and fixes](#getting-updates-and-fixes)
|
13 |
| - * [GitHub limitations](#github-limitations) |
14 | 13 | * [Day-to-day development scenarios](#day-to-day-development-scenarios)
|
15 | 14 | * [Reinstall Magento](#reinstall-magento)
|
16 | 15 | * [Clear magento cache](#clear-magento-cache)
|
@@ -71,8 +70,12 @@ Software listed below should be available in [PATH](https://en.wikipedia.org/wik
|
71 | 70 | git clone git@github.com:paliarush/magento2-vagrant-for-developers.git vagrant-magento
|
72 | 71 | ```
|
73 | 72 |
|
74 |
| - 1. Copy [etc/composer/auth.json.dist](etc/composer/auth.json.dist) to `etc/composer/auth.json` and specify your [GitHub OAuth token](https://github.com/settings/tokens) there. See [API rate limit and OAuth tokens](https://getcomposer.org/doc/articles/troubleshooting.md#api-rate-limit-and-oauth-tokens) for more information |
75 |
| - |
| 73 | + 1. Optionally, if you use private repositories on GitHub or download packages from Magento Marketplace |
| 74 | + |
| 75 | + - copy [etc/composer/auth.json.dist](etc/composer/auth.json.dist) to `etc/composer/auth.json` |
| 76 | + - specify your GitHub token by adding `"github.com": "your-github-token"` to `github-oauth` section for GitHub authorization |
| 77 | + - add Magento Marketplace keys for Marketplace authorization |
| 78 | + |
76 | 79 | 1. Optionally, copy [etc/config.yaml.dist](etc/config.yaml.dist) as `etc/config.yaml` and make necessary customizations
|
77 | 80 |
|
78 | 81 | 1. Initialize project, configure environment, install Magento, configure PHPStorm project:
|
@@ -121,16 +124,6 @@ Current vagrant project follows [semantic versioning](http://semver.org/spec/v2.
|
121 | 124 | 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`.
|
122 | 125 | Note, that semantic versioning is only used for `x.0` branches (not for `develop`).
|
123 | 126 |
|
124 |
| -### GitHub limitations |
125 |
| - |
126 |
| -Be aware that you may encounter GitHub limits on the number of downloads (used by Composer to download Magento dependencies). |
127 |
| - |
128 |
| -These limits may significantly slow down the installation since all of the libraries will be cloned from GitHub repositories instead of downloaded as ZIP archives. In the worst case, these limitations may even terminate the installation. |
129 |
| - |
130 |
| -If you have a GitHub account, you can bypass these limitations by using an OAuth token in the Composer configuration. See [API rate limit and OAuth tokens](https://getcomposer.org/doc/articles/troubleshooting.md#api-rate-limit-and-oauth-tokens) for more information. |
131 |
| - |
132 |
| -For the Vagrant configuration you may specify your token in `etc/github.oauth.token` file after cloning the repository. The file is a basic text file and is ignored by Git, so you'll need to create it yourself. Simply write your OAuth token in this file making sure to avoid any empty spaces, and it will be read during deployment. |
133 |
| - |
134 | 127 | ## Day-to-day development scenarios
|
135 | 128 |
|
136 | 129 | ### Reinstall Magento
|
|
0 commit comments