From a85c83649b908f005eec470572011db3731f9100 Mon Sep 17 00:00:00 2001 From: Rolf van de Bovenkamp Date: Tue, 8 Aug 2023 17:01:35 +0200 Subject: [PATCH 01/17] Updated how-to-configure-varnish-for-shopware-6 removed hypernode VCL because it is outdated --- .../shopware-6/how-to-configure-varnish-for-shopware-6.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md b/docs/ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md index a45db281..09f8e2b7 100644 --- a/docs/ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md +++ b/docs/ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md @@ -90,7 +90,7 @@ Go to [Shopware's Reverse Http Cache documentation](https://developer.shopware.c ## Step Four: Implement a .vcl Into Varnish -To actually use Varnish you need to implement a varnish config file, a .vcl. If you're on Shopware >= 6.4, fetch the [Varnish configuration from their documentation](https://developer.shopware.com/docs/guides/hosting/infrastructure/reverse-http-cache#configure-varnish) (copy the code block starting with *vcl 4.0;*). Otherwise, you can use the `.vcl` from our [Github](https://gist.github.com/hn-support/29efb2e58b18ff2ef0f25363bd02dbe9), or you can create your own. +To actually use Varnish you need to implement a varnish config file, a .vcl. If you're on Shopware >= 6.4, fetch the [Varnish configuration from their documentation](https://developer.shopware.com/docs/guides/hosting/infrastructure/reverse-http-cache#configure-varnish) (copy the code block starting with *vcl 4.0;*). Or you can create your own. So, the steps to implement the Varnish configuration into Varnish are: From 62edf6a77cb55be9042a2015fa27c0f7ceb8f7b0 Mon Sep 17 00:00:00 2001 From: reggysupport <142213583+reggysupport@users.noreply.github.com> Date: Mon, 14 Aug 2023 12:13:35 +0200 Subject: [PATCH 02/17] Deleted old Service Panel part on how-to-configure-ftp-sftp-on-hypernode.md We're deleting all old Service Panel documentation as we almost don't have any customers who use the old Service Panel. In this article we've deleted the topic: 'Via Your Service Panel'. --- .../ftp/how-to-configure-ftp-sftp-on-hypernode.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md b/docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md index 47e9e296..b01bfcd0 100644 --- a/docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md +++ b/docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md @@ -106,16 +106,6 @@ To remove values from your whitelists you can run the following: hypernode-systemctl whitelist remove ftp 1.2.3.4 ``` -### Via Your Service Panel - -Customers who log in via [service.byte.nl](http://service.byte.nl) can whitelist an IP via the Service Panel by following the steps below: - -1. Log on to your [Service Panel](http://service.byte.nl). -1. Select the Hypernode. -1. Go to ‘Instellingen’. -1. Select ‘Externe FTP toegang’. -1. Add IP address and description. - ### Via Your Control Panel Customers who log in via [my.hypernode.com](https://my.hypernode.com) can allow an IP via the Control Panel by following the steps below: From ab61159dc2ff97bb9d267d95b17f06388ce24cf9 Mon Sep 17 00:00:00 2001 From: reggysupport <142213583+reggysupport@users.noreply.github.com> Date: Mon, 14 Aug 2023 12:41:19 +0200 Subject: [PATCH 03/17] Delete dns-for-service-panel-users.md We're deleting all old Service Panel documentation as we almost don't have any customers who use the old Service Panel. In this case we can delete the whole article because there's already an articlle for the Control Panel --- .../dns/dns-for-service-panel-users.md | 171 ------------------ 1 file changed, 171 deletions(-) delete mode 100644 docs/hypernode-platform/dns/dns-for-service-panel-users.md diff --git a/docs/hypernode-platform/dns/dns-for-service-panel-users.md b/docs/hypernode-platform/dns/dns-for-service-panel-users.md deleted file mode 100644 index 656dc119..00000000 --- a/docs/hypernode-platform/dns/dns-for-service-panel-users.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -myst: - html_meta: - description: You can edit the DNS setting for your domain names in the Service - Panel (Instellingen => DNS). It takes 24 hours for a DNS change to be implemented. - title: How to manage your DNS as a Service Panel user? -redirect_from: - - /en/support/solutions/articles/48001153093-dns-for-service-panel-users/ ---- - - - -# DNS for Service Panel Users - -DNS stands for "Domain Name System" and is a protocol that translates domain names to IP addresses on the internet. A DNS server is simply a table that contains IP addresses and hostnames (the name of a computer). The internet also uses DNS. When you go to a website, the IP address of the server behind the domain name is checked. - -You can edit the DNS setting for your domain names in the Service Panel (Instellingen => DNS). - -It takes 24 hours for a DNS change to be implemented everywhere. Take this into account. - -More information about DNS settings for your Magento webshop on Hypernode technology, for example how to manage your DNS settings for a Hypernode can be found [here](how-to-manage-your-dns-settings-for-hypernode.md). - -## Manage DNS With a Third Party - -Please note that Hypernode cannot provide uptime guarantees for external DNS. Your SLA does not apply in this case. When a domain name is registered externally, please keep in mind that Hypernode has no influence on the functioning of the DNS. If you don't want to transfer your domain name to Hypernode, changing the name servers to the Byte name servers is a good second option. You will need a Presence plan to be able to manage your DNS from the Service Panel. When you have the DNS set up correctly you can ask your domain name provider to change the name servers to the Byte name servers: - -nsa.byte.nl - -nsb.byte.nl - -nsc.byte.nl - -If it is not possible to change the name servers at your domain provider you can find how to direct your domain to your Hypernode [here](how-to-manage-your-dns-settings-for-hypernode.md#option-2-manage-an-external-dns-by-pointing-your-domain-to-hypernode-by-using-cname-and-not-an-a-record). - -## How Does DNS Work at Hypernode? - -You can find the DNS settings in our Service Panel. To do this, go to the 'Instellingen' tab and choose the DNS option. For each Presence plan we have a list of standard DNS set up: - -3 NS records (name servers) from Hypernode. These cannot be removed or changed. If you need to change the name servers (to for example Cloudflare) you can request this by sending an email to [support@hypernode.com](mailto:support@hypernode.com) (from the email address that is linked to the account) - -3 MX records referring to Byte mail servers - -4 A records to link the domain name to the web hosting - -3 CNAME records to link certain services at the domain level - -1 TXT record (SPF record) to ensure that Byte's mail servers are authorised to email with email addresses ending in this domain. - -There are also four buttons with which you can perform the following actions: - -### Reset DNS - -When this button is pressed, any DNS changes will be reset to the DNS settings to the default settings for the plan. - -### Add Record - -When this button is pressed you will see a new screen. Here you can add a new record. Here you indicate in the field for **Name** for which subdomain you are creating a record. At **Type** you choose between A, AAAA, CNAME, MX, TXT and SRV. With **conten**t you indicate to which hostname or to which IP address should be referred. You specify which **priority** the record gets and how long the TTL should be. - -### X Icon - -This will delete the DNS record. - -### Notepad Icon - -This changes a current record. You will see the same screen as you click on **Add Record,** but you can edit a current record here. - -## The Fields in a DNS Table - -You can add a number of values to the different DNS records. These values are explained below: - -### Name - -Here you enter the domain name, which can be a fixed address such as example.nl or [www.example.nl](http://www.example.nl), but you can also add a so called wildcard record. A wildcard record is for example * .example.nl and means that all subdomains that do not have a separate DNS record fall under this, an example: - -| | | | | | -| ----------------------------------------- | -------- | ------------ | --------------- | ---------------- | -| **Name** | **Type** | **Priority** | **Content** | **Time to live** | -| example.com | A | - | 125.125.125.125 | 600 | -| [www.example.com](http://www.example.com) | A | - | 124.124.124.124 | 600 | -| \*.example.com | A | - | 123.123.123.123 | 600 | - -### Type - -The type of record will be shown here, more about the type of DNS records is explained in the next paragraph. - -### Content - -The value of the DNS record is entered here, which differs per record type. Information about which values you can enter per type can be found in the next paragraph about types of records. - -### Prio - -The priority of a DNS record is only used for MX records (mail records), with this you can assign a priority to different mail servers and thus ensure that, for example, our (fallback) mailserver is called on when your own mail servers are offline. - -### TTL - -TTL stands for “Time To Live”, which is the time in seconds that a server remembers the data in a DNS record. At hypernode the TTL for the A records is set to 600 by default. This means that if you go to a domain, the data for that record is stored for ten minutes. So if you surf on a Hypernode domain for fifteen minutes, your provider's DNS server should have made two requests to request the A record of that domain. Providers sometimes want to store this data for longer, they will then force a longer TTL than actually indicated in the DNS server. This is called DNS caching and it is described in detail further on this page. - -Hypernode recommends using a short TTL for the A records. Suppose you want to change an IP address of a record with a TTL of an hour or more, it will take an hour for people who have already visited the site to be notified of the change. A short TTL ensures that you can switch quickly if necessary. - -## Types of Records - -Different DNS records have been created for the different types of internet traffic. Here it is described which types of DNS records are most common and what purpose they have; - -### NS Records - -The NS records contain the "authoritative name servers" or prevailing name servers. When your domain name is listed with Hypernode, these will always be on Byte's name servers by default. This determines that we are the party that manages the DNS records. You can also find them in the WHOIS. The Byte name servers are: - -nsa.byte.nl - -nsb.byte.nl - -nsc.byte.nl - -If you have set up other name servers, the DNS data will be downloaded from that server. Hypernode always recommends using the Byte name servers so that in the event of IP changes (if you switch from datacenter) we can switch quickly, without having to make changes to the DNS configuration. You can NOT change the name servers from the Service Panel. If you need to change the name servers (to for example Cloudflare) you can request this by sending an email to [support@hypernode.com](mailto:support@hypernode.com) (from the email address that is linked to the account). - -### A Records - -The A record is used to link a domain name to an IP address. Usually there are multiple A records per domain name. In the example mentioned earlier under “The fields in a DNS table” there are three A records. One ensures that all visitors of domainname.nl are forwarded to the correct server and the other ensures that the domain name starting with www is also redirected to the server. A domain name always needs at least one A record to identify the web server. The third A record in the example is a wildcard record (`*.example.com`) - -If no A (or CNAME) record exists for * .example.nl, subdomains will not be accessible and (provided no separate address has been created for it) [www.example.nl](http://www.domainname.nl) neither. Www.example.com is seen as a subdomain by DNS. - -### AAAA Records - -This is the A record for IPv6 addresses. - -### MX Records - -The MX records contain the host names of the mail server(s). In addition to the hostname, you can assign a priority to each MX record. For example, you can give your own mail servers a higher priority (a lower number) than our smtp2.byte.nl server. This means that smtp2.byte.nl is only used as a mail server when your own servers are not available. We also call this "fallback server". Also make sure that you do not give every MX record a priority of 10, otherwise our server will not be able to determine which record is about the primary mail server. These are the MX records of the Hypernode mail servers: - -| | | | | -| ----------- | -------- | ------------- | -------- | -| **Name** | **Type** | **Value** | **Prio** | -| example.com | MX | smtp1.byte.nl | 10 | -| example.com | MX | smtp2.byte.nl | 20 | - -Always use your primary domain for your MX records. An MX record with the Name on “mail.example.nl” will only work for …@mail.example.nl addresses. - -### CNAME Records - -With a CNAME record you can make a reference for a hostname to another hostname. - -| | | | | -| ----------------------------------------- | -------- | -------------------- | -------- | -| **Name** | **Type** | **Value** | **Prio** | -| [www.example.com](http://www.example.com) | CNAME | example.hypernode.io | - | - -An advantage of using a CNAME is that if the IP address of the web server changes you won't need to change the record for the www domain. - -### TXT Records - -TXT records are flexible in use, you can store all kinds of information in a TXT record. For example, Google uses it for identification if you want to link a Google Apps account to your domain name. Google will then ask you to create a TXT record with a code in it that verifies your identity. - -### SRV records - -SRV (Service) records are used by some programs or devices to provide automatic settings. Certain IP telephones, for example, can easily be connected or reached with this. An SRV record has a specific format: . .example.org, and a specific value: “ ”. If you want to create an SRV record, you will receive the name of the service and the protocol of the program or device that can use SRV records. You can find this in the manual or on the website of your product. For example: Your domain name is example.com and you must create “\_sip.\_tcp.example.com” with the following value: “10 60 5060 bigbox.example.com”. You enter “\_sip.\_tcp” as the name, “60 5060 bigbox.example.com” as the value and “10” as the Priority. - -### SOA Records - -An SOA record is mainly used for the internal communication of different DNS servers and never needs to be changed. - -### SPF Records - -With an SPF record you can define which mail servers are allowed to send email for that particular domain (and prevent spam from being sent from your domain). You can find more information about SPF records and how to use them for Hypernode [here](how-to-set-up-your-spf-records-for-hypernode.md). - -## DNS Caching - -DNS Caching means that the content of a DNS record is stored on a server between your computer and the authoritative name server. Some providers store this data longer than specified in the TTL, so it can take up to a day for the changes to your DNS record to take effect everywhere. This is something to keep in mind when changing DNS settings. There is very little you can do about it that the whole world does not immediately see your new site (most of it), but as a developer it is of course annoying. Fortunately, there is a (local) solution, namely the hosts file. This is a file where you can enter hostnames and IP addresses yourself. This way you can link a domain name to an IP address so that when you visit this domain name, the DNS server is no longer consulted and you are always referred to the same IP address.Please see[this article](../../best-practices/testing/how-to-test-your-website-by-changing-your-hosts-file.md) for more information about the host file. - -### DKIM and DMARC - -DKIM and DMARC are techniques that use a combination of private and public keys to indicate who the sender is. The public keys can be added via the Service Panel as a TXT record in the DNS editor. The private key that is injected into the header of an email can be added using your own PHP code. This is a very complex technique that requires a lot of knowledge. Unfortunately, we cannot help with generating the keys and / or adding the private key in the code of your website / webshop / email client. If you experience problems with setting the TXT record, it is best to send us an email. Please include the full public key so that we can determine what is going wrong. From c0291f51843e4ec2222397cc48154317c996da4f Mon Sep 17 00:00:00 2001 From: reggysupport <142213583+reggysupport@users.noreply.github.com> Date: Mon, 14 Aug 2023 13:25:59 +0200 Subject: [PATCH 04/17] Delete old Service Panel topic - Update how-to-configure-varnish-for-magento-1-x.md We're deleting all old Service Panel documentation as we almost don't have any customers who use the old Service Panel. In this case we can delete the topic: 'Dutch Customers: Via Your Service Panel' --- .../magento-1/how-to-configure-varnish-for-magento-1-x.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md b/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md index 74d13df0..867d8745 100644 --- a/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md +++ b/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md @@ -22,7 +22,6 @@ Although Varnish is extremely awesome when it get's to speeding up websites, Var - [Enable Varnish for Magento 1.x](#enable-varnish-for-magento-1x) - [All Customers: Via the hypernode-systemctl CLI Tool](#all-customers-via-the-hypernode-systemctl-cli-tool) - - [Dutch Customers: Via Your Service Panel](#dutch-customers-via-your-service-panel) - [International Customers: Via Your Control Panel](#international-customers-via-your-control-panel) - [Install Turpentine](#install-turpentine) - [Configure Turpentine](#configure-turpentine) @@ -39,10 +38,6 @@ Before installing Turpentine we recommend enabling Varnish on your Hypernode usi Activating Varnish and set which version to use on your Hypernode can be done via the [hypernode-systemctl tool](../../hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md). -### Dutch Customers: Via Your Service Panel - -Only *Dutch customers* can also easily activate Varnish via their [Service Panel](https://service.byte.nl/). Go to `Instellingen` and change Varnish to `Actief`. Once you’ve changed this setting and enabled Varnish in Magento, Varnish will store all information in it’s own cache. Only when Varnish needs data that hasn’t been cached it will connect with the server. - ### International Customers: Via Your Control Panel English speaking customers who ordered their Hypernode via Hypernode.com have access to their [control panel](https://my.hypernode.com/). Find your Hypernode, click on `Settings` and go to `Caching`. There you can enable Varnish with 1 click on the button. From 119ada9a2fb36e3b75d38608828d1c2b0703bec7 Mon Sep 17 00:00:00 2001 From: reggysupport <142213583+reggysupport@users.noreply.github.com> Date: Mon, 14 Aug 2023 13:44:21 +0200 Subject: [PATCH 05/17] Delete how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md We're deleting all old Service Panel documentation as we almost don't have any customers who use the old Service Panel. In this case we can delete the whole article because there's already an artille for the Control Panel (hypernode.com) --- ...hypernode-when-ordered-via-hypernode-nl.md | 259 ------------------ 1 file changed, 259 deletions(-) delete mode 100644 docs/hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md diff --git a/docs/hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md b/docs/hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md deleted file mode 100644 index 0ca00203..00000000 --- a/docs/hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md +++ /dev/null @@ -1,259 +0,0 @@ ---- -myst: - html_meta: - description: An SSL certificate keeps online interactions and transactions private - and helps to gain confidence of customers. Read here how to use SSL ordered - via Byte.nl. -redirect_from: - - /en/hypernode/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-byte-nl/ - - /knowledgebase/use-ssl-certificates-on-your-hypernode/ ---- - - - -# How to Use SSL Certificates on your Hypernode When Ordered via Hypernode.nl - -This article explains how to install SSL certificates on your Hypernode. An SSL certificate keeps online interactions and transactions private and they help customers gain confidence to provide personal information on your website. We strongly recommend shop owners to use SSL certificates. This way, your shop will become securely accessible using HTTPS. - -## Why Use SSL? - -SSL sends information across the internet encrypted so that only the intended recipient can understand it. SSL establishes a secure connection between your visitor's browser and your webshop. It allows you to sent private and sensitive information, such as payment credentials, across the internet without having to worry about the problems of eavesdropping, data tampering, and message forgery. - -## Service Panel users: SSL on Hypernode - -**Service Panel** users (Hypernode.nl) have three options to use SSL for their Hypernode plan(s): - -- Order an SSL certificate via Hypernode (recommended) -- Upload your own SSL certificate -- Request a certificate using Let’s Encrypt - -We recommend purchasing an SSL certificate through Hypernode, because you’ll benefit from our managed hosting services. - -When using a third party SSL certificate or [Let’s Encrypt](../ssl/how-to-use-lets-encrypt-on-hypernode.md), you are responsible for implementing, maintaining and renewing the certificate. We cannot provide any support on custom SSL certificates and related issues. - -## Buy an SSL Certificate Via Hypernode (Recommended) - -We recommend you to purchase an SSL certificate via Hypernode, because then you’ll benefit from our managed hosting services. Not only do we take care of the technical implementation of the certificate for you, we also renew and validate the certificate on time and provide customer support on SSL issues. This way your e-commerce shop will always have a secure connection. - -**Note: If you purchase your SSL certificate via Hypernode for you will need an additional Presence or Presence Plus plan for the domain name you want to order the SSL for (except of course when you already have a Presence plan for that domain).** - -In case you do not already have a Presence plan for this domain, start with ordering one. If you do have a Presence plan, please skip the steps below and go straight to ‘Order an SSL certificate’. - -### Order a Presence Plan - -You need to order a Presence plan to connect the SSL certificate to your Hypernode. A Presence plan acts as a v-host to make a domain known in our systems, otherwise you cannot order an SSL certificate. So, **first** order a Presence plan for domain.com and **then** order an SSL certificate as an add-on to this Presence plan. The steps: - -- [Log in](http://auth.byte.nl/) to the Service Panel -- Click the ‘Bestel Direct’ button on the right -- Choose your domain name under ‘Kies een domeinnaam’ and click on ‘controleer beschikbaarheid’. If you want to keep the domain registered elsewhere you can choose the option ‘hosting only verhuizen’ -- Select ‘Domeinregistratie’ -- Select ‘Presence or ‘Presence Plus’ -- Click on the ‘Controleren & Afronden’ button to check your order details -- If all is OK, click on the “Bevestig & Betaal’ button to finalise your order - -### Order an SSL Certificate - -The following steps will help you to purchase an SSL certificate for your domain: - -- [Log in](http://auth.byte.nl/) to the Service Panel -- Select the domain for which you need an SSL certificate -- In the ‘Administration’ tab you click on ‘SSL-certificaat’ -- Select the type of SSL certificate you want to order (Single, Wildcard or EV) -- Select a validation e-mail address -- Agree with the terms and conditions -- Click ‘Bestel’ - -We will email you once your certificate is received and installed. - -### Install the SSL Certificate on your Hypernode - -When the certificate is ready, you can easily add it to your Hypernode by visiting the ‘SSL & DNS instellingen’ overview mentioned here above. The domain for which you ordered a SSL certificate will now have a status ‘Beschikbaar’ in de ‘SSL Certificaat’ column. Simply choose ‘Installeren’ to add it to your Hypernode. - -**Keep in mind:** - -- You can only link SSL certificates from plans that have the same Contractant role as your Hypernode plan. Make sure these roles match! -- You cannot link Let’s Encrypt certificates via your Service Panel as these certificates are managed locally on the node itself. - -## Add a Custom SSL Certificate - -Using a SSL certificate from a third party is a possibility too, although we don’t recommend it. When using a third party SSL certificate, you are responsible for implementing, maintaining and renewing the certificate. - -If you wish to upload your own custom SSL certificate, you will need a few .PEM files: - -- The unencrypted private key -- The certificate -- The CA certificate Chain file (Intermediate certificates) - -To upload your custom SSL, follow the steps below: - -- [Log in](http://auth.byte.nl/) to the Byte Service Panel -- Select your Hypernode plan -- Click on the ‘Instellingen’ tab -- Click ‘SSL & DNS instellingen’ -- Click ‘Beheer SSL Certificaten’ -- Click ‘Koppel handmatig een certificaat’ -- Fill in the Private Key, Certificate and Certificate Authority (only .PEM files) -- Click ‘Volgende’ -- Check whether you uploaded the correct certificate -- Click ‘Add certificate’ - -## Use Let’s Encrypt - -For the more technical equipped developers we provide [Let’s Encrypt](../ssl/how-to-use-lets-encrypt-on-hypernode.md). - -Let’s Encrypt is a way to order free SSL certificates through domain validation. This has a few limitations: - -- You are responsible for your own Let’s Encrypt certificates, we do not provide support for Let’s Encrypt. -- Let’s Encrypt does not provide wildcard and/or EV certificates -- Let’s Encrypt SSL Certificates are only valid for a 3 months period. - -See [our documentation about configuring Let’s Encrypt on your Hypernode](../ssl/how-to-use-lets-encrypt-on-hypernode.md) on how to setup Let’s Encrypt on your Hypernode. - -## How Do I remove a Custom SSL certificate From My Hypernode? - -Removing an SSL certificate from your Hypernode is easily done via your Service Panel following the steps below: - -- [Log in](http://auth.byte.nl/) to the Service Panel -- Select your Hypernode plan -- Navigate to the ‘Instellingen’ tab and click ‘SSL & DNS instellingen’ -- Click ‘Beheer SSL Certificaten’ -- Click the waste bin button on the right of the certificate you wish to remove -- Click ‘Delete SSL certificate’ - -Your SSL certificate is now removed from your Hypernode. If you wish to add it again, simply go back to the overview page and click ‘Koppel handmatig een certificaat’. - -To remove Let’s Encrypt certificates you need to log in to your hypernode and[delete the created certificates](../ssl/how-to-use-lets-encrypt-on-hypernode.md#stop-using-dehydrated--cleanup) over SSH. - -## Changing Your Base URLs - -If your SSL certificates are linked to your Hypernode, or you ordered Let’s Encrypt certificates, we can change the base URLs to use only HTTPS. To do this, we created a little Python script that changes all your base URLs to HTTPS. - -To use this: - -```nginx -## Download the script - -wget -O change_baseurls.py https://gist.githubusercontent.com/hn-support/0c76ebb5615a5be789997db2ae40bcdd/raw/ - -## Execute to change the base URLs to HTTPS - -python change_baseurls.py -``` - -## Forcing Your Entire shop to Use SSL - -You can easily force your entire shop to go over HTTPS using a simple redirect. - -### Redirecting all traffic (when Varnish is not used) - -To redirect all traffic from HTTP to HTTPS, open the `server.rewrites` with your editor: - -```nginx -editor /data/web/nginx/server.rewrites -``` - -Then add the following snippet: - -```nginx -if ($scheme = http) { return 301 https://$host$request_uri; } -``` - -Now finish saving the option using `CTRL+o` followed by `CTRL+x`. - -To check if all went well, check if `/data/web/nginx/nginx_error_output` is present containing an error message. If you can’t find this file, your config reload went well. - -Now test your result by visiting the domain! - -It is also possible to [selectively redirect to HTTP or HTTPS](../nginx/how-to-redirect-from-or-to-www.md) depending on the domain, by using a mapping. - -Redirecting all traffic to https and www - -If you want to redirect your domain to both https and www, add this snippet to `server.rewrites` - -```nginx -if ($http_host ~* "^(?!www\.).*$") { - - return 301 https://www.$http_host$request_uri; - -} - -if ($scheme = http) { - - return 301 https://$host$request_uri; - -} -``` - -### Redirecting to HTTPS When Using Varnish - -If you are using Varnish on your Hypernode, the given redirect will be cached by Varnish causing the site to go down with a 'too many redirects' error, as the redirect will be served from the cache on both HTTP and HTTPS. - -To resolve this, make use of a `public.rewrites` instead of a `server.rewrites`. - -All files in /data/web/nginx starting with public.\* will be included in front of the Varnish instance, and will therefore not be cached. - -## Things to Remember When Using an SSL Certificate - -- Don’t forget to point the DNS for your domain to your Hypernode. More information about how this is done [can be found in the article DNS settings Hypernode](../dns/how-to-manage-your-dns-settings-for-hypernode.md). -- You will need a storefront in Magento with a secure_base_url. Otherwise Magento will redirect you to the main store. You can change the base urls using the script mentioned above, you can also do this using the following support documentation. - -## SSL on Your (non-www) Naked Domain While Using the Www-izer - -If you use the www-izer forwarders in the DNS settings for your domain name, people that visit directly will get an error message, either indicating that there is no https available or a plain connection refused error. -If Hypernode manages your DNS, or you’ve configured your DNS to point directly to the Hypernode, this will not be a problem. - -For more information please read the article [DNS Settings Hypernode](../dns/how-to-manage-your-dns-settings-for-hypernode.md) - -## Enable SSL Stapling - -To enable SSL Stapling for your SSL certificate, create the following configuration in /data/web/nginx/http.ocsp: - -```nginx -ssl_stapling on; - -ssl_stapling_verify on; -``` - -## Check Settings of Third Party Solutions - -After configuring your shop to only use HTTPS, please do not forget to check HTTP(S) settings of third party solutions to avoid problems, e.g.: - -- Payment providers like Adyen -- Stock providers like Picqer -- Google Analytics and Google Search Console - -## How to Generate Certificate Signing Request on Nginx using OpenSSL - -Log into your Hypernode with SSH and run the following command: - -```nginx -openssl req -new -newkey rsa:2048 -nodes -keyout myserver.key -out myserver.csr -``` - -**Note:** Replace yourdomain with the domain name you're securing. For example, if your domain name is mydomain.com, you would type mydomain.key and mydomain.csr where server is the name of your server. - -This will begin the process of generating two files: the Private-Key file for the decryption of your SSL Certificate, and a certificate signing request (CSR) file used to apply for your SSL Certificate. - -Enter the requested information: - -\*\*- Common Name (CN):\*\*The fully-qualified domain name, or URL, you want to secure. - -If you are requesting a Wildcard certificate, add an asterisk (\*) to the left of the common name where you want the wildcard, for example \*.mydomain.com. - -**- Organization (O):** The legally-registered name for your business. If you are enrolling as an individual, enter the certificate requestor's name. - -**- Organization Unit (OU):** If applicable, enter the DBA (Doing Business As) name. - -**- City or Locality (L):** Name of the city where your organization is registered/located. Do not abbreviate. - -\*\*- State or Province (S):\*\*Name of the state or province where your organization is located. Do not abbreviate. - -\*\*- Country (C):\*\*The two-letter International Organization for Standardisation (ISO) format country code for where your organisation is legally registered. - -**Note:** If you do not want to enter a password for this SSL, you can leave the Passphrase field blank. - -Your `.csr` file will then be created. - -Open the CSR file with a text editor and copy and paste it (including the BEGIN and END tags) into the Certificate order form. - -Save (backup) the generated .key file as it will be required later when installing your SSL certificate in Nginx. From ada1bc5e779a98523a754373477079508a3866e8 Mon Sep 17 00:00:00 2001 From: reggysupport <142213583+reggysupport@users.noreply.github.com> Date: Mon, 14 Aug 2023 14:03:31 +0200 Subject: [PATCH 06/17] Deleted old Service Panel topic - Update how-to-use-hypernode-development-plans.md We're deleting all old Service Panel documentation as we almost don't have any customers who use the old Service Panel. In this article we've deleted the topic: 'Upgrading Your Development Plan for Service Panel Users'. --- .../how-to-use-hypernode-development-plans.md | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/docs/hypernode-platform/tools/how-to-use-hypernode-development-plans.md b/docs/hypernode-platform/tools/how-to-use-hypernode-development-plans.md index 5bc93d02..782584aa 100644 --- a/docs/hypernode-platform/tools/how-to-use-hypernode-development-plans.md +++ b/docs/hypernode-platform/tools/how-to-use-hypernode-development-plans.md @@ -23,20 +23,7 @@ The development plans come ready-to-go. You don’t have to worry about web stac ## Converting a Development Plan to a Production Plan -When you’re done developing you can convert to a regular production node at the click of a button in your Service Panel (service.byte.nl) or Control Panel (my.hypernode.com). - -### Upgrading Your Development Plan for Service Panel Users - -When you log in via [service.byte.nl](https://auth.byte.nl/)please follow the steps below to upgrade your development plan: - -- Log in to the Service Panel. After logging in, you'll see a list of all your Hypernode plans. -- Click on the domain or Hypernode you want to upgrade. -- Click on **Pakketbeheer**in the tab **Administratief**. -- Click on **Wijzigen**next to **Pakkettype**. -- You'll now see an overview of your current plan. Next to your current plan, you'll see the specs of the new plan in the column Pakket. -- After selecting the right plan in the right column (don't forget to select **Production**at Uitvoering), scroll down to agree with terms and conditions and click **Pakket aanpassen**. Your plan will be changed immediately. - -Please note only the Contracting party or Technical Party (when they're a Hypernode partner) can change the plan +When you’re done developing you can convert to a regular production node at the click of a button in Control Panel (my.hypernode.com). ### Upgrading Your Development Plan for Control Panel Users From 231adcea56f43d5e5fe34119442e38a28a51a310 Mon Sep 17 00:00:00 2001 From: dvd2david <126869057+dvd2david@users.noreply.github.com> Date: Thu, 17 Aug 2023 14:42:58 +0200 Subject: [PATCH 07/17] Update how-to-configure-ftp-sftp-on-hypernode.md Remove Service Panel reference --- .../ftp/how-to-configure-ftp-sftp-on-hypernode.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md b/docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md index 47e9e296..b01bfcd0 100644 --- a/docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md +++ b/docs/hypernode-platform/ftp/how-to-configure-ftp-sftp-on-hypernode.md @@ -106,16 +106,6 @@ To remove values from your whitelists you can run the following: hypernode-systemctl whitelist remove ftp 1.2.3.4 ``` -### Via Your Service Panel - -Customers who log in via [service.byte.nl](http://service.byte.nl) can whitelist an IP via the Service Panel by following the steps below: - -1. Log on to your [Service Panel](http://service.byte.nl). -1. Select the Hypernode. -1. Go to ‘Instellingen’. -1. Select ‘Externe FTP toegang’. -1. Add IP address and description. - ### Via Your Control Panel Customers who log in via [my.hypernode.com](https://my.hypernode.com) can allow an IP via the Control Panel by following the steps below: From 32d7446d726d853a3abd57c683204e70352aea66 Mon Sep 17 00:00:00 2001 From: Alexander Grooff Date: Thu, 17 Aug 2023 16:02:27 +0200 Subject: [PATCH 08/17] docs: general cluster documentation --- docs/hypernode-platform/cluster.md | 77 ++++++++++++++++++ .../cluster/_res/hypernode-cluster-map.png | Bin 0 -> 7200 bytes 2 files changed, 77 insertions(+) create mode 100644 docs/hypernode-platform/cluster.md create mode 100644 docs/hypernode-platform/cluster/_res/hypernode-cluster-map.png diff --git a/docs/hypernode-platform/cluster.md b/docs/hypernode-platform/cluster.md new file mode 100644 index 00000000..254296b6 --- /dev/null +++ b/docs/hypernode-platform/cluster.md @@ -0,0 +1,77 @@ +--- +myst: + html_meta: + description: Hypernode clusters allow you to scale your setup to your needs, both horizontally and vertically. + title: Cluster | Hypernode platform +--- + +# Hypernode Cluster + +Hypernode comes as a single server setup by default. This is to make sure that latency between services is as low as possible, +and that the server is as fast as possible. However, if you have a lot of traffic, or a lot of data, you might want to consider a +cluster setup. This is a setup where you have multiple servers, each with their own task. This way, you can scale your setup to +your needs. + +## Cluster vs single server + +Choosing between a single server setup and a cluster setup is a trade-off between performance and flexibility. A single server +setup is the fastest, but a cluster setup is more flexible as it allows for more ways of scaling up the available resources. +You can add more servers to your cluster, allowing you to scale your setup to your needs. However, a cluster setup does come +with a performance penalty. The latency between services is higher, which causes a slight overhead in performance. + +## Up/downgrading between plans + +You're able to up or downgrade your plan with Hypernode whenever you want. This applies to both single server setups and +cluster setups. + +In a Hypernode cluster this goes per Hypernode. So if you have a cluster with 3 Hypernodes, you can upgrade 1 Hypernode to a +higher plan, and the other 2 Hypernodes can stay on the old plan. This allows you to scale your setup to your needs while +the rest of the cluster stays up. + +## Connecting between cluster Hypernodes + +All Hypernodes within the same cluster are connected to each other. You can see how the Hypernodes relate to each other in the +map: + +![](cluster/_res/hypernode-cluster-map.png) + +You can generate this map on the fly using the CLI command `hypernode-cluster-map`. You can also get a detailed overview of the +state of the cluster using the CLI command `hypernode-cluster-info`: + +```bash +app@1fosk3-hnclusterweb1-magweb-hetz:~$ hypernode-cluster-info ++---------------+--------------------------+-------------+----------------+------------+ +| Hypernode | Roles | Private_IP | Private_subnet | Cluster_IP | ++---------------+--------------------------+-------------+----------------+------------+ +| hnclusterdb1 | mysql | 192.168.1.5 | 192.168.1.0/24 | 10.0.0.2 | +| hnclusterlb1 | redis, nfs, loadbalancer | 192.168.1.2 | 192.168.1.0/24 | 10.0.0.3 | +| hnclusterweb1 | web | 192.168.1.3 | 192.168.1.0/24 | 10.0.0.1 | +| hnclusterweb2 | web | 192.168.1.4 | 192.168.1.0/24 | 10.0.0.5 | ++---------------+--------------------------+-------------+----------------+------------+ +``` + +### Wireguard + +All nodes within the cluster can communicate with each other over their cluster IP addresses. These are private IP addresses +that are only accessible within the cluster, as they are [Wireguard](https://www.wireguard.com/) tunnels between each Hypernode +in the cluster. + +```bash +app@1fosk3-hnclusterweb1-magweb-hetz:~$ ssh hnclusterdb1.hypernode.io hostname +cj8jv7-hnclusterdb1-magweb-hetz.nodes.hypernode.io + +# For convenience, you can also use the short hostname +app@1fosk3-hnclusterweb1-magweb-hetz:~$ ssh hnclusterdb1.h hostname +cj8jv7-hnclusterdb1-magweb-hetz.nodes.hypernode.io +``` + +### Private network switch + +We can provide you with a private network so that your Hypernodes can communicate with each other with a larger bandwidth than +over a regular internet connection. This is especially useful if you have a lot of traffic between your Hypernodes, or if you +have a lot of data that needs to be transferred between your Hypernodes. + +For this we provide a subnet where every Hypernode has its own private network IP address, which is only accessible to Hypernodes +in the same cluster and in the same datacenter/regions. Just like with Wireguard connections you can connect between Hypernodes +over the same private network. When available, we automatically configure the use of the private network over Wireguard +connections because of the larger bandwidth. diff --git a/docs/hypernode-platform/cluster/_res/hypernode-cluster-map.png b/docs/hypernode-platform/cluster/_res/hypernode-cluster-map.png new file mode 100644 index 0000000000000000000000000000000000000000..46654756fa4233e8d4dd2d673783177d298f5433 GIT binary patch literal 7200 zcmaKwWl&tpwtzPlB$+^PJ3vB^1h)(>!QEX?aF@vhcY*{9?ykXoU~ma;f#5O_d~kPo zoLBX#Zr!@~{pj7bx@vb-@7=xD*I$^5k~9d190vdZkgSY^+Ed^9)aJ2JpPpV4zrQ|p z*iJIK5CC}D^G`!bV0uXb02C9l5@H%|>HACWUW6O>m`8_Pwas%&ivycVSg$W7m0mXC z#-NHYxoA~Uwa-saU(D#$|6!5rB=*&?5%SSvBSgm~BrGq+!_tmYl=*mYyZAOu!1Hie zuwA64DZ7JTmnIBx87@*YRC_BZa5`t1nc{8{5)>4S@=*j2l1Jf3|8^LJFaF7ruPC%& zck5XVZ6-&&@8u3(q#p*osefq=7r4h-ZvG@ec4F1iDw_MTb~UxC!|c5i6us}K3_2x( zhC^yAxL@#2gY_cHeca6TTCnPXDl_n_!K6>C>4M`lvvQ#%!ytSgF`Xm3^Ua;~7lPgY z7<(E2BVi7Dv@#uUjD&Y$mh((v|+VBki;Z>x#_AuIk@@oz!Uz{-i zCb3T@4&OSicsYz{nol7jkh^4{ZorkW9DtQ%axAbVw z0SV%bEdsYZ3huU7j#G6a^ua%Cd+BK@_C6~jlkuATA4cIb0w{o=+v09P*CJrhQ2Dn| zUZ!%!A8R{Lb;H68&aGoVTeVhki1<2JF8%?|#hGd2^ucuW;Crs~2Hj5$%k>K024p_c z*&$~2(8;Im9M z>mimdIa|W}t6_ZTr+$~p^2EgCm*N(rj)*i0srh!4yQ-@AX+28$8~UfLms8lthJ84nu86E@qU_S5=i4)59~sg6H;^OdeN{t`nY zn?4==y#pImB+;YbR6u2dDB@!I&=@L>5mR!h4(`;XrBYzw{a9c&CK zTvD;tGq_1KDT-1WStYLR(XDs0x%=QcN6>T*qMet?_em>Ckt1hPey()fnIr!xmS`Fx zz+(|^gg`-gzyS!3AzC<;hikc?1BB6HFd0SjxUjxxuae|-33~h@EIa7HG>>4{%-6b^wl4#X$<8kybhAIsc&t`;O;h0jP%`*g zM$F&4-f6D&&f>P;Vjx9IB;KaE!1rGcE}0}*RO@Rw)<_PdzSw4wNlw}`IODwMtzZHx z3c5{tyiY{ae21!MsR?SzXy546G&UgmGNf?-+p+Pge!`4h4iI09{HwaLV%Yz7^`oJu zex7}8w>At~r{1f)BOyh+y^XBCS6pa@FGvx7Z-j?%e3XSix>w-HsSi{Wb=taQm@oH8 z0sn~{qO!wcw-dVy3VSVq_H;SdOO>t-Sl#8U5e>HucY+4~+6KQ1AI?q1a|?ZJoBeWb zfL6O0OJ#KS6DoB<0Npn{ORIh4PP_nSbq8a7n~BwgdUGira$axOK0LMI%a;$T^y8Aw zLeW2XUA#=!gWI#>w;}=ju88z;yH~-|TpD=Hv^X+4S~w=_SF4&bw^4*dRL%ycR}Z78 zkp79Iy1%HFcsv4oO|15ISr51tTEpcC)v!^PQ8{soI&r&HxbO-jx_}qnSN_o-uKa9~ z6Pq%iXFzr^JuS0lKUr`Pqr!OxzfXyAXe=)ip@Wuq?K!4~^RL_n6(`Gz-JHg-YLN|6 zgTCgiA!`k%)Fj`0w$}jgv8drsQ$R2O?S~+AAk@npdAE_51vc1`Ox*hxV7GwKid=pJ z(JYRSrD0E>+zlIeH>~@oR6`|DOI%Xh8BL*Z(ZIo$>#n5@c083X1>`!ZJ!@)w`%K#I zB)Vm?egE2``K7iRki7}npp%xy6>x`$xTYi---RqXHNe~qmrj=H@+PZ*2c=D&3t@IqJ5#&-qGni~wBxvZ0`>uC zZ?=7&U@6$M*+UWfCe;G%QM^P&CfHXYpsFmwPqVRtL@p}nRNcVWvAm<_8OGOnVyxq% z441Ta<>Vl6^!xraUK2B=%p?QS{>w|P)3@(wXntR$T>Dy=JRP#2qK-rt+F>nx4#Cn%n_p8Y^ zD`&^PnDdxib1EMW(0dSksrOmXFWYe*f!|2ycEd_y?@;+QrkTD}u*H2}q)rvNyd-Uk)&Ay(|dD>b(})I_cQGr1DZgsQQz>g4W+)W zt;E8UwrFvkB9`Vgs^k8)j1cV~zP+XR#lii*F67?pG~Fz>VS}TWv2VamxN49KXg3M6Df}@dhw${{7jv8zKlq--F1V zt_2My5GsQZ)C(|HMRLfm)B9oX48tWMe(A?;jMQw_EKJWWL_|oM@F)LWt(B6ahg6-F z2~_Qn)BEqFZY`w$id_FjVE-lLC*OryY^kS zy3tk)bu7;6q=w5WH*f(RjW-1hZj0L&5s>6Gl;0XB`^WeIVA8!M-Dm1hVdu3T3`)Db z3si+lGYLA#VPWjMdMfi2FwY5gFR8^nZtBl%c$nNxW_tah&uXcByi=-oKGN)=U0p2? z@A?)kd}8r66BXD^6NIcO=bEA#5;E7HU21G@_))=wqrH`)P(ZkKD-g?Y|{1?ygZt@wnT2%eU+zb0#Dl>B?HH@ zEsy^0wSiXNM#lpI4r6rS%3gtjaBkt7r#lG^==!VVRN}P3{)FZ|a=6!JIlfuYK{GTu z)(Tq31}-w+?;TG$K1rt}zyNa7Gbw3!rZ))Fo(?xbs^AF8yol$XkLJM<{NRitl$R`U`tfJGy}&YcJM zRHcNC7L8(I4~TJk+bhi-eFGC`d0f-NeO7-be||J0#sW4zf5mKfUitJ^csP0Xp@M|Z5ONWw;y+V=}}-HpvIma0A| ztF2jkL7;`f5R7L7b)j=y-KOS+T`j$@s$X*!OpHj0<>@_1lR-S&y@%eqG z^Q8*=Z<_}Df~yaTZ07fceea*i;cdO+!hEC(OD(rBSzJtLjP`LSuo1ujrjg$kM|(De zYnHhZ%=3a-5^GxE59|F|_tsE1RnJPI^<^>Zf#nu@2AH+UTV`$xq68Kr-mPU&Nx;ps zK<2lj+S_}1%Ou*b>!yk7i|);See2TzDWZi0M~oo6w5C5j8qP7ahb2<1%s-bq8zTN5 z&|-1A{kStE&@eR6=pgGhA3(zptOtVko^HMLEv(qE!$9BvI%AYzXOxy6k55uES<-&Z zI%zMfuwI~9=ku_6sYGEpDi?|!hleV98?+~$oEAgrbx%m)Idf2y^rhwTXu7g)X0sn_ zt@>nDaaT~@Rml4;;2in0^3Etnq;+k_+$~cq2>U}DN-y}66xO7=jwZ+SH~_4aNmNs| zWc-o8ygP^zit-+dkr9=X!1|TdZ`&!(3I5%KbR<1IBXpclkJIl)Y!}}3ub!{UM1)Nt zvX4>!-%S5c(sPnN*xGdt2bc=Ok_P)!&Mchw%X$$TMV)MNL2hb}oy=kP& zmy{35q-Di^r>Z7z?co2?vO(eF%Q>av$foP^fZMa*M>*DH->%|yn(CQhRn(?jWPBE0 z-7}@9^PK{G<|X#5Fm*e<^w`p2q3CuRE9;JZ`-J=`S$dB++t zvc6t?|E_``+#Zhpw&;orhz*V3Iq*_+@L}k+h;^CuX{=YvKqwaG(_iC#u|a-j%V7mq zqM35(@*P}7)^ozLqe1erY8VU**B=Aa%PqiQHfwRy=aZDK}}_ zz)(zI_((w$2EXp!H}lm9dgaLKlwnGb%ubzDeKQreMtQwc7mDL=fdelpEk!@AxGVm< z5%@3l=s)X&;MVq}1H$Uh_lq4duG9bPKAKi#dvr`tiAV(mAmZtT`7FjM+;`0=qMrHJ zSs*aRbA@cwmwu<=F{He0VxJ;LK{4)EKMd#>TZg~%n(8c-HHU1iG&dIBd-OFR%5*ao z!j2G8)xcl}qCDm9 zY0&u}>v608pIG4k%A!NYzGUqri$YosZ|i!nv!@$Uw3cBL+h=G+vl)bP;v`9$EH;Z`3Yx~ zwGLpiNNYid`BX_4Rm!v{QV~KDD##GLen{=joq;aIwfpO&@t#P0LG|4hob`3a zaR&wN2;;-nJzFN{+%lWl`9*t045i1-FEl7x`!egfva#nD(%re!NDjOH%zCgkYVV#g zZ&U__^ifma)&3jhJa4(X&ms9jme%?1iZuUxpff+HF&6rPPqhTi zjZ-ttyK$2uKwII2_C~0vRgPBt0<}byI@a$O;m^cB`XF-(GBYGoq?JC)qN)>Dz#mhv zW-K#r;nqF&7@@mmk);AdZF8<#M^T0?pMDA94nU(@KbM4{0&B3nXk5prBrEyasHyD@ zb#1|_>JY#wk6cc069LJptvEWX#?d?*uG9BvmMru=EB6w@04mH5wd#$0^R}k=IKdBZ z4+kvU?EU~NM=2w|?ibTd;36tUL7p=*vay4REhB+BaTFTZ;-C7{(N$Cl9^d^M(YCt| zt})+VCMdw4#E0E|+!4dmxPJ9RZQgYwT)Wwb&mzV5R$CWisqO&aBGbCF8X2>?I?5mb zt%Dt%f}f-Kfea}!iM!UlFDg5YY_15Nu^P4aYr7sKSboXc&jF4$1_~Kqh-#0K2m-b& zitBs!jHTl-M*&8_%)-{t=tdFQ#eF%6xKuGIV%8xp-R7&m4byhHc?USlwjHuXONe)G zCq9!K6}j(O^~anIkz|R(yC7-{U6jZvQ0P){NTz z_}z!F?a|4qWMigkK@?`Qyt5|>elAle6(rkO6A>Y$@2hZo677?cqFqF+D&)gjUKIw~se%?&}*;@rNaAthc!X)-CJ7 zTxonXa+Vkt+;(NTAA4vxNeEExTDb7e}RzDHJ3x z_Y!hA=6RonR24!&xIB0**u$1jR%(U6f;>=w4i%U6?qPcW3kzy~_?zRR-ORaHDeChq zX`Dhr^ZKq2<&{Hr2n}^-Eh9w4oQN-SpuZ)Rib?gVXE^;8Gq-Qz6nhO$PHTRn=G9J@ zvG9SHm}x%nTj%1il_Av)$l17JAPc9`y9pr)m_j0rrkU(KT=J9N9X<~3wK_#sin!Og zUHgt*k9;{yxvuAT-#&AiSfVSIO2X$hm=Ir}Wg~>CYYs=mznh4P$m44eV*i5t)0`wN zg93!Q))7>7K0ko7O`y_nTOQoQdz>;}?nNXm0z8E6k9Vj0yVJ|*sc@Q99@nX@zkDno zw{%IU&uX>2P9}CwJZDA}b@5nVqx)T8S>l>~zy=CW?%DRXZ|82ze?Srkua^^ZX)%TG zu7<}i<1Z{)n+%s>)<4TqhW@Nam`u4&Z+YF#w~0^XS!NwgVH$h%?I*#;GMi{p>CmmH z%?<^Ap#!3~r-PbG)H^ zA;u!B=cRqL(j@pE%Iz?O?NY`NF(xDPeu4C5ORb3S5hLju0oeDL@~0EY1`(H|>I*<8 z+*bG+-eck@-fQ*yJk@T`usO?U{`jF=zuo0GhaR_2q&YM?=@^u%b9CeM_SwaMG$Q{; zK~EAOLbWMo^x;19-t&t+PP=f@`&^1Akdl_rTUH$a> zg21DN;35(JbKa7U+0}a<-yjT1VC(iZ$B`Syzv`NZM@$$0&%o##EA}TS0c0hWBq~0d G1pE)I? Date: Thu, 17 Aug 2023 17:44:07 +0200 Subject: [PATCH 09/17] chore: mdformat --- docs/hypernode-platform/cluster.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/hypernode-platform/cluster.md b/docs/hypernode-platform/cluster.md index 254296b6..92cd333a 100644 --- a/docs/hypernode-platform/cluster.md +++ b/docs/hypernode-platform/cluster.md @@ -1,7 +1,8 @@ --- myst: html_meta: - description: Hypernode clusters allow you to scale your setup to your needs, both horizontally and vertically. + description: Hypernode clusters allow you to scale your setup to your needs, both + horizontally and vertically. title: Cluster | Hypernode platform --- From 95babe22c13e1075d313f30fb40f1dc82e4e0f3f Mon Sep 17 00:00:00 2001 From: Alexander Grooff Date: Mon, 21 Aug 2023 12:05:15 +0200 Subject: [PATCH 10/17] docs: mention both cloud + dedicated work --- docs/hypernode-platform/cluster.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/hypernode-platform/cluster.md b/docs/hypernode-platform/cluster.md index 92cd333a..d03c90a9 100644 --- a/docs/hypernode-platform/cluster.md +++ b/docs/hypernode-platform/cluster.md @@ -13,6 +13,10 @@ and that the server is as fast as possible. However, if you have a lot of traffi cluster setup. This is a setup where you have multiple servers, each with their own task. This way, you can scale your setup to your needs. +Hypernode Cluster is available for both cloud and dedicated nodes. Dedicated nodes benefit extra from a cluster setup, as they +are more prone to going down because of hardware failures. With a cluster setup, you can make sure that your setup stays up +even if one of your servers fails. + ## Cluster vs single server Choosing between a single server setup and a cluster setup is a trade-off between performance and flexibility. A single server From 43a0dd102221b5b20b2426cc9e655a30f4ff8aa7 Mon Sep 17 00:00:00 2001 From: Timon de Groot Date: Mon, 21 Aug 2023 15:46:47 +0200 Subject: [PATCH 11/17] Remove old references to SSL hypernode.nl article --- .../magento-1/how-to-configure-varnish-for-magento-1-x.md | 2 +- .../how-to-order/how-to-order-a-domain-presence-plan.md | 4 ++-- .../nginx/how-to-configure-your-shop-to-only-use-https.md | 4 ---- ...ificate-and-more-frequently-asked-questions-about-ssl.md | 6 +++--- 4 files changed, 6 insertions(+), 10 deletions(-) diff --git a/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md b/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md index 74d13df0..50ec2172 100644 --- a/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md +++ b/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md @@ -143,4 +143,4 @@ HTTP/1.1 200 0.79 secs: 14856 bytes ==> /vogelbekdier.html ## Troubleshooting -If your Varnish setup is not working over SSL, check [this article](../../hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md#redirecting-to-https-when-using-varnish). +If your Varnish setup is not working over SSL, check [this article](../../hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md#redirecting-to-https-when-using-varnish). diff --git a/docs/getting-started/how-to-order/how-to-order-a-domain-presence-plan.md b/docs/getting-started/how-to-order/how-to-order-a-domain-presence-plan.md index 42ad39d0..7bbae718 100644 --- a/docs/getting-started/how-to-order/how-to-order-a-domain-presence-plan.md +++ b/docs/getting-started/how-to-order/how-to-order-a-domain-presence-plan.md @@ -53,6 +53,6 @@ A complete list of extensions we offer can be found [here](https://www.byte.nl/d You can read a detailed description of the step-by-step plan [here](../../services/domain-procedures/how-to-use-domains-in-the-control-panel.md#transfer-an-existing-domain-to-hypernode). -**How can I order a SSL certificate?** +**How can I order an SSL certificate?** -You can read a detailed description of the step-by-step plan [here](../../hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md#order-an-ssl-certificate). +You can read a detailed description of the step-by-step plan [here](../../hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md#buy-an-ssl-certificate-via-hypernode-recommended). diff --git a/docs/hypernode-platform/nginx/how-to-configure-your-shop-to-only-use-https.md b/docs/hypernode-platform/nginx/how-to-configure-your-shop-to-only-use-https.md index 3a239128..6f4ee2ca 100644 --- a/docs/hypernode-platform/nginx/how-to-configure-your-shop-to-only-use-https.md +++ b/docs/hypernode-platform/nginx/how-to-configure-your-shop-to-only-use-https.md @@ -24,10 +24,6 @@ You can find more in-depth information in [this article about SSL on Hypernode]( Please check out [this article](../ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md) for the different SSL options when you use the Hypernode Control Panel. -## How to Use SSL Certificates via Hypernode.nl - -Please check out [this article](../ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md) for the different SSL options when you use the Byte Service Panel. - ## Order Let’s Encrypt Certificates ### On Hypernodes With Hypernode Managed Vhosts Enabled diff --git a/docs/hypernode-platform/ssl/how-to-validate-your-ssl-certificate-and-more-frequently-asked-questions-about-ssl.md b/docs/hypernode-platform/ssl/how-to-validate-your-ssl-certificate-and-more-frequently-asked-questions-about-ssl.md index 9af30fc4..a8faa679 100644 --- a/docs/hypernode-platform/ssl/how-to-validate-your-ssl-certificate-and-more-frequently-asked-questions-about-ssl.md +++ b/docs/hypernode-platform/ssl/how-to-validate-your-ssl-certificate-and-more-frequently-asked-questions-about-ssl.md @@ -38,7 +38,7 @@ The costs for an SSL certificate consist of two aspects: the costs for the actua The certificate costs you pay for an SSL certificate that you order via Hypernode, is the purchase prise we pay at our supplier. We arrange the entire SSL application for you. You do not have to do anything more than to order the certificate in your Service Panel. Only with EV-SSL you still have to take care of a number of things (as explained [here](#what-kind-of-certificates-can-i-order-via-hypernode)). -In the background, the certificate is requested with the correct data, the validation is done (place file, perform validation), the certificate is retrieved and safely stored in the right place. We ensure that your SSL certificate works properly, even if you change your plan. All you have to take care of is to install the SSL on the right Hypernode (which can be done with [one click](../ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md#install-the-ssl-certificate-on-your-hypernode)). +In the background, the certificate is requested with the correct data, the validation is done (place file, perform validation), the certificate is retrieved and safely stored in the right place. We ensure that your SSL certificate works properly, even if you change your plan. All you have to take care of is to link the SSL certificate to the right Hypernode (which can be done with [one click](../ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md#link-a-third-party-ssl-certificate-to-a-hypernode)). ### Your SSL Certificate Is Automatically Renewed @@ -82,7 +82,7 @@ So first make sure that you have ordered a Presence plan, even if your domain is ## How Do I Order an SSL Certificate? -You can request an SSL certificate via our Service Panel. You can order this as an add-on to a Presence package. You can find out how to do that [here](../ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md#buy-an-ssl-certificate-via-hypernode-recommended). +You can order an SSL certificate in the Control Panel. You can find out how to do that [here](../ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md#buy-an-ssl-certificate-via-hypernode-recommended). ## How Can I Link the SSL Certificate to the Hypernode? @@ -114,4 +114,4 @@ Make sure there are no more redirects to the HTTPS version of your site. ## Can I Use My Own SSL Certificate? -You can also use a (custom) SSL certificate you purchased elsewhere on a Hypernode. You can find out how to install this on your Hypernode [here](../ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md#add-a-custom-ssl-certificate). +You can also use a (custom) SSL certificate you purchased elsewhere on a Hypernode. You can find out how to install this on your Hypernode [here](../ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md#add-a-third-party-ssl-certificate-to-your-account). From bf658cbb730b39d3932643c458cf26a30e514ae9 Mon Sep 17 00:00:00 2001 From: Alexander Grooff Date: Mon, 21 Aug 2023 16:01:00 +0200 Subject: [PATCH 12/17] docs: brancher cleanup script --- .../tools/hypernode-brancher.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/docs/hypernode-platform/tools/hypernode-brancher.md b/docs/hypernode-platform/tools/hypernode-brancher.md index 68271ce5..4a316545 100644 --- a/docs/hypernode-platform/tools/hypernode-brancher.md +++ b/docs/hypernode-platform/tools/hypernode-brancher.md @@ -225,6 +225,31 @@ Brancher App 'example-eph123456' deleted. See hypernode-systemctl brancher --lis Brancher App 'example-eph234567' deleted. See hypernode-systemctl brancher --list for the list of remaining brancher apps. ``` +##### Example cleanup script + +To prevent long running Hypernode Brancher nodes from accumulating, you can use the following script to clean up old Brancher nodes. This is configured to delete all Brancher nodes that have been running for more than 4 hours: + +```bash +MAX_MINUTES_ALIVE=240 +LONG_RUNNING_BRANCHERS=$(hypernode-systemctl brancher --list --machine-readable | jq -r '.[] | select (.minutes>='"${MAX_MINUTES_ALIVE}"') | .name') + +if [ -z "${LONG_RUNNING_BRANCHERS}" ]; then + echo "No long running Brancher nodes found" + exit 0 +fi + +for BRANCHER in ${LONG_RUNNING_BRANCHERS}; do + echo "Deleting Brancher node ${BRANCHER}" + hypernode-systemctl brancher --delete "${BRANCHER}" +done +``` + +You can convert this to a single line if you're into that: + +```bash +hypernode-systemctl brancher --list --machine-readable | jq -r '.[] | select (.minutes>=240) | .name' | xargs -n1 --no-run-if-empty hypernode-systemctl brancher --delete +``` + ## Brancher Install Hook While it's already very valuable to be able to create a running copy of your Hypernode, it is a very common use case to make some configuration changes. From d431c1ae632f89622da0e4221e697b304dee2f27 Mon Sep 17 00:00:00 2001 From: dvd2david <126869057+dvd2david@users.noreply.github.com> Date: Tue, 5 Sep 2023 16:55:54 +0200 Subject: [PATCH 13/17] Update emergency-support-outside-office-hours.md removed chat function mentions --- .../support/emergency-support-outside-office-hours.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/about-hypernode/support/emergency-support-outside-office-hours.md b/docs/about-hypernode/support/emergency-support-outside-office-hours.md index 8defeba0..4fda294f 100644 --- a/docs/about-hypernode/support/emergency-support-outside-office-hours.md +++ b/docs/about-hypernode/support/emergency-support-outside-office-hours.md @@ -25,8 +25,7 @@ During office hours (from 9:00 AM – 6 PM CE(S)T) you can request Hypernode Eme ### Step 1 Send a Request to the Hypernode Emergency Service Team -- **Basic SLA** Via the online form on [hypernode-emergency.com](http://hypernode-emergency.com) -- **Standard SLA** Via chat on [hypernode-emergency.com](http://hypernode-emergency.com) + Via the online form on [hypernode-emergency.com](http://hypernode-emergency.com) ### Step 2 The Request is Sent to the On Duty Hero From 7cc05e1e7b455a8d11fb7fd2f9c4ea5ecab86c51 Mon Sep 17 00:00:00 2001 From: Rick van de Loo Date: Tue, 5 Sep 2023 16:55:06 +0200 Subject: [PATCH 14/17] format the emergency-support doc --- .../support/emergency-support-outside-office-hours.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/about-hypernode/support/emergency-support-outside-office-hours.md b/docs/about-hypernode/support/emergency-support-outside-office-hours.md index 4fda294f..da5006ab 100644 --- a/docs/about-hypernode/support/emergency-support-outside-office-hours.md +++ b/docs/about-hypernode/support/emergency-support-outside-office-hours.md @@ -25,7 +25,7 @@ During office hours (from 9:00 AM – 6 PM CE(S)T) you can request Hypernode Eme ### Step 1 Send a Request to the Hypernode Emergency Service Team - Via the online form on [hypernode-emergency.com](http://hypernode-emergency.com) +Via the online form on [hypernode-emergency.com](http://hypernode-emergency.com) ### Step 2 The Request is Sent to the On Duty Hero From c4ffbbfd64fc233c8469bfb87d622288b505c884 Mon Sep 17 00:00:00 2001 From: Rick van de Loo Date: Wed, 6 Sep 2023 14:46:26 +0200 Subject: [PATCH 15/17] add php-amqp to docs --- .../tools/how-to-use-the-hypernode-systemctl-cli-tool.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md b/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md index f4dc92be..dfc02f35 100644 --- a/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md +++ b/docs/hypernode-platform/tools/how-to-use-the-hypernode-systemctl-cli-tool.md @@ -48,7 +48,8 @@ To see which values you can set and which values they are allowed to have take a - `password_auth`: indicates whether password authentication for the Hypernode is allowed instead of only SSH keys. - `permissive_memory_management`: Configure [memory management policy](https://changelog.hypernode.com/release-5946-configurable-memory-management-policy-and-rss-bruteforce-detection/) (OOM kills) - `php_version`: Change the PHP version -- `php_apcu_enabled`: Enable the PHP-apcu +- `php_apcu_enabled`: Enable the php-apcu module +- `php_amqp_enabled`: Enable the php-amqp module - `redis_persistent_instance` - `redis_version`: Change the Redis version - `rabbitmq_enabled`: a popular open source message broker From 892b886ddfd62df44c52c6ad9b12807e83848b0b Mon Sep 17 00:00:00 2001 From: Timon de Groot Date: Tue, 12 Sep 2023 11:46:11 +0200 Subject: [PATCH 16/17] Update magento 2 installation php version note --- .../magento-2/how-to-install-magento-2-on-hypernode.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ecommerce-applications/magento-2/how-to-install-magento-2-on-hypernode.md b/docs/ecommerce-applications/magento-2/how-to-install-magento-2-on-hypernode.md index e0c1b92b..5b4205c8 100644 --- a/docs/ecommerce-applications/magento-2/how-to-install-magento-2-on-hypernode.md +++ b/docs/ecommerce-applications/magento-2/how-to-install-magento-2-on-hypernode.md @@ -20,7 +20,7 @@ Installing Magento 2 will take only 5-10 minutes (add 15 minutes if you want the ## Upgrade Your PHP Version -**Before installing Magento,**[**change your PHP version**](../../hypernode-platform/php/supported-php-versions-and-how-to-change-them-on-hypernode.md#changing-the-php-version-you-use-on-hypernode)**to php7.1 or higher** +**Before installing Magento, [change your PHP version](../../hypernode-platform/php/supported-php-versions-and-how-to-change-them-on-hypernode.md#changing-the-php-version-you-use-on-hypernode) to 8.1 or higher** Some vendor libraries are not compatible with older PHP version anymore, causing errors during the installation. From 6b9a990075383cd8cbd7327120532328ca7c8110 Mon Sep 17 00:00:00 2001 From: Staging Jenkins Date: Thu, 21 Sep 2023 10:44:49 +0000 Subject: [PATCH 17/17] [automated] Marking Release 20230921.104418 --- debian/changelog | 248 ++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 246 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index 6c407ac5..56a6f29b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -hndocsnext (20230208.082003) UNRELEASED; urgency=medium +hndocsnext (20230921.104418) UNRELEASED; urgency=medium [ Rick van de Loo ] * Initial packaging @@ -127,5 +127,249 @@ hndocsnext (20230208.082003) UNRELEASED; urgency=medium [ Timon de Groot ] * docs/brancher: Add label/clear_services examples to hnapi / hndeploy + * docs: Add docs for GitHub Actions and Gitlab CI + * Apply suggestions from code review + * docs/hndeploy: Add note about CI container image + * ci: Report changed pages + * ci: Only allow index, follow for production - -- Hypernode team Wed, 08 Feb 2023 08:20:11 +0000 + [ Lianne van Looij ] + * Update what-kind-of-emails-does-hypernode-send.md + + [ Cipriano Groenendal ] + * Use example.com and example.hypernode.io + + [ Lianne van Looij ] + * Updated DNS article to Control Panel + + [ Cipriano Groenendal ] + * Update how-to-resolve-rate-limited-requests-429-too-many-requests.md + * chore: mdformat + * chore: mdformat + + [ RensZuurbier ] + * replace_create_project_with_wget_link + + [ Cipriano Groenendal ] + * chore: mdformat + * Update how-to-use-mysql-on-hypernode.md + + [ Lianne van Looij ] + * chore: apply mdformat + + [ Cipriano Groenendal ] + * Update how-to-use-mysql-on-hypernode.md + + [ Timon de Groot ] + * Fix incorrect internal URL + + [ Nick ] + * Updated the PNL command with 'ua' (line 36). + + [ Alexander Grooff ] + * feat: codespaces template + + [ Cipriano Groenendal ] + * Update how-to-use-mysql-on-hypernode.md + * Update how-to-use-mysql-on-hypernode.md + * Update how-to-use-mysql-on-hypernode.md + + [ Lianne van Looij ] + * Delete old article for SP (2FA) + + [ Cipriano Groenendal ] + * chore: mdformat + * Remove duplicate bit + * Update inbound links + * Use correct language indicators + * Clear up examples + + [ Timon de Groot ] + * Use composer to install akeneo with version + + [ Lianne van Looij ] + * New doc: Domain extensions + + [ Timon de Groot ] + * Remove pim-community-standard directory naming + * Fix document name and add heading + + [ Lianne van Looij ] + * Update which-tlds-does-hypernode-offer.md + + [ Timon de Groot ] + * ci: Use docs.hypernode.io for Brancher instances + * Fix formatting for doc + + [ Lianne van Looij ] + * Update which-tlds-does-hypernode-offer.md + * Update which-tlds-does-hypernode-offer.md + + [ rednaslaarom ] + * Sentence removed + + [ Timon de Groot ] + * Update Hypernode Docker article + + [ Cipriano Groenendal ] + * Add Swapnil Kothawade + * chore: mdformat + + [ Lianne van Looij ] + * Updated TLD article with extra info + * chore:apply mdformat + * Added missing link to TLD article + + [ Cipriano Groenendal ] + * Update default allowlist + + [ Rick van de Loo ] + * replace dealer4dealer user agent with xcore + * whitelist Mollie in default bots docs + + [ Timon de Groot ] + * akeneo6: Simplify article + + [ Lianne van Looij ] + * Removed SP specific info from SSH article + + [ Timon de Groot ] + * brancher: Add documentation for the Brancher install hook + + [ dvd2david ] + * Update how-to-configure-nginx-for-a-multistore.md + + [ RensZuurbier ] + * update-trailing-slash + * adding-trailing-slash-v2 + + [ Lianne van Looij ] + * Delete how to autoresponder + * Delete conflict between merchant and webdesigner + * Updated different control panel scenarios + * chore: apply mdformat + * Email preferences screenshots + + [ Niutoseq ] + * adding feedback group tile to docs + + [ Timon de Groot ] + * ci: Report sphinx build errors to Github Actions workflow summary + + [ Cipriano Groenendal ] + * Update how-to-restrict-access-to-your-admin-area.md + * Update how-to-restrict-access-to-your-admin-area.md + * chore: mdformat + + [ Lianne van Looij ] + * Created Hipex-Hypernode Billing FAQ + * chore: apply mdformat + * Update waarom-facturatie-vanuit-hypernode-ipv-hipex.md + + [ Timon de Groot ] + * Update waarom-facturatie-vanuit-hypernode-ipv-hipex.md + + [ Lianne van Looij ] + * Updated billing article - missed a header + + [ Henk Valk ] + * Update how-to-configure-redis-for-magento-2.md + + [ Hypernode Support ] + * Update path were to set sitemap magento 2 + + [ Timon de Groot ] + * Change PM2 documentation + + [ Lianne van Looij ] + * Delete Service Panel specific document + * Delete how to login to Service Panel + * Removed SP specific info in how to cancel + * Removed SP specific info + * Deleting billing FAQ for SP + * Delete how-to-block-bad-bots-via-the-SP + * Updated Supported PHP versions + + [ Timon de Groot ] + * Remove unnecessary service panel reference + * Remove service-panel.md + * Improve blackfire doc + + [ Henk Valk ] + * Update how-to-find-your-performance-bottleneck-with-new-relic.md + + [ Rick van de Loo ] + * fix login link control panel in newrelic doc + + [ Niutoseq ] + * fixing commit + * fixing mobile search bar + * changing the text in right panel on Tom request + + [ Timon de Groot ] + * Apply updated documentation formatting + * magento2/varnish: Remove mention of service panel + * magento2/varnish: Remove weird * characters around hmv link + * magento2/varnish: Remove VCL tip + * magento2/varnish: Add performance improvement section + * Update docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md + + [ Cipriano Groenendal ] + * Update security-hall-of-fame.md + * Fix link + + [ Timon de Groot ] + * tools/nodejs: Update documentation + * magento2/varnish: Remove unnecessary bash semicolons + * platform/brancher: Add note about Falcon/Eagle availability + * Update docs/hypernode-platform/tools/hypernode-brancher.md + * support: Update office hours in docs + + [ Erwin Romkes ] + * Update how-to-use-the-hypernode-systemctl-cli-tool.md + + [ Cipriano Groenendal ] + * Create incident-response-policy.md + * Add Arthur Sjouw + + [ dvd2david ] + * Update how-to-copy-your-hypernode-to-another-hypernode.md + + [ timhipex ] + * Update how-to-set-magento-2-x-to-the-utc-timezone.md + + [ Rolf van de Bovenkamp ] + * Updated how-to-configure-varnish-for-shopware-6 removed hypernode VCL because it is outdated + + [ reggysupport ] + * Deleted old Service Panel part on how-to-configure-ftp-sftp-on-hypernode.md + * Delete dns-for-service-panel-users.md + * Delete old Service Panel topic - Update how-to-configure-varnish-for-magento-1-x.md + * Delete how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-nl.md + * Deleted old Service Panel topic - Update how-to-use-hypernode-development-plans.md + + [ dvd2david ] + * Update how-to-configure-ftp-sftp-on-hypernode.md + + [ Alexander Grooff ] + * docs: general cluster documentation + * chore: mdformat + * docs: mention both cloud + dedicated work + + [ Timon de Groot ] + * Remove old references to SSL hypernode.nl article + + [ Alexander Grooff ] + * docs: brancher cleanup script + + [ dvd2david ] + * Update emergency-support-outside-office-hours.md + + [ Rick van de Loo ] + * format the emergency-support doc + * add php-amqp to docs + + [ Timon de Groot ] + * Update magento 2 installation php version note + + -- Hypernode team Thu, 21 Sep 2023 10:44:49 +0000