This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Update first-time-setup.md #2266
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
|
You should add changes from PR #2267 to this PR, and push back up for review. Please also ensure you're changing all applicable versions (if they aren't symlinked together). |
shrielenee
added
the
Waiting for Response
shrielenee
suggested changes
Jun 20, 2018
| @@ -40,10 +40,10 @@ Prior to setting up your workspace, you may want to gather the following credent | |||
|
|
|||
| * **Magento Access Key**: Provides secure access through a 32-character authentication token. The token authenticates between your account, the Magento 2 code repo (repo.magento.com), and any other Git services like GitHub and 3rd party accounts needed for development. You can create multiple Magento access keys. For the workspace setup, you can start with one specific key for your code repository. To generate a key, contact the Project Owner to generate [Magento authentication keys]({{ page.baseurl }}/install-gde/prereq/connect-auth.html). | |||
| * **Cloud Project account**: The Project Owner or Technical Admin (Super User) should invite you to the {{site.data.var.ece}} project. When you receive the e-mail invitation, click the link and follow the prompts to create your account. See [Set up an account]({{ page.baseurl }}/cloud/before/before-workspace.html#newaccount) for details. | |||
| * **Magento Encryption Key**: When importing an existing Magento system only, you will need to capture the Magento encryption key used to protect your access and data for the Magento database. For details on this key, see [Resolve issues with encryption key]({{ page.baseurl }}/cloud/trouble/trouble-crypt-key-variable.html) | |||
| * **Magento Encryption Key**: When importing an existing Magento system only, you will need to capture the Magento encryption key used to protect your access and data for the Magento database. For details on this key, see [Resolve issues with an encryption key]({{ page.baseurl }}/cloud/trouble/trouble-crypt-key-variable.html) | |||
There was a problem hiding this comment.
This change isn't relevant, as "Resolve issues with encryption key" is the actual name of the page. Please revert.
shrielenee
added
Editorial
|
Hello @shrielenee Thank you! |
shrielenee
removed
the
Waiting for Response
|
Thanks for making these changes @neeta-wagento! |
shrielenee
approved these changes
Jun 21, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a: Fix typos
Summary
Fix typos
When this pull request is merged, it will...
Additional information