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
Expand all lines: docs/about-hypernode/support/how-to-handle-os-and-room-change-upgrade.md
+18-12Lines changed: 18 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,8 @@
1
1
---
2
2
myst:
3
3
html_meta:
4
-
description: 'Learn how our Xgrade proces work and how to make sure your Hypernode is ready for the Debian Bookworm upgrade'
4
+
description: Learn how our Xgrade proces work and how to make sure your Hypernode
5
+
is ready for the Debian Bookworm upgrade
5
6
title: How does the Xgrade proces work
6
7
---
7
8
@@ -14,13 +15,13 @@ An Xgrade is an automated process that allows your server to be upgraded or down
14
15
An Xgrade to Debian Bookworm or R405 (which can be performed together) is carried out by our automation. Below are the relevant steps in the process:
15
16
16
17
1. Ensure a new Hypernode is created.
17
-
2. Configure the new Hypernode (Operating system, MySQL, PHP, Varnish, etc.).
18
-
3. Synchronize data (everything within the "/" and "/data" partition).
19
-
4. Stop all services on the current Hypernode.
20
-
5. Synchronize any new data that has been written.
21
-
6. Perform checks to ensure all processes are complete.
22
-
7. Send a "Hypernode migrated" event.
23
-
8. Destroy the old Hypernode.
18
+
1. Configure the new Hypernode (Operating system, MySQL, PHP, Varnish, etc.).
19
+
1. Synchronize data (everything within the "/" and "/data" partition).
20
+
1. Stop all services on the current Hypernode.
21
+
1. Synchronize any new data that has been written.
22
+
1. Perform checks to ensure all processes are complete.
23
+
1. Send a "Hypernode migrated" event.
24
+
1. Destroy the old Hypernode.
24
25
25
26
As you can see, a completely new Hypernode is created with the correct configurations, whether for a Debian Bookworm or an R405 Xgrade. The first synchronization of data will then take place. The duration of this synchronization depends on the amount and type of data. Typically, we calculate about 1 GB per minute, but this may vary.
26
27
@@ -29,6 +30,7 @@ At a certain point, all services will be stopped to prevent new orders from bein
29
30
## What should be checked or adjusted before the Xgrade? (e.g., Node.js and TLS configuration)
30
31
31
32
### Nodejs
33
+
32
34
Before scheduling a Xgrade to Debian Bookworm/R405, you must check which Node.js version you are using. This is necessary because Node.js versions 6 and 10 are no longer supported on the new operating system. Standard Magento 2 does not make use of Nodejs, but if you use another CMS or have custom scripts that require them, you may need to update your setup.
33
35
34
36
You can check your Node.js version in two ways; withing the Control Panel, or on the CLI:
@@ -47,11 +49,13 @@ Operation was successful and is being processed. Please allow a few minutes for
47
49
```
48
50
49
51
### TLS configuration
52
+
50
53
With the upgrade to Debian Bookworm, the TLS configurations will also change. We have chosen to phase out outdated TLS versions 1.0 and 1.1. Additionally, the "modern" TLS configuration will now only support TLS 1.3.
51
54
52
55
Below are the TLS configurations for Debian Buster:
# What needs to be adjusted after the Xgrade? When can it be performed? (IP changes)
140
144
141
145
If you choose to Xgrade to R405, you will receive a new IP address from our automation system. You must update this IP address in the DNS settings for both the non-www and www records of your domain. This information will be sent to the email address associated with the Hypernode owner.
@@ -145,11 +149,13 @@ My domain is at Hypernode, can we automate this? Yes, you can enable the "Synchr
145
149
We make use of Cloudflare, would we be able to "automate" this proces? Sure! You can enable CNAME Flattening, which ensures that both the non-www and www records point to the Hypernode hostname. For example:
0 commit comments