Skip to content

Commit 3a5abad

Browse files
committed
Fixup documents with needs_review: true
1 parent 348595e commit 3a5abad

File tree

4 files changed

+18
-43
lines changed

4 files changed

+18
-43
lines changed

docs/ecommerce-applications/magento-1/how-to-reset-your-magento-1-x-admin-password.md

Lines changed: 11 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@ myst:
44
description: If you are unable to login to your Magento shop, you have several
55
methods to retrieve a new password to log back in. Check out here how to reset
66
your password.
7-
needs_review: true
87
---
98

109
<!-- source: https://support.hypernode.com/en/support/solutions/articles/48000970831-how-to-reset-your-magento-1-x-admin-password/ -->
@@ -28,9 +27,9 @@ Visit your Magento admin backend in a browser, and click the link **Forgot your
2827

2928
Next insert your email address and press the **Retrieve Password** button.
3029

31-
An email will be send to your email address, containing a password reset link.
30+
An email will be sent to your email address, containing a password reset link.
3231

33-
An email will be send to your email address, containing a password reset link. Click the **RESET PASSWORD** link, or paste the link in your browser.
32+
An email will be sent to your email address, containing a password reset link. Click the **RESET PASSWORD** link, or paste the link in your browser.
3433

3534
You then will be asked to insert a new password. Insert the password twice and click the **Reset Password** button to save your changes.
3635

@@ -50,7 +49,7 @@ To reset a password through the Magento backend, access the backend in your brow
5049

5150
From the **My Account** management page, insert your **current password** and second, insert your new password twice. After that, click the **Save Account** Button in the top-right corner of the page.
5251

53-
### Reset Someone Elses Password Using the Magento Admin Backend
52+
### Reset Someone Else's Password Using the Magento Admin Backend
5453

5554
To reset another users credentials, insert the name of the particular user, first, select `System` -> `Permissions` -> `Users`.
5655

@@ -67,37 +66,31 @@ The `magerun` Magento management commandline utility provides a plugin to create
6766
```bash
6867
cd ~/public
6968
magerun admin:user:change-password [username]
70-
7169
```
7270

7371
This will show a password prompt. Insert the password and test if you can login on the webinterface. The plugin does not ask for a confirmation, so it might be smart to test the password right after changing it.
7472

7573
## Change the Password Directly in the Database
7674

77-
Additionally you can change the passwords for admin users directly in the database. This is for experts only and not the easiers way. If you are not familiar with using MySQL, use the `magerun` plugin.
75+
Additionally you can change the passwords for admin users directly in the database. This is for experts only and not the easier way. If you are not familiar with using MySQL, use the `magerun` plugin.
7876

7977
### Set a New Password Using phpMyAdmin
8078

8179
First, log in to phpMyAdmin:
8280

83-
- Go to phpMyAdmin on the hypernode by visitting <http://appname.hypernode.io/phpmyadmin> or by clicking the link in our service panel.
81+
- Go to phpMyAdmin on the hypernode by visiting <http://appname.hypernode.io/phpmyadmin> or by clicking the link in our service panel.
8482
- Login with the username and password in `~/.my.cnf`
85-
- Select the prod database in the left side panel.
83+
- Select the prod database on the left side panel.
8684
- In the top bar, select the `SQL` tab.
8785

8886
Next, follow the instructions below:
8987

9088
- Paste the following query:
91-
92-
```mysql
93-
UPDATE admin_user SET password = CONCAT(MD5('$SALT$PASSWORD'), ':$SALT') WHERE username = '$USERNAME';
94-
```
95-
96-
```
97-
+ Replace `$PASSWORD` with the new admin password and replace `$USERNAME` with the username you want to change the password for.
98-
+ Replace `$SALT` with a random string of characters. Use the same random string in both parts of the SQL query. The string should be just 2 characters.
99-
```
100-
89+
```mysql
90+
UPDATE admin_user SET password = CONCAT(MD5('$SALT$PASSWORD'), ':$SALT') WHERE username = '$USERNAME';
91+
```
92+
- Replace `$PASSWORD` with the new admin password and replace `$USERNAME` with the username you want to change the password for.
93+
- Replace `$SALT` with a random string of characters. Use the same random string in both parts of the SQL query. The string should be just 2 characters.
10194
- Click `Go` to execute the query, and login with the given username using the new password.
10295

10396
If your Magento 1 shop uses table prefixes add the prefix to your table name. IE: If your table prefix is mage\_, use the following query instead:
@@ -118,5 +111,4 @@ export PASSWORD="Randompassword123"
118111
export DATABASE="magento_live"
119112
export TABLE_PREFIX="mage_"
120113
export SALT="$( < /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c${1:-32};echo; )" ## Or pick your own random password
121-
122114
```

docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,6 @@ To do this, run the following command:
7777

7878
```console
7979
$ cd /data/web/magento2;
80-
$ chmod 750 bin/magento;
8180
$ bin/magento setup:config:set --http-cache-hosts=127.0.0.1:6081;
8281
```
8382

docs/ecommerce-applications/shopware-6/how-to-configure-redis-for-shopware-6.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
needs_review: true
3-
---
4-
51
<!-- source: https://support.hypernode.com/en/support/solutions/articles/48001200521-how-to-configure-redis-for-shopware-6/ -->
62

73
# How to Configure Redis for Shopware 6
@@ -12,8 +8,8 @@ Redis is a caching method which can increase the speed of the backend and fronte
128

139
Add the following line to the .env file:
1410

15-
```nginx
16-
REDIS_URL=redis://localhost/<database ID>
11+
```bash
12+
REDIS_URL=redis://localhost:6379/1
1713
```
1814

1915
## Step Two: Create the framework.yml File

docs/troubleshooting/performance/how-to-implement-pagespeed-booster.md

Lines changed: 5 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,6 @@ myst:
33
html_meta:
44
description: PageSpeed Booster is a reverse proxy which uses many static optimisation
55
techniques to greatly increase the pagespeed score and performance of your website.
6-
needs_review: true
76
---
87

98
<!-- source: https://support.hypernode.com/en/troubleshooting/performance/how-to-implement-pagespeed-booster/ -->
@@ -15,7 +14,7 @@ needs_review: true
1514
To get started with the PageSpeed Booster (formerly known as Percolate), you must meet the following requirements:
1615

1716
- ***Production environment that is hosted on Hypernode.***
18-
- ***Dev environment that is a copy of live and hosted on Hypernode.***
17+
- ***Development/staging environment that is a copy of live and hosted on Hypernode.***
1918
- ***Varnish has to be enabled***
2019
- ***Time to thoroughly test the environment with PageSpeed Booster enabled.***
2120

@@ -141,22 +140,11 @@ varnishadm vcl.use psb
141140

142141
With the addition of Pagespeed booster, you'll have to deal with an extra layer of cache that needs to be flushed when demanded.
143142

144-
Add your Pagespeed booster URL as entry to the **http_cache_hosts** section in your **env.php**:
143+
Add your Pagespeed booster URL to your Magento `http_cache_hosts` configuration:
145144

146-
******app/etc/env.php******
147-
148-
```
149-
******'http_cache_hosts' => [
150-
[
151-
'host' => '127.0.0.1',
152-
'port' => '6081'
153-
],
154-
// PSB
155-
[
156-
'host' => 'appname-appname.fsn1.percolate-3.hipex.cloud',
157-
'port' => '80'
158-
]
159-
],******
145+
```bash
146+
bin/magento setup:config:set \
147+
--http-cache-hosts=varnish:6081,appname-appname.fsn1.percolate-3.hipex.cloud:80
160148
```
161149

162150
After the change in your **env.php** perform a cache clean:

0 commit comments

Comments
 (0)