This repository has been archived by the owner on Nov 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'develop' of https://github.com/magento/devdocs_internal …
…into functional_areas # Conflicts: # common/js/app.min.js # css/app.css
- Loading branch information
Showing
834 changed files
with
3,576 additions
and
870 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
<div markdown="1"> | ||
|
||
You can also use SSH tunneling to connect to a service from your local development environment as if the service were local. Before tunneling, you need to have [SSH configured]({{ page.baseurl }}cloud/env/environments-ssh.html). | ||
|
||
Use a terminal application to log in and issue commands. | ||
|
||
magento-cloud login | ||
|
||
First, you may want to check if any tunnels are already open using the following command: | ||
|
||
magento-cloud tunnel:list | ||
|
||
To build a tunnel, you must know the name of the app to which to tunnel. Use the following commands to list those applications: | ||
|
||
cd <project directory> | ||
magento-cloud project:list | ||
magento-cloud apps | ||
|
||
For information on the command, you can enter `magento-cloud apps --help`. | ||
|
||
### Set up the SSH tunnel {#tunnel-setup} | ||
Use the following command: | ||
|
||
magento-cloud tunnel:open -e <environment ID> --app <app name> | ||
|
||
For example, to open a tunnel to the `sprint5` branch in a project with an app named `mymagento`, enter | ||
|
||
magento-cloud tunnel:open -e sprint5 --app mymagento | ||
|
||
Messages similar to the following display: | ||
|
||
SSH tunnel opened on port 30003 to relationship: solr | ||
SSH tunnel opened on port 30004 to relationship: redis | ||
SSH tunnel opened on port 30005 to relationship: database | ||
Logs are written to: /home/magento_user/.magento/tunnels.log | ||
|
||
List tunnels with: magento-cloud tunnels | ||
View tunnel details with: magento-cloud tunnel:info | ||
Close tunnels with: magento-cloud tunnel:close | ||
|
||
### Get tunnel information {#tunnel-info} | ||
To display information about your tunnel, enter: | ||
|
||
magento-cloud tunnel:info -e <environment ID> | ||
|
||
### Connect to services {#tunnel-services} | ||
Now you can connect to services as if they were running locally. | ||
|
||
For example, to connect to the database, use the following command: | ||
|
||
mysql --host=127.0.0.1 --user='<database user name>' --pass='<user password>' --database='<name>' --port='<port>' | ||
|
||
Details about the service display if you use the `magento-cloud tunnel:info` command. |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,9 @@ | ||
<div markdown="1"> | ||
|
||
<div class="bs-callout bs-callout-info" id="info" markdown="1"> | ||
**Updating your Pro project** | ||
These sections include instructions for Pro projects updated to manage Staging and Production through the Project Web Interface. For more information adding this management to existing Pro projects (created before October 23, 2017), see [Add Staging and Production to Pro projects UI]({{page.baseurl}}cloud/trouble/pro-env-management.html). | ||
**Updating your Pro project**: These sections include instructions for Pro projects with Staging and Production available in the Project Web Interface. To add Staging and Production to your interface, see [Add Staging and Production to Pro projects UI]({{page.baseurl}}cloud/trouble/pro-env-management.html). | ||
|
||
We can update Pro projects created before October 23, 2017. All new Pro projects include these features. Your ticket will be queued for update, which may take time to complete. We will keep you updated through the process. | ||
|
||
If you do not request this update, you must use CLI commands or tickets to modify settings, variables, routes, and more for Pro plan Staging and Production environments. | ||
</div> |
This file contains 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
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.