You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: src/cloud/project/project-multi-sites.md
+9-6Lines changed: 9 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ functional_areas:
11
11
You can configure {{site.data.var.ee}} to have multiple websites or stores, such as an English store, a French store, and a German store. See [Understanding websites, stores, and store views]({{ site.baseurl }}/cloud/configure/configure-best-practices.html#sites).
12
12
13
13
{:.bs-callout-warning}
14
-
Be aware that catalog data expands as you increase the number of websites and stores. Depending on your project architecture, the additional stores can lead to a longer indexing process and slower response times for non-cached catalog pages. Adobe recommends that you monitor site performance closely.
14
+
Catalog data expands as you increase the number of websites and stores. Depending on your project architecture, the additional stores can lead to a longer indexing process and slower response times for non-cached catalog pages. Adobe recommends that you monitor site performance closely.
15
15
16
16
The process to set up multiple stores depends on whether you choose to use unique or shared domains.
17
17
@@ -36,15 +36,17 @@ To add a store view to the site base URL, you do not have to create multiple dir
36
36
37
37
## Add New Domains
38
38
39
-
The process to add a new domain depends on the type of Cloud account:
39
+
Custom domains can be added to Pro Staging and any Production environment; they cannot be added to Integration environments.
40
40
41
-
- For Pro
41
+
The process to add a domain depends on the type of Cloud account:
42
42
43
-
You must open a Support ticket to request new domains to be added to the cluster.
43
+
- For Pro Staging and Production
44
44
45
-
- For Starter
45
+
Add the new domain to Fastly, see [Manage domains][], or open a support ticket to request assistance. In addition, you must open a Support ticket to request new domains to be added to a cluster.
46
46
47
-
You can add the new domain to Fastly for Production, or you can create a support ticket to request assistance. You must add the new domain to the **Domains** tab in the Program UI: `https://<zone>.magento.cloud/projects/<project-ID>/edit`
47
+
- For Starter Production only
48
+
49
+
Add the new domain to Fastly, see [Manage domains][], or open a support ticket to request assistance. In addition, you must add the new domain to the **Domains** tab in the Project Web Interface: `https://<zone>.magento.cloud/projects/<project-ID>/edit`
48
50
49
51
## Configure local installation
50
52
@@ -337,3 +339,4 @@ Adobe recommends fully testing in the Staging environment before pushing to the
Copy file name to clipboardExpand all lines: src/cloud/project/project-upgrade.md
-3Lines changed: 0 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,6 @@ Review the [{{site.data.var.ece}} service versions][version compatibility matrix
22
22
- Upgrade third-party extensions to the latest supported version.
23
23
- Update the `.gitignore` file.
24
24
25
-
{:.bs-callout-info}
26
-
If you upgrade the PHP version, you must also submit a Support ticket to update the New Relic service.
27
-
28
25
### Configuration management
29
26
30
27
Older versions of {{site.data.var.ee}}, such as 2.1.4 or later to 2.2.x or later, used a `config.local.php` file for Configuration Management. {{site.data.var.ee}} version 2.2.0 and later use the `config.php` file, which works exactly like the `config.local.php` file, but it has different configuration settings that include a list of your enabled modules and additional configuration options.
The `mysql` service provides persistent data storage based on [MariaDB](https://mariadb.com/) versions 10.2-10.4, supporting the [XtraDB](https://www.percona.com/software/mysql-database/percona-server/xtradb) storage engine and reimplemented features from MySQL 5.6 and 5.7.
11
+
The `mysql` service provides persistent data storage based on [MariaDB](https://mariadb.com/) versions 10.2 to 10.4, supporting the [XtraDB](https://www.percona.com/software/mysql-database/percona-server/xtradb) storage engine and reimplemented features from MySQL 5.6 and 5.7.
12
12
13
13
{% include install/maria-db.md %}
14
14
15
15
{:.bs-callout-warning}
16
16
Be careful when upgrading MariaDB from version 10.1 to 10.2.
17
-
MariaDB 10.1 is the last version that support XtraDB as the storage engine. Version 10.2 uses InnoDB for the storage engine. Once you upgrade from 10.1 to 10.2, you cannot rollback the change. {{site.data.var.ee}} supports both storage engines; however, you must check extensions and other systems used by your project to make sure they are compatible with MariaDB 10.2. Read about this [backwards incompatible change](https://mariadb.com/kb/en/upgrading-from-mariadb-101-to-mariadb-102/#incompatible-changes-between-101-and-102).
17
+
MariaDB 10.1 is the last version that supports XtraDB as the storage engine. Version 10.2 uses InnoDB for the storage engine. Once you upgrade from 10.1 to 10.2, you cannot rollback the change. {{site.data.var.ee}} supports both storage engines; however, you must check extensions and other systems used by your project to make sure they are compatible with MariaDB 10.2. Read about this [backwards incompatible change](https://mariadb.com/kb/en/upgrading-from-mariadb-101-to-mariadb-102/#incompatible-changes-between-101-and-102).
18
18
19
19
{% include cloud/service-config-integration-starter.md %}
20
20
@@ -50,12 +50,12 @@ MariaDB 10.1 is the last version that support XtraDB as the storage engine. Vers
50
50
51
51
## Set up multiple database users
52
52
53
-
Optionally, you can set up multiple databases as well as multiple users with different permissions.
53
+
Optionally, you can set up multiple databases and multiple users with different permissions.
54
54
55
-
An _endpoint_ is a set of credentials (or users) with specific privileges. By default, there is one endpoint named `mysql` that has administrator access to all defined databases. To set up multiple database users, you must define multiple endpoints in the services.yaml file and declare the relationships in the .magento.app.yaml file.
55
+
An _endpoint_ is a set of credentials (or users) with specific privileges. By default, there is one endpoint named `mysql` that has administrator access to all defined databases. To set up multiple database users, you must define multiple endpoints in the services.yaml file and declare the relationships in the `.magento.app.yaml` file. For Pro Staging and Production environments, submit a Support ticket to request the additional user.
56
56
57
57
{:.bs-callout-warning}
58
-
You cannot use multiple _databases_ with {{site.data.var.ee}} at this time, but you **can** create multiple endpoints to restrict access to the `main` database.
58
+
You cannot use multiple _databases_ with {{site.data.var.ee}}, but you **can** create multiple endpoints to restrict access to the `main` database.
59
59
60
60
Use a nested array to define the endpoints for specific user access. Each endpoint can designate access to one or more schemas (databases) and different levels of permission on each.
61
61
@@ -87,13 +87,13 @@ mysql:
87
87
main: rw
88
88
```
89
89
90
-
In the preceding example, the `admin` endpoint provides admin-level access to the `main` database, the `reporter` endpoint provides read-only access, and the `importer` endpoint provides read-write access. This means that:
90
+
In the preceding example, the `admin` endpoint provides admin-level access to the `main` database, the `reporter` endpoint provides read-only access, and the `importer` endpoint provides read-write access, which means:
91
91
92
92
- The `admin` user has full control of the database.
93
93
- The `reporter` user has SELECT privileges only.
94
94
- The `importer` user has SELECT, INSERT, UPDATE, and DELETE privileges.
95
95
96
-
You must add the endpoints defined in the above example to the `relationships` property of the `.magento.app.yaml` file. For example:
96
+
Add the endpoints defined in the above example to the `relationships` property of the `.magento.app.yaml` file. For example:
97
97
98
98
```yaml
99
99
relationships:
@@ -103,13 +103,17 @@ relationships:
103
103
```
104
104
105
105
{:.bs-callout-info}
106
-
If you configure one MySQL user, you cannot use the [`DEFINER`](http://dev.mysql.com/doc/refman/5.6/en/show-grants.html) access control mechanism for stored procedures and views.
106
+
If you configure one MySQL user, you cannot use the [`DEFINER`](https://dev.mysql.com/doc/refman/5.6/en/show-grants.html) access control mechanism for stored procedures and views.
107
107
108
108
## Connect to the database
109
109
110
-
Accessing the MariaDB database directly requires you to use a SSH to log in to the remote server, and connect to the database.
110
+
Accessing the MariaDB database directly requires you to use a SSH to log in to the remote Cloud environment, and connect to the database.
111
111
112
-
1. Log in to the remote server using SSH.
112
+
1. Use SSH to log in to the remote environment.
113
+
114
+
```bash
115
+
magento-cloud ssh
116
+
```
113
117
114
118
1. Retrieve the MySQL login credentials from the `database` and `type` properties in the [$MAGENTO_CLOUD_RELATIONSHIPS]({{ site.baseurl }}/cloud/project/magento-app-properties.html#relationships) variable.
115
119
@@ -147,7 +151,7 @@ Accessing the MariaDB database directly requires you to use a SSH to log in to t
147
151
],
148
152
```
149
153
150
-
1. Connect to the database:
154
+
1. Connect to the database.
151
155
152
156
- For Starter, use the following command:
153
157
@@ -161,13 +165,16 @@ Accessing the MariaDB database directly requires you to use a SSH to log in to t
161
165
mysql -h <hostname> -P <number> -u <username> -p'<password>'
162
166
```
163
167
168
+
{:.bs-callout-tip}
169
+
You can use the `magento-cloud db:sql` command to connect to the remote database and run SQL commands.
170
+
164
171
## Connect to secondary database
165
172
166
-
In some cases, you might need to connect to the secondary database, for example to improve database performance or resolve database locking issues. If this configuration is required, use `"port" : 3304` to establish the connection. See the [{{ site.data.var.ece }} database best practice](https://support.magento.com/hc/en-us/articles/360049045351) article in the _{{site.data.var.ee}} Help Center_.
173
+
Sometimes, you have to connect to the secondary database to improve database performance or resolve database locking issues. If this configuration is required, use `"port" : 3304` to establish the connection. See the [{{ site.data.var.ece }} database best practice](https://support.magento.com/hc/en-us/articles/360049045351) article in the _{{site.data.var.ee}} Help Center_.
167
174
168
175
## Troubleshooting
169
176
170
-
See the following {{site.data.var.ee}} Support articles for help troubleshooting MySQL problems:
177
+
See the following {{site.data.var.ee}} Support articles for help with troubleshooting MySQL problems:
171
178
172
179
- [Checking slow queries and processes MySQL](https://support.magento.com/hc/en-us/articles/360030903091-Checking-slow-queries-and-processes-MySQL-)
173
180
- [Create database dump on Cloud](https://support.magento.com/hc/en-us/articles/360003254334-Create-database-dump-on-Cloud)
0 commit comments