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
Copy file name to clipboardExpand all lines: basics/keeping-up-to-date/migration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,7 +165,7 @@ mysql> SHOW VARIABLES LIKE "secure_file_priv";
165
165
#### Get changes between source and destination databases
166
166
Now you have retrieved your data from the production shop, you have to adapt it to the new structure before inserting it on your new database.
167
167
168
-
An efficient way to get the changes is getting a database structure diff between the 2 running shops. MySQL provides another tool for this called [mysqldiff](https://docs.oracle.com/cd/E17952_01/mysql-utilities-1.5-en/mysqldiff.html).
168
+
An efficient way to get the changes is getting a database structure diff between the 2 running shops. MySQL provides another tool for this called [mysqldiff](https://downloads.mysql.com/docs/mysql-utilities-1.5-en.pdf).
169
169
170
170
Note this utility may be not immediately available on your environment, even if you have the mysql client installed. For instance on Ubuntu, an additional package needs to be installed:
- Use [interactive staging](https://git-scm.com/book/en/v2/Git-Tools-Interactive-Staging) when you have made several changes in the same file but not all those changes are meant to be in a single commit.
52
52
- Consider [squashing your commits](https://www.atlassian.com/git/tutorials/rewriting-history#git-rebase-i) as necessary, especially when you have performed many changes following code review.
53
-
- **Avoid merge commits in your Pull Request.** They make the commit history more difficult to understand, and they can lead to hidden changes which are not visible by reviewers. If you need to resolve conflicts with the base branch, [rebase your branch](https://anavarre.net/how-to-rebase-a-github-pull-request/) instead.
53
+
- **Avoid merge commits in your Pull Request.** They make the commit history more difficult to understand, and they can lead to hidden changes which are not visible by reviewers. If you need to resolve conflicts with the base branch, [rebase your branch](https://github.com/spyder-ide/spyder/wiki/How-to-rebase-a-pull-request) instead.
The module created within this tutorial can be found [here](https://github.com/PrestaShop/demo-cqrs-hooks-usage-module)
19
+
The module created within this tutorial can be found [here](https://github.com/PrestaShop/example-modules/tree/master/demoextendsymfonyform3)
20
20
21
21
## Prerequisites
22
22
@@ -138,7 +138,7 @@ class CustomerReviewController extends FrameworkBundleAdminController
138
138
{{% notice note %}}
139
139
**This example has been simplified for practical reasons.**
140
140
141
-
You can find full implementation [here](https://github.com/PrestaShop/demo-cqrs-hooks-usage-module) which uses CQRS pattern to toggle the reviewer state. [More about it here]({{< relref "/9/development/architecture/domain/cqrs" >}}).
141
+
You can find full implementation [here](https://github.com/PrestaShop/example-modules/tree/master/demoextendsymfonyform3) which uses CQRS pattern to toggle the reviewer state. [More about it here]({{< relref "/9/development/architecture/domain/cqrs" >}}).
142
142
{{% /notice %}}
143
143
144
144
```php
@@ -251,7 +251,7 @@ about it can be found [here]({{< relref "/9/development/components/form/types-re
251
251
{{% notice note %}}
252
252
**This example has been simplified for practical reasons.**
253
253
254
-
You can find full implementation [here](https://github.com/PrestaShop/demo-cqrs-hooks-usage-module) which uses CQRS pattern to get reviewer state. [More about it here]({{< relref "/9/development/architecture/domain/cqrs" >}}).
254
+
You can find full implementation [here](https://github.com/PrestaShop/example-modules/tree/master/demoextendsymfonyform3) which uses CQRS pattern to get reviewer state. [More about it here]({{< relref "/9/development/architecture/domain/cqrs" >}}).
255
255
{{% /notice %}}
256
256
257
257
```php
@@ -310,7 +310,7 @@ dedicated to handle this topic - lets do that!
310
310
{{% notice note %}}
311
311
**This example has been simplified for practical reasons.**
312
312
313
-
You can find full implementation [here](https://github.com/PrestaShop/demo-cqrs-hooks-usage-module) which uses CQRS pattern to create or update reviewer state. [More about it here]({{< relref "/9/development/architecture/domain/cqrs" >}}).
313
+
You can find full implementation [here](https://github.com/PrestaShop/example-modules/tree/master/demoextendsymfonyform3) which uses CQRS pattern to create or update reviewer state. [More about it here]({{< relref "/9/development/architecture/domain/cqrs" >}}).
Copy file name to clipboardExpand all lines: scale/benchmark/back-office.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -173,7 +173,7 @@ You could then write your own `batch.sh` to run multiple gatling benchmarks.
173
173
174
174
### Gatling installation
175
175
176
-
Download Gatling from **[here](https://gatling.io/download/)**, and in the same way have a look at **[the Gatling quickstart page](https://gatling.io/docs/current/quickstart/)**.
176
+
Download Gatling from **[here](https://gatling.io/download-gatling-community-edition)**, and in the same way have a look at **[the Gatling quickstart page](https://docs.gatling.io/tutorials/)**.
177
177
178
178
Once unzipping the folder it will look like as shown below:
0 commit comments