diff --git a/src/_data/toc/cloud-guide.yml b/src/_data/toc/cloud-guide.yml index 76ec8d59d83..6a34a65f0f6 100644 --- a/src/_data/toc/cloud-guide.yml +++ b/src/_data/toc/cloud-guide.yml @@ -491,11 +491,11 @@ pages: url: /cloud/live/stage-prod-test.html versionless: true - - label: Go live and launch + - label: Site launch url: /cloud/live/live.html versionless: true children: - - label: Go live checklist + - label: Launch checklist url: /cloud/live/go-live-checklist.html versionless: true diff --git a/src/_data/whats-new.yml b/src/_data/whats-new.yml index 0c4725683e9..4a41d2e17b2 100644 --- a/src/_data/whats-new.yml +++ b/src/_data/whats-new.yml @@ -896,7 +896,7 @@ entries: type: Major update date: November 27, 2019 link: https://github.com/magento/devdocs/pull/6080 -- description: Added the [Security configuration](https://devdocs.magento.com/cloud/live/go-live-checklist.html#security-configuration) +- description: Added the [Security configuration](https://devdocs.magento.com/cloud/live/site-launch-checklist.html#security-configuration) section to the "Go live checklist" topic in the _Cloud Guide_ and replaced the current Go live checklist document attachment with the most recent version, which is more comprehensive and up-to-date. diff --git a/src/cloud/architecture/pro-develop-deploy-workflow.md b/src/cloud/architecture/pro-develop-deploy-workflow.md index e68bf4871ea..3b40b08c9cb 100644 --- a/src/cloud/architecture/pro-develop-deploy-workflow.md +++ b/src/cloud/architecture/pro-develop-deploy-workflow.md @@ -9,7 +9,7 @@ functional_areas: - Cloud --- -The {{site.data.var.ece}} Pro plan includes a single, Git repository with a Global Master and three, main environments: the Integration environment for development and testing, the Staging environment for testing with all services, and the Production environment to go live. See [Pro architecture]({{ site.baseurl }}/cloud/architecture/pro-architecture.html) for an overview. +The {{site.data.var.ece}} Pro plan includes a single, Git repository with a Global Master and three, main environments: the Integration environment for development and testing, the Staging environment for testing with all services, and the Production environment for launching and maintaining your live site. See [Pro architecture]({{ site.baseurl }}/cloud/architecture/pro-architecture.html) for an overview. The following graphic demonstrates the Pro develop and deploy workflow, which uses a simple, git-branching approach. You [develop](#develop) code using an Active branch based on the Integration environment branch, _pushing_ and _pulling_ code changes to and from your remote, Active branch. You deploy verified code by _merging_ the remote branch to the base branch, which activates an automated [build and deploy](#deploy) process for that environment. @@ -67,10 +67,10 @@ It is best to thoroughly test every service, verify your performance testing too ### Merge to Production -After thorough testing in the Staging environment, merge to the Production environment and thoroughly test using live credentials. The moment you go live, customers must be able to complete purchases and administrators must be able to manage the live store. We provide a detailed, clear walk-through for deploying your store and going live: +After thorough testing in the Staging environment, merge to the Production environment and thoroughly test using live credentials. The moment you launch your production site, customers must be able to complete purchases and administrators must be able to manage the live store. We provide a detailed, clear walk-through for deploying your store and going live: - See [Deploy your store]({{ site.baseurl }}/cloud/live/stage-prod-live.html) -- See [Go live and launch]({{ site.baseurl }}/cloud/live/live.html) +- See [Site launch]({{ site.baseurl }}/cloud/live/live.html) ### Merge to Global Master diff --git a/src/cloud/basic-information/starter-architecture.md b/src/cloud/basic-information/starter-architecture.md index 9ab66b81a5c..fc5331e5192 100644 --- a/src/cloud/basic-information/starter-architecture.md +++ b/src/cloud/basic-information/starter-architecture.md @@ -19,7 +19,7 @@ The Production environment is your live store(s) and site(s). The environment in The Production environment runs your public-facing Magento single and multi-site storefronts. This system is read-only, requiring deployment across the architecture from the Integration environment to the Staging environment, and finally to the Production environment. -We walk you through [deploying to Production]({{ site.baseurl }}/cloud/live/stage-prod-live.html) and [Go Live]({{ site.baseurl }}/cloud/live/live.html) requirements and processes. +We walk you through [deploying to Production]({{ site.baseurl }}/cloud/live/stage-prod-live.html) and [launching your site]({{ site.baseurl }}/cloud/live/live.html) requirements and processes. We highly recommend fully testing in your Staging environment and branch before pushing to the `master` branch which deploys to the Production environment. diff --git a/src/cloud/basic-information/starter-develop-deploy-workflow.md b/src/cloud/basic-information/starter-develop-deploy-workflow.md index 0e2fc8f4497..c568f2f0e0f 100644 --- a/src/cloud/basic-information/starter-develop-deploy-workflow.md +++ b/src/cloud/basic-information/starter-develop-deploy-workflow.md @@ -78,7 +78,7 @@ We recommend using a branching strategy with your development work. Using one br * Integrate with a 3rd party service * Push this code, test, and merge to Staging then Production -And so on until you have your store fully built, configured, and ready to go live. But keep reading, we have even better options for your store and code configuration! +And so on until you have your store fully built, configured, and ready to launch. But keep reading, we have even better options for your store and code configuration! {:.bs-callout-info} Do not complete any configurations in your local workstation yet. @@ -203,14 +203,15 @@ To learn more, see [Deploy your store]({{ site.baseurl }}/cloud/live/stage-prod- ### Push to Master / Production {#pro} -When you push to the `master` branch, you are pushing to the Production environment. Complete configuration and testing activities in the Production environment like you did in the Staging environment with one important difference. In the Production environment use live credentials for during configuration and testing. The moment you go live and launch, customers must be able to complete purchases and administrators should be able to manage your live store. +When you push to the `master` branch, you are pushing to the Production environment. Complete configuration and testing activities in the Production environment like you did in the Staging environment with one important difference. In the Production environment use live credentials for configuration and testing. The moment you launch your site, customers must be able to complete purchases and administrators should be able to manage your live store. + To learn more, see [Deploy your store]({{ site.baseurl }}/cloud/live/stage-prod-live.html). -### Go live {#go-live} +### Site launch We provide a clear walk-through for going live and launching, which requires more steps than pressing a button. After you complete these steps, your store can serve up products in your customized theme for sale immediately. -To learn more, check out [Go live and launch]({{ site.baseurl }}/cloud/live/live.html). +To learn more, see [Site launch]({{ site.baseurl }}/cloud/live/live.html). ## Continuous integration {#continuous-integration} diff --git a/src/cloud/before/before-workspace.md b/src/cloud/before/before-workspace.md index cbe4cefad4f..e37555693b0 100644 --- a/src/cloud/before/before-workspace.md +++ b/src/cloud/before/before-workspace.md @@ -39,7 +39,7 @@ Developing code for {{site.data.var.ee}} requires working in Git branches. Not e Have the following prepared to complete your initial workspace and project setup: * {{site.data.var.ece}} account with an added user account -* Magento authentication keys from Magento Marketplace. If the Project Owner or Technical Lead created the project according to these instructions, the [Magento authentication keys]({{ site.baseurl }}/guides/v2.3/install-gde/prereq/connect-auth.html) should already be installed and available in the auth.json file in the code repository. +* Magento authentication keys from Magento Marketplace. If the License Owner or Technical Lead created the project according to these instructions, the [Magento authentication keys]({{ site.baseurl }}/guides/v2.3/install-gde/prereq/connect-auth.html) should already be installed and available in the auth.json file in the code repository. ## Get started diff --git a/src/cloud/cdn/configure-fastly.md b/src/cloud/cdn/configure-fastly.md index 9bca08546a9..2ed8b63a644 100644 --- a/src/cloud/cdn/configure-fastly.md +++ b/src/cloud/cdn/configure-fastly.md @@ -265,7 +265,7 @@ CNAME records cannot be set for apex domains, also referred to as a naked or bas - `151.101.129.124` - `151.101.193.124` -Refer to [Go live checklist]({{ site.baseurl }}/cloud/live/go-live-checklist.html) for more information. +Refer to [Go live checklist]({{ site.baseurl }}/cloud/live/site-launch-checklist.html) for more information. ### TLS and Fastly {#fastly-tls} diff --git a/src/cloud/cdn/trouble-fastly.md b/src/cloud/cdn/trouble-fastly.md index e2f7b0d4b68..7f895589185 100644 --- a/src/cloud/cdn/trouble-fastly.md +++ b/src/cloud/cdn/trouble-fastly.md @@ -113,7 +113,7 @@ If the apex domain and subdomains for your {{ site.data.var.ece }} project are a - Update the apex and subdomain configuration on the existing Fastly account. See [Multiple Fastly accounts and assigned domains]({{ site.baseurl }}/cloud/cdn/cloud-fastly.html#domain). -- [Enable and configure Fastly]({{ site.baseurl }}/cloud/cdn/configure-fastly.html#cloud-fastly-config) and complete the [DNS configuration]({{ site.baseurl }}/cloud/live/go-live-checklist.html#dns) for your project environment. +- [Enable and configure Fastly]({{ site.baseurl }}/cloud/cdn/configure-fastly.html#cloud-fastly-config) and complete the [DNS configuration]({{ site.baseurl }}/cloud/live/site-launch-checklist.html#dns) for your project environment. ## Verify or debug Fastly services diff --git a/src/cloud/docker/docker-development.md b/src/cloud/docker/docker-development.md index b4b10badd34..d35eb6b888b 100644 --- a/src/cloud/docker/docker-development.md +++ b/src/cloud/docker/docker-development.md @@ -21,11 +21,11 @@ Prior to setting up a local workspace, gather the following credentials and acco - **Magento authentication keys (Composer keys)** - Magento authentication keys are 32-character authentication tokens that provide secure access to the Magento 2 Composer repository (repo.magento.com), and any other Git services required for Magento development such as GitHub. Your account can have multiple Magento authentication keys. For the workspace setup, start with one specific key for your code repository. If you do not have any keys, contact the Project Owner to create them, or create the [Magento authentication keys] yourself. + Magento authentication keys are 32-character authentication tokens that provide secure access to the Magento 2 Composer repository (repo.magento.com), and any other Git services required for Magento development such as GitHub. Your account can have multiple Magento authentication keys. For the workspace setup, start with one specific key for your code repository. If you do not have any keys, contact the Account Owner to create them, or create the [Magento authentication keys] yourself. - **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] for details. + The License 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] for details. - **Magento Encryption Key** diff --git a/src/cloud/env/environments-start.md b/src/cloud/env/environments-start.md index 4775af44c2a..07741334ef4 100644 --- a/src/cloud/env/environments-start.md +++ b/src/cloud/env/environments-start.md @@ -48,7 +48,7 @@ Only delete an environment if you are certain that you no longer need it. You ca {:.bs-callout-warning} You cannot delete the `master` environment of any project. -You must be a [project administrator]({{ site.baseurl }}/cloud/project/user-admin.html#cloud-role-project), [environment administrator]({{ site.baseurl }}/cloud/project/user-admin.html#cloud-role-env), or [Project Owner]({{ site.baseurl }}/cloud/project/user-admin.html#cloud-role-acct-owner) to perform this task. +You must be a [project administrator]({{ site.baseurl }}/cloud/project/user-admin.html#cloud-role-project), [environment administrator]({{ site.baseurl }}/cloud/project/user-admin.html#cloud-role-env), or [Account Owner]({{ site.baseurl }}/cloud/project/user-admin.html#cloud-role-acct-owner) to perform this task. When you delete an environment, the environment is set to _inactive_. The code is still available in the Git branch, but no longer contains the services or the database. To delete the environment completely, you must also delete the corresponding remote Git branch. diff --git a/src/cloud/live/launch-steps.md b/src/cloud/live/launch-steps.md index 4f8498d806e..9df7fda7f62 100644 --- a/src/cloud/live/launch-steps.md +++ b/src/cloud/live/launch-steps.md @@ -13,19 +13,19 @@ functional_areas: {:.ref-header} Previous step -[Go live checklist]({{ site.baseurl }}/cloud/live/go-live-checklist.html) +[Go live checklist]({{ site.baseurl }}/cloud/live/site-launch-checklist.html) After testing and completing your launch checklist, you can start the final steps to launch. These steps include entering tickets, cutting over access, and finally testing your store(s) when live. Magento support staff work with you through the process, checking status, and helping if any questions or issues occur. All issues should be tracked with tickets to best capture what happened and how it was resolved. When you begin continuous iterations deploying updates to your launched store, you may have similar issues occur again. These tickets can help pinpoint the issues and help adjust your deployment tasks. -## Contact Magento to go live {#contact} +## Contact Magento to launch your site {#contact} -Contact Magento support and update any go live tickets with the intended date and time to switch over and launch your store(s). +Contact Magento support and update any site launch (go live) tickets with the intended date and time to switch over and launch your store(s). ## Switch DNS to the new site {#dns} -The Time-to-Live changed value is important for checking your changed domain. When you modify the A and CNAME records, the update will take the TTL configured time to update correctly. For details on DNS settings, see [DNS configurations]({{ site.baseurl }}/cloud/live/go-live-checklist.html#dns). +The Time-to-Live changed value is important for checking your changed domain. When you modify the A and CNAME records, the update will take the TTL configured time to update correctly. For details on DNS settings, see [DNS configurations]({{ site.baseurl }}/cloud/live/site-launch-checklist.html#dns). {:.procedure} To cut over to the new site: diff --git a/src/cloud/live/live.md b/src/cloud/live/live.md index c41bcf1e82e..c003d4c2eab 100644 --- a/src/cloud/live/live.md +++ b/src/cloud/live/live.md @@ -1,17 +1,17 @@ --- group: cloud-guide -title: Go live and launch +title: Site launch functional_areas: - Cloud --- -When you have completed deployment and testing in Integration and Staging environments, you can start going live. First, you should complete all development and testing prior to touching Production. Feel ready to launch? Review our checklists, best practices, and final steps to go live. +When you have completed deployment and testing in Integration and Staging environments, you can start going live. First, you should complete all development and testing prior to touching Production. Feel ready to launch? Review our checklists, best practices, and final steps to launch your site. If you checked this information prior to deploying and testing in Staging, consider reviewing the benefits of testing in Staging first in the next section. Staging is a near-production environment running on similar hardware, configurations, architecture, and services. It can reduce your downtime and make your extension, service, custom configurations, and merchant User Acceptance Testing vital components to releasing your sites and stores. -## Info you need to go live {#goliveinfo} +## Info you need to launch your site {#goliveinfo} -You need the following information to go live: +**Prerequisites for site launch:** * CNAME record information for configuring the DNS * List of all storefront domains to add to the certificate @@ -89,9 +89,9 @@ Scan results include a label that describes scan pass or fail status with detail The scan results also provide suggested remediation steps for each failed security test. Security scan results are protected and viewable only by the registered user. Only users designated in the site registration process receive scan completion notifications. -## Ready to go live {#ready} +## Ready to launch your site {#ready} -When you are ready to begin the go-live process, see the following: +When you are ready to begin the site launch process, see the following: -* [Go live checklist]({{ site.baseurl }}/cloud/live/go-live-checklist.html) +* [Launch checklist]({{ site.baseurl }}/cloud/live/site-launch-checklist.html) * [Launch steps]({{ site.baseurl }}/cloud/live/launch-steps.html) diff --git a/src/cloud/live/go-live-checklist.md b/src/cloud/live/site-launch-checklist.md similarity index 92% rename from src/cloud/live/go-live-checklist.md rename to src/cloud/live/site-launch-checklist.md index cdf41bf33b0..271d119c87e 100644 --- a/src/cloud/live/go-live-checklist.md +++ b/src/cloud/live/site-launch-checklist.md @@ -1,12 +1,16 @@ --- group: cloud-guide -title: Go live checklist +title: Launch checklist functional_areas: - Cloud - Testing + +redirect_from: + - /common/pdf/magento-commerce-cloud-prelaunch-checklist.pdf + - /cloud/live/go-live-checklist.html --- -Before you deploy to the Production environment, download the [Go live checklist]({{ site.downloads }}/magento-commerce-cloud-prelaunch-checklist.pdf), and use it with these instructions to confirm that you have completed all required configuration and testing. See an overview of the complete deployment process for Starter and Pro at [Deploy your store]({{ site.baseurl }}/cloud/live/stage-prod-live.html). +Before you deploy to the Production environment, download the [Launch checklist]({{ site.downloads }}/magento-commerce-cloud-prelaunch-checklist.pdf), and use it with these instructions to confirm that you have completed all required configuration and testing. See an overview of the complete deployment process for Starter and Pro at [Deploy your store]({{ site.baseurl }}/cloud/live/stage-prod-live.html). ## Completely test in Production {#test} diff --git a/src/cloud/live/stage-prod-live.md b/src/cloud/live/stage-prod-live.md index 46c21b59b3e..5f87d7d3959 100644 --- a/src/cloud/live/stage-prod-live.md +++ b/src/cloud/live/stage-prod-live.md @@ -25,7 +25,7 @@ Now you are ready to develop and deploy: 1. Push your local branch to the Git remote branch to test in a full environment. 1. To fully test in a near-production level environment, push code to a Staging branch. 1. Fully test in the Staging environment including payment gateways, shipping, price rules, various products, and full customer and admin interactions. -1. Finally, deploy to the Production `master` to complete testing, go live steps, and start selling. +1. Finally, deploy to the Production `master` to complete testing, site launch steps, and start selling. For detailed information of the process, see [Starter Develop and Deploy Workflow]({{ site.baseurl }}/cloud/basic-information/starter-develop-deploy-workflow.html). @@ -39,7 +39,7 @@ Pro comes with a large Integration environment with eight active branches and en 1. Merge final code to the Integration `master` branch. 1. To fully test in a near-production level environment, push code to the Staging environment. 1. Fully test in the Staging environment including payment gateways, shipping, price rules, various products, and full customer and admin interactions. -1. Finally, deploy to the Production environment to complete testing, go live steps, and start selling. +1. Finally, deploy to the Production environment to complete testing, site launch steps, and start selling. For detailed information of the process, see [Pro Develop and Deploy Workflow]({{ site.baseurl }}/cloud/architecture/pro-develop-deploy-workflow.html). @@ -80,4 +80,4 @@ To learn more, check the following: * [Prepare to deploy]({{ site.baseurl }}/cloud/live/stage-prod-migrate-prereq.html) * [Migrate and deploy]({{ site.baseurl }}/cloud/live/stage-prod-migrate.html) * [Test deployment]({{ site.baseurl }}/cloud/live/stage-prod-test.html) -* [Go live and launch]({{ site.baseurl }}/cloud/live/live.html) +* [Site launch]({{ site.baseurl }}/cloud/live/live.html) diff --git a/src/cloud/onboarding/onboarding-portal.md b/src/cloud/onboarding/onboarding-portal.md index 89693a5e5ae..b0ee887fc3f 100644 --- a/src/cloud/onboarding/onboarding-portal.md +++ b/src/cloud/onboarding/onboarding-portal.md @@ -82,4 +82,5 @@ The technical admin, technical users, developers, and others can directly access When you are ready to launch your sites and stores, work through Launch options: * **UAT Checklist**: A high-level checklist for verifying Magento features and your configured settings, extensions, products, and more. You can follow this checklist along with the [Test deployment]({{ site.baseurl }}/cloud/live/stage-prod-test.html) information. -* **Site Launch**: A high-level checklist for your initial "go live". After completing the checklist, you can enter Live Site Configuration information to enter a Submit a Support ticket. You can follow this checklist along with the [Go live checklist]({{ site.baseurl }}/cloud/live/go-live-checklist.html) and [Test deployment]({{ site.baseurl }}/cloud/live/stage-prod-test.html) information. \ No newline at end of file + +* **Site Launch**: A high-level checklist for your initial "go live". After completing the checklist, you can enter Live Site Configuration information to enter a Submit a Support ticket. You can follow this checklist along with the [Go live checklist]({{ site.baseurl }}/cloud/live/site-launch-checklist.html) and [Test deployment]({{ site.baseurl }}/cloud/live/stage-prod-test.html) information. diff --git a/src/cloud/project/project-upgrade.md b/src/cloud/project/project-upgrade.md index 43fb0aa84f5..2ab28405a15 100644 --- a/src/cloud/project/project-upgrade.md +++ b/src/cloud/project/project-upgrade.md @@ -198,7 +198,7 @@ To verify and upgrade your extensions: 1. Push to the Staging environment to test in a pre-production environment. -We strongly recommend upgrading your Production environment _before_ including the upgraded extensions in your go-live process. +We strongly recommend upgrading your Production environment _before_ including the upgraded extensions in your site launch process. {:.bs-callout-info} When you upgrade your Magento version, the upgrade process updates to the latest version of the [Fastly CDN module for Magento 2] automatically. diff --git a/src/cloud/project/projects.md b/src/cloud/project/projects.md index e3c0e731c6f..b157d3c75e8 100644 --- a/src/cloud/project/projects.md +++ b/src/cloud/project/projects.md @@ -67,7 +67,7 @@ To review your integration tokens, IDs, and more: ## Access the project and environments {#project} -When you first login, a list of projects you have access to displays. As a Project Owner, you may only see your company's project. A Magento Solution Partner may see multiple projects for all of the clients they support. +When you first login, a list of projects you have access to displays. As an Account Owner, you can only see your company's project. A Magento Solution Partner may see multiple projects for all of the clients they support. Click on a project to access branches and more. On the page, you will see a hierarchy of environments named by the Git branch. @@ -84,7 +84,7 @@ The following table details the branches for Pro: | Branch | Environment | Description | |---------- | (no branch) | Global Master | This "branch" captures global project changes including adding user accounts and variables. **Important:** Do not create branches from or merge to Global Master. | -| `production` | Production | This is a child branch from `master` with a deployment target. You cannot branch from this branch. You merge code from `master` to this branch to go live with updated configurations and code. | +| `production` | Production | This is a child branch from `master` with a deployment target. You cannot branch from this branch. You merge code from `master` to this branch to launch your site with updated configurations and code. | | `staging` | Staging | This is a child branch from `master` with a deployment target. You cannot branch from this branch. You merge code from `master` to this branch to test in a pre-production environment. | | `master` | Integration master | The master branch of the single repository. In the Project Web Interface, this is called Integration. You branch from `master` for your development on your local, generating an environment when you push code. When this code is complete, you merge to `staging` and `production`. | diff --git a/src/cloud/reference/discover-deploy.md b/src/cloud/reference/discover-deploy.md index cb9816e368a..dbd996148bb 100644 --- a/src/cloud/reference/discover-deploy.md +++ b/src/cloud/reference/discover-deploy.md @@ -12,7 +12,7 @@ Build and deploy scripts activate when you merge code to a remote environment. The build and deploy process is slightly different for each plan: -- **Starter plans**—For the Integration environment, every active branch builds and deploys to a full environment for access and testing. Fully test your code after merging to the `staging` branch. To go live, push `staging` to `master` to deploy to the Production environment. You have full access to all branches through the Project Web Interface and the CLI commands. +- **Starter plans**—For the Integration environment, every active branch builds and deploys to a full environment for access and testing. Fully test your code after merging to the `staging` branch. To launch your site, push `staging` to `master` to deploy to the Production environment. You have full access to all branches through the Project Web Interface and the CLI commands. - **Pro plans**—For the Integration environment, every _active_ branch builds and deploys to a full environment for access and testing. You must merge your code to the `integration` branch before you can merge to the Staging environment and then the Production environment. You can merge to the Staging and Production environments using the Project Web Interface or using SSH and Magento Cloud CLI commands. @@ -254,4 +254,4 @@ With an understanding of the process, we provide the following instructions for - [Prepare to deploy]({{ site.baseurl }}/cloud/live/stage-prod-migrate-prereq.html) - [Deploy code and data]({{ site.baseurl }}/cloud/live/stage-prod-migrate.html) - [Test deployment]({{ site.baseurl }}/cloud/live/stage-prod-test.html) -- [Go live and launch]({{ site.baseurl }}/cloud/live/live.html) +- [Site launch]({{ site.baseurl }}/cloud/live/live.html) diff --git a/src/cloud/requirements/cloud-requirements.md b/src/cloud/requirements/cloud-requirements.md index 41369b57376..fa131f4d334 100644 --- a/src/cloud/requirements/cloud-requirements.md +++ b/src/cloud/requirements/cloud-requirements.md @@ -77,7 +77,7 @@ To get started as a developer in a {{site.data.var.ece}} project, you need to se * Set up a [local development environment]({{ site.baseurl }}/cloud/before/before-workspace.html). Your local workspace works best as a virtual system (VM or container) with all prerequisites installed and the project `master` Git branch cloned. You'll develop in branches to add modules, extensions, 3rd party integrations, and configurations. We recommend reading over develop and deploy process for your [Starter]({{ site.baseurl }}/cloud/basic-information/starter-develop-deploy-workflow.html) or [Pro]({{ site.baseurl }}/cloud/architecture/pro-develop-deploy-workflow.html) plan. * Get [`repo.magento.com` credentials]({{ site.baseurl }}/guides/v2.3/install-gde/prereq/connect-auth.html) in your account. -* Get a [project invitation]({{ site.baseurl }}/cloud/onboarding/onboarding-tasks.html#users) from the Project Owner or a super user. +* Get a [project invitation]({{ site.baseurl }}/cloud/onboarding/onboarding-tasks.html#users) from the Account Owner or a super user. We walk you through everything you need to do and know. diff --git a/src/cloud/setup/first-time-setup.md b/src/cloud/setup/first-time-setup.md index 23896101673..3dbb34d14e2 100644 --- a/src/cloud/setup/first-time-setup.md +++ b/src/cloud/setup/first-time-setup.md @@ -19,10 +19,10 @@ Prior to setting up a workspace, gather the following credentials and accounts: - **Magento authentication keys (Composer keys)** - Magento authentication keys are 32-character authentication tokens that provide secure access to the Magento 2 Composer repository (repo.magento.com), and any other Git services required for Magento development such as GitHub. Your account can have multiple Magento authentication keys. For the workspace setup, start with one specific key for your code repository. If you do not have any keys, contact the Project Owner to create them, or create the [Magento authentication keys] yourself. + Magento authentication keys are 32-character authentication tokens that provide secure access to the Magento 2 Composer repository (repo.magento.com), and any other Git services required for Magento development such as GitHub. Your account can have multiple Magento authentication keys. For the workspace setup, start with one specific key for your code repository. If you do not have any keys, contact the Account Owner to create them, or create the [Magento authentication keys] yourself. - **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]({{ site.baseurl }}/cloud/before/before-workspace.html#newaccount) for details. + The Account 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]({{ site.baseurl }}/cloud/before/before-workspace.html#newaccount) for details. - **Magento Encryption Key** When importing an existing Magento system only, 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]({{ site.baseurl }}/cloud/trouble/trouble-crypt-key-variable.html)