From f037e12aa2f9f42e348517126293aa02f0cfb080 Mon Sep 17 00:00:00 2001 From: poespas Date: Wed, 16 Sep 2026 11:55:45 +0200 Subject: [PATCH 1/2] Remove dead links and references to Byte Service Panel --- .../billing-faq-for-the-control-panel.md | 1 + ...ontrol-panel-billing-facturen-faq-dutch.md | 86 ------------------- ...f-your-magento-extensions-is-vulnerable.md | 2 +- .../email/how-to-export-your-emails.md | 17 +--- ...ng-sent-from-your-name-or-email-address.md | 2 +- ...ow-hypernode-protects-your-magento-shop.md | 2 +- .../security/how-to-apply-magento-patches.md | 14 +-- ...malicious-javascript-credit-card-hijack.md | 2 +- ...ento-patch-supee-8788-and-release-1-9-3.md | 2 +- ...ect-magento-against-brute-force-attacks.md | 4 +- .../how-to-recover-a-hacked-magento-shop.md | 2 +- .../how-to-secure-magento-cacheleak.md | 2 +- ...ow-to-use-a-cloud-firewall-on-hypernode.md | 2 +- .../how-to-go-live-with-your-hypernode.md | 8 +- .../testing/hypernode-docker.md | 6 +- .../zero-downtime-deployment-on-hypernode.md | 2 +- ...press-next-to-your-magento-installation.md | 2 +- .../best-practices/usage/hypernode-magerun.md | 2 +- ...ow-to-configure-varnish-for-magento-1-x.md | 9 +- ...o-reset-your-magento-1-x-admin-password.md | 2 +- ...-up-a-staging-environment-for-magento-1.md | 2 +- ...onfigure-remote-storage-for-magento-2-x.md | 2 +- ...basic-staging-environment-for-magento-2.md | 2 +- .../magento-2/how-to-update-magento-2.md | 2 +- ...how-to-configure-varnish-for-shopware-5.md | 2 +- ...-install-shopware-5-on-hypernode-docker.md | 2 +- ...nfigure-remote-storage-for-shopware-6-x.md | 2 +- ...-install-shopware-6-on-hypernode-docker.md | 4 +- .../how-to-install-shopware-6-on-hypernode.md | 4 +- ...sic-staging-environment-with-shopware-6.md | 2 +- ...how-to-install-woocommerce-on-hypernode.md | 2 +- ...o-get-started-with-your-hypernode-trial.md | 8 +- .../applications/config-for-magento-1.md | 29 +++++++ .../applications/config-for-magento-2.md | 17 +++- .../applications/config-for-nextjs.md | 8 ++ .../applications/config-for-shopware-6.md | 8 ++ docs/hypernode-deploy/pipelines.md | 12 +++ .../pipelines/bitbucket-pipelines.md | 22 +++-- .../pipelines/github-actions.md | 8 ++ docs/hypernode-deploy/pipelines/gitlab-ci.md | 8 ++ .../how-does-horizontal-autoscaling-work.md | 4 +- .../dns/dns-for-control-panel-users.md | 14 +-- ...-manage-your-dns-settings-for-hypernode.md | 4 +- ...o-set-up-your-spf-records-for-hypernode.md | 3 +- .../dns/your-dns-is-misconfigured.md | 2 +- ...ivate-a-virus-filter-for-your-email-box.md | 10 +-- .../email/how-to-configure-the-spam-filter.md | 14 +-- ...-to-set-up-your-dns-for-using-office365.md | 15 ++-- .../email/how-to-use-dmarc.md | 2 - .../how-to-configure-ftp-sftp-on-hypernode.md | 2 +- ...w-to-free-disk-space-from-mysql-ibdata1.md | 2 +- .../mysql/how-to-use-phpmyadmin.md | 2 +- .../nginx/how-to-use-nginx.md | 2 +- ...how-to-log-in-to-the-hypernode-with-ssh.md | 2 +- .../ssh/how-to-use-ssh-keys-on-hypernode.md | 2 +- ...ypernode-when-ordered-via-hypernode-com.md | 2 +- ...re-frequently-asked-questions-about-ssl.md | 8 +- .../tools/how-to-configure-lesti-fpc.md | 2 +- ...opy-your-hypernode-to-another-hypernode.md | 2 +- ...ng-running-php-processes-with-livestack.md | 4 +- .../how-to-migrate-your-shop-to-hypernode.md | 35 ++------ .../how-to-use-hypernode-development-plans.md | 2 +- .../tools/how-to-use-mailhog-on-hypernode.md | 2 +- ...se-periodic-tasks-cronjobs-on-hypernode.md | 2 +- ...to-use-the-hypernode-systemctl-cli-tool.md | 4 +- .../how-to-enable-varnish-on-hypernode.md | 2 +- .../how-to-change-your-hypernode-settings.md | 2 +- .../control-panel/how-to-use-the-dns-check.md | 2 +- ...ything-about-presence-plans-and-domains.md | 68 --------------- ...ransfer-your-domain-away-from-hypernode.md | 3 +- ...-name-to-another-provider-service-panel.md | 53 ------------ ...-undo-the-cancellation-of-a-domain-name.md | 2 - ...how-to-use-domains-in-the-control-panel.md | 1 + .../services/magereport/magereport-premium.md | 2 +- .../how-to-fix-invalid-form-key-error.md | 2 +- ...-optimise-your-magento-disk-performance.md | 2 +- 76 files changed, 209 insertions(+), 388 deletions(-) delete mode 100644 docs/about-hypernode/billing/control-panel-billing-facturen-faq-dutch.md delete mode 100644 docs/services/domain-procedures/everything-about-presence-plans-and-domains.md delete mode 100644 docs/services/domain-procedures/how-to-transfer-your-domain-name-to-another-provider-service-panel.md diff --git a/docs/about-hypernode/billing/billing-faq-for-the-control-panel.md b/docs/about-hypernode/billing/billing-faq-for-the-control-panel.md index 5f7ae012..9b4227bd 100644 --- a/docs/about-hypernode/billing/billing-faq-for-the-control-panel.md +++ b/docs/about-hypernode/billing/billing-faq-for-the-control-panel.md @@ -6,6 +6,7 @@ myst: title: Billing Control Panel FAQ | Hypernode redirect_from: - /en/about/billing/billing-faq-for-the-control-panel/ + - /en/about/billing/migration-faq/ --- diff --git a/docs/about-hypernode/billing/control-panel-billing-facturen-faq-dutch.md b/docs/about-hypernode/billing/control-panel-billing-facturen-faq-dutch.md deleted file mode 100644 index 7797ceb6..00000000 --- a/docs/about-hypernode/billing/control-panel-billing-facturen-faq-dutch.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -myst: - html_meta: - description: This FAQ covers billing and invoicing questions for customers who - are migrated from the old Dutch legacy platform (Service Panel) to the new Control - Panel. - title: Billing and Invoicing FAQ for Dutch Customers | Hypernode -redirect_from: - - /en/about/billing/migration-faq/ ---- - - - -# Control Panel Billing / Facturen FAQ (Dutch) - -***Note: This article is in Dutch because it is aimed at customers who are migrated from our old Dutch-only legacy platform (Service Panel) to the new Control Panel.*** - -We zijn dit kwartaal druk bezig om alle klanten van het oude service panel ([service.byte.nl](http://service.byte.nl)) om te zetten naar het nieuwe control panel ([my.hypernode.com](http://my.hypernode.com)). Omdat dit gepaard gaat met flink wat veranderingen en dit best wat vragen oplevert met betrekking tot facturatie hebben we deze FAQ in leven geroepen om hopelijk al je vragen te beantwoorden. - -Voor algemene informatie over wat er precies is veranderd in vergelijking met het oude service panel kun je deze flyer raadplegen: - -______________________________________________________________________ - -## Waarom betaal ik nu van te voren in plaats van achteraf voor mijn Hypernode? - -Eigenlijk simpelweg omdat we over zijn gegaan op een nieuw subscription management systeem die alleen maar met vooruitbetalingen werkt. Dit nieuwe systeem biedt een hoop voordelen en mogelijkheden voor klanten maar helaas hebben we wel deze omschakeling moeten maken. - -## Waarom betaal ik nu voor een andere contractperiode? - -Voorheen was je contractperiode afhankelijk van de dag dat je was begonnen met je Hypernode of domeinnaamregistratie. Met het control panel factureren we nu altijd gewoon van de 1ste tot de 1ste. Eventueel extra kosten voor upgrades zie je dan terug op het eerstvolgende facturen en bij downgrades wordt er een tegoed berekend op het volgende factuur. Zo blijft het eenvoudig en overzichtelijk. - -## Waarom krijg ik nu 2 of zelfs 3 facturen in 1 maand? - -Simpel gezegd komt dit omdat in meeste gevallen wij klanten niet precies op de 1ste van de maand migreren. Je hebt dus te maken met dat facturatie wordt 'afgesloten' vanuit het Service Panel, en we in het Control Panel alleen op de 1ste van elke maand factureren. - -Om de contractperiodes van het service panel en het control panel te overbruggen wordt dit als volgt opgelost, laten we even van een situatie uit gaan waar jij als klant op 15 juni gemigreerd wordt. - -- Op 1 juli ontvang je een factuur vanuit het **Control Panel**waarin je wordt gefactureerd voor - 1. De periode van 1 juli tot en met 1 augustus (want nu factureren we vooraf) - 1. De periode van 15 juni tot 1 juli (hierover corrigeren we het bedrag dat je eventueel al vooruit betaald hebt op het laatste factuur vanuit het Service Panel van mei, dit zie je onderaan het factuur terug als **promotional credits**indien van toepassing) -- Op 1 juli ontvang je ook nog een factuur vanuit het **Service Panel**voor de periode tot aan 15 juni - \*\* **Vanuit het Service Panel ontvang je mogelijk nog een derde en laatste factuur** voor de periode vanaf de originele contractdatum tot en met 15 juni. Dit is dus alleen het geval als je bijvoorbeeld een Hypernode hebt die liep van 12 mei tot en met 12 juli terwijl je daar in die periode nog geen factuur voor hebt ontvangen.\* - -## Ik word dubbel gefactureerd voor dezelfde periode, waarom is dat? - -Je wordt niet dubbel gefactureerd maar dit lijkt wellicht zo omdat je 2 of zelfs 3 facturen hebt ontvangen in korte tijd, en je nu dus ook vooraf betaald inplaats van achteraf. Zie de uitleg hierboven onder de vraag 'Waarom krijg ik nu 2 of zelfs 3 facturen in 1 maand' hoe dat precies ziet. - -Bij twijfel kun je altijd mailen naar [billing@hypernode.com](mailto:billing@hypernode.com) dan zoeken we dit graag voor je uit - -## Waar is de iDEAL / Betaal knop bij mijn factuur? - -Helaas kunnen wij die niet meer aanbieden, al hebben we wel een verzoek ingediend bij onze payment provider om dit weer mogelijk te maken. Je kunt nu echter wel gebruik maken van automatisch incasso (dit gebruikt voor Nederlandse klanten ook iDEAL als verificatie) en Credit Card, daarmee hoef je dus helemaal niet meer om te kijken naar je facturen. - -## Waarom ziet mijn factuur er anders uit? - -Omdat we naar een nieuw systeem zijn over gegaan en we ook de mogelijkheid hebben genomen om alles te updaten naar ons nieuwe design die matched met onze website. Factuurnummers bestaan nu dus ook uit 4 cijfers (in de toekomst 5). - -## Waarom is alles in het Engels? - -We zijn steeds meer Internationale klanten aan het bedienen en omdat wij deze markt niet willen buitensluiten en Nederlandse bedrijven ook steeds vaker mensen in dienst hebben die geen Nederlands spreken hebben we ervoor gekozen nu alles primair in het Engels te doen. Je kunt natuurlijk wel altijd nog gewoon in het Nederlands contact met ons ons support team communiceren. - -## Kan ik nu met automatisch incasso betalen? - -Dat kan zeker, en je kunt nu zelfs ook met Credit Card betalen. Dit doe je simpelweg door in te loggen op [my.hypernode.com](https://my.hypernode.com). Vervolgens druk je op je profiel rechtsboven en ga je naar Billing Portal: - -![](_res/paSdE2q60V3Q_Kc_FulzAluhCvYzJ6j0PQ.png) - -Vervolgens kies je voor 'Payment methods' en kies je daar je gewenste betaalmethode: - -![](_res/vk4S5HryCx51RkcUKy9-eUZZAtzDxw1PMQ.png) - -## Waar kan ik mijn oude facturen van het service panel terugvinden? - -Helaas zijn deze niet meer direct toegankelijk, mail naar [billing@hypernode.com](mailto:billing@hypernode.com) en geef aan voor welke periode je de facturen wilt ontvangen dan sturen we deze graag nog naar je toe. - -## Hoe kan ik mijn bedrijfsnaam/btw nummer/adresgegevens op het factuur krijgen? - -Dit doe je via het eerder genoemde Billing Portal (zie uitleg 'Kan ik nu met automatisch incasso betalen?' alleen ga je daar naar \*\*Billing & Shipping Addresses.\*\*Alle informatie die je bij 'Billing' aanpast zal op het eerstvolgende factuur verschijnen. - -## Kan ik een mail adres opgeven waar alle facturen naar worden gestuurd? - -Jazeker, het mail adres die je bij **Billing & Shipping Addresses**gebruiken wij om direct de facturen naar toe te sturen. - -## Wat als ik verder nog vragen heb? - -Zet je vraag graag op de mail naar [billing@hypernode.com](mailto:billing@hypernode.com), je kunt ons ook telefonisch benaderen voor vraagstukken maar gezien vragen over facturatie nog best vaak wat uitzoekwerk vergt nemen we liever graag de tijd om hier goed in te duiken, en dit gaat simpelweg makkelijker via e-mail. Je kunt in meeste gevallen verwachten dat wij binnen 1 werkdag reageren. diff --git a/docs/about-hypernode/security-policies/one-of-your-magento-extensions-is-vulnerable.md b/docs/about-hypernode/security-policies/one-of-your-magento-extensions-is-vulnerable.md index ddd55f78..d9f0c28d 100644 --- a/docs/about-hypernode/security-policies/one-of-your-magento-extensions-is-vulnerable.md +++ b/docs/about-hypernode/security-policies/one-of-your-magento-extensions-is-vulnerable.md @@ -52,4 +52,4 @@ To verify if your shop is hacked or not, [use the article about recovering a hac ## Need help? -Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to contact [one of these agencies](https://www.magereport.com/page/support). +Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to contact [one of these agencies](https://www.hypernode.com/en/our-partners/). diff --git a/docs/best-practices/email/how-to-export-your-emails.md b/docs/best-practices/email/how-to-export-your-emails.md index 3e4c2277..40474bf9 100644 --- a/docs/best-practices/email/how-to-export-your-emails.md +++ b/docs/best-practices/email/how-to-export-your-emails.md @@ -2,8 +2,7 @@ myst: html_meta: description: Learn how to export your emails from various email clients such as - Byte Webmail, Outlook, Mozilla Thunderbird and Mac Mail. Follow our step-by-step - guide. + Outlook, Mozilla Thunderbird and Mac Mail. Follow our step-by-step guide. title: How to Export your Emails? | Hypernode redirect_from: - /en/best-practices/email/how-to-export-your-emails/ @@ -13,19 +12,7 @@ redirect_from: # How to Export your Emails -In this article we explain how you can export your email with a number of common email clients and our own webmail application. - -## Export email in Byte Webmail - -In the Byte webmail client it is not possible to export all the emails at once, so you have to save each email individually. - -1. Log in to the Byte webmail application. - -1. Click on an email. - -1. In the menu item More, select the option 'Opslaan' (.eml) - -An .eml file is then created in which the specific email is stored. You can then import this .eml file back into your email client. Please note that you cannot import email into Byte's webmail. +In this article we explain how you can export your email with a number of common email clients. ## Export Email in Outlook diff --git a/docs/best-practices/email/how-to-prevent-spam-being-sent-from-your-name-or-email-address.md b/docs/best-practices/email/how-to-prevent-spam-being-sent-from-your-name-or-email-address.md index ed354860..038ce945 100644 --- a/docs/best-practices/email/how-to-prevent-spam-being-sent-from-your-name-or-email-address.md +++ b/docs/best-practices/email/how-to-prevent-spam-being-sent-from-your-name-or-email-address.md @@ -25,7 +25,7 @@ It may happen that others send mail in your name. These could be viruses that ha The email system does not provide for sender verification, so it is possible to specify anything. However, there a few things you could try to minimise the chances of this happening: - If you get a lot of responses from a single person, you can have this sender blocked by your mail program. -- If the responses are sent to an address that falls under your Catch All, but that you don't actually use, you can disable this specific address via the Service Panel. For this you create an extra address (the address to which the messages will be sent) and have the mail forwarded to “nobody”. The messages will then be discarded. +- If the responses are sent to an address that falls under your Catch All, but that you don't actually use, you can have this specific address disabled by [support@hypernode.com](mailto:support@hypernode.com). For this you create an extra address (the address to which the messages will be sent) and have the mail forwarded to “nobody”. The messages will then be discarded. - Tighten your SPF record with -all at the end, so that anything that is not formulated in your SPF record will not be accepted by the receiving mail server. - Make sure you have SAV enabled in all your mailboxes. \*\*Please note:\*\*This construction only works if no mailboxes have been selected, and no other external addresses have been specified. diff --git a/docs/best-practices/security/how-hypernode-protects-your-magento-shop.md b/docs/best-practices/security/how-hypernode-protects-your-magento-shop.md index 6a7cd0a7..71fb7c76 100644 --- a/docs/best-practices/security/how-hypernode-protects-your-magento-shop.md +++ b/docs/best-practices/security/how-hypernode-protects-your-magento-shop.md @@ -12,7 +12,7 @@ redirect_from: # How Hypernode protects your Magento shop -Due to the standardisation of the ecosystem of Hypernode and our continuous integration pipeline, we can implement changes to all Hypernodes in no time. From the moment a security issue becomes known, a Magento patch for example, [we are able to block security threads on our complete platform in less than 4 hours](https://www.hypernode.com/blog/security/how-hypernode-identifies-and-blocks-new-security-threats-within-the-hour). This way we can offer our customers premium protection. +Due to the standardisation of the ecosystem of Hypernode and our continuous integration pipeline, we can implement changes to all Hypernodes in no time. From the moment a security issue becomes known, a Magento patch for example, [we are able to block security threads on our complete platform in less than 4 hours](../../about-hypernode/security-policies/hypernode-security-statement.md). This way we can offer our customers premium protection. But, this is not only applicable for acute security issues. As Magento nerds we know that development files also need to be protected and that the Magmi tool can create a huge security hazard for example. Such risks are proactively taken care of at Hypernode. diff --git a/docs/best-practices/security/how-to-apply-magento-patches.md b/docs/best-practices/security/how-to-apply-magento-patches.md index a3e9b684..ca19f454 100644 --- a/docs/best-practices/security/how-to-apply-magento-patches.md +++ b/docs/best-practices/security/how-to-apply-magento-patches.md @@ -41,9 +41,9 @@ Log on to the shell server. If you don’t how to log on, contact your hosting p ### Step 3: Download and Upload the Patch -To download the correct patch for your webshop you need to know what version of Magento you’re using. Don’t know what version you use? Find out using [this tutorial](https://www.euperia.com/development/how-to-find-the-magento-version/844). +To download the correct patch for your webshop you need to know what version of Magento you’re using. Don’t know what version you use? You can find it in the back-end of your Magento shop under **System > Tools > Compilation**, or by checking the `app/Mage.php` file. -Download the patch(es) you need via the [Magento downloads page](http://magento.com/security/patches). Upload the patch with SSH to your Magento folder. +Download the patch(es) you need via the [Magento downloads page](https://magento.com/security/patches). Upload the patch with SSH to your Magento folder. ### Step 4: Apply the Patch @@ -56,11 +56,11 @@ app@abcdef-example-magweb-cmbl:~/magento$ bash patch_supee-5994.sh ### Step 5: Clear Your Cache -It’s important to flush the Magento cache after applying the patch. Flushing your caches can be done in the back-end of your Magento shop under Cache management. More info about flushing your cache in the back-end of Magento can be found in the [Magentocommerce Knowledgebase](http://www.magentocommerce.com/knowledge-base/entry/cache-storage-management/%09200). Don’t forget to flush your OPcode or APC cache as well! +It’s important to flush the Magento cache after applying the patch. Flushing your caches can be done in the back-end of your Magento shop under Cache management. More info about flushing your cache in the back-end of Magento can be found in the [Adobe Commerce documentation](https://experienceleague.adobe.com/en/docs/commerce-admin/systems/tools/cache-management). Don’t forget to flush your OPcode or APC cache as well! ### Step 6: Check Your Shop -Don’t forget to check your shop for vulnerabilities after patching and flushing your caches. Magento’s [Security Patch Page](http://magento.com/security-patch) provides a list of signs to look out for to determine whether your site is comprised or not. +Don’t forget to check your shop for vulnerabilities after patching and flushing your caches. Adobe’s [Security Patch Page](https://magento.com/security/patches) provides a list of signs to look out for to determine whether your site is comprised or not. ### Step 7: Clean up the Patch @@ -103,12 +103,12 @@ In this example only SUPEE-5344 has been applied. When you uninstalled a patch, **Magereport keeps saying security patch 6482 isn’t installed** -We found out that there are several reasons why Patch 6788 comes out as uninstalled on [MageReport.com.](https://www.magereport.com/page/support), so we recommend you to check the following: +We found out that there are several reasons why Patch 6788 comes out as uninstalled on [MageReport.com.](https://www.magereport.com/), so we recommend you to check the following: -- When compilation is enabled in the backend of your Magento, SUPEE-6482 doesn’t work properly. Disable compilation (navigate to System > Tools > Compilation page and click on Disable button) to make sure the patch works. After disabling compilation, check your site with [MageReport.com.](https://www.magereport.com/page/support) again. If the check still comes out as not installed, try re-compiling. +- When compilation is enabled in the backend of your Magento, SUPEE-6482 doesn’t work properly. Disable compilation (navigate to System > Tools > Compilation page and click on Disable button) to make sure the patch works. After disabling compilation, check your site with [MageReport.com.](https://www.magereport.com/) again. If the check still comes out as not installed, try re-compiling. - Check if the patch is installed in the correct directory; - Reload your opcode cache, webserver, php-fpm process and possible other caches. The old code might be still be active; - Check your shops’ .htaccess. If you’ve made any adjustements in your .htaccess, it’s possible the patch is only partially installed; - Using a Magento version older than Magento 1.6.1.0? Update to a more recent version. When patching Magento versions older than Magento 1.6.1.0, certain redirects aren’t added. -We hope one of the causes mentioned above can fix your problem. If not, we recommend you to hire a Magento specialist. Unfortunately we can’t help fixing these problems. We’re a hosting company that specializes in Magento hosting. Magento development however is a completely different specialty. A list of Magento developers per country can be found on [MageReport.com.](https://www.magereport.com/page/support) +We hope one of the causes mentioned above can fix your problem. If not, we recommend you to hire a Magento specialist. Unfortunately we can’t help fixing these problems. We’re a hosting company that specializes in Magento hosting. Magento development however is a completely different specialty. A list of Magento developers per country can be found on [MageReport.com.](https://www.hypernode.com/en/our-partners/) diff --git a/docs/best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md b/docs/best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md index b2190d43..68edc2a5 100644 --- a/docs/best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md +++ b/docs/best-practices/security/how-to-fix-malicious-javascript-credit-card-hijack.md @@ -174,4 +174,4 @@ We recommend you ‘clean’ your shop following the steps written in the articl ## Need Help? -Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to [contact one of these agencies](https://www.magereport.com/page/support). +Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to [contact one of these agencies](https://www.hypernode.com/en/our-partners/). diff --git a/docs/best-practices/security/how-to-install-magento-patch-supee-8788-and-release-1-9-3.md b/docs/best-practices/security/how-to-install-magento-patch-supee-8788-and-release-1-9-3.md index 009f2531..3225e5c9 100644 --- a/docs/best-practices/security/how-to-install-magento-patch-supee-8788-and-release-1-9-3.md +++ b/docs/best-practices/security/how-to-install-magento-patch-supee-8788-and-release-1-9-3.md @@ -19,7 +19,7 @@ This patch fixes about 17 issues, some of which are highly critical. They allow ## How to Install the Patch -Follow the regular patch instructions. If you run into problems, please visit the [8788 answers page at the StackExchange](http://magento.stackexchange.com/questions/140550/security-patch-supee-8788-possible-problems). +Follow the regular patch instructions. If you run into problems, please visit the [8788 answers page at the StackExchange](https://magento.stackexchange.com/questions/140550/security-patch-supee-8788-possible-problems). Notably: the patch contains binary characters. So you should probably not open it with a regular editor, as that will mangle the data. diff --git a/docs/best-practices/security/how-to-protect-magento-against-brute-force-attacks.md b/docs/best-practices/security/how-to-protect-magento-against-brute-force-attacks.md index 8ecefb2a..59133f42 100644 --- a/docs/best-practices/security/how-to-protect-magento-against-brute-force-attacks.md +++ b/docs/best-practices/security/how-to-protect-magento-against-brute-force-attacks.md @@ -165,8 +165,8 @@ Disclaimer: these configuration snippets are provided “as is” and we do not ### Amasty Improved Layered Navigation (Magento 1) -Do you have a Magento 1 shop and do you use the Amasty extension? You may be open to bruteforce attacks if you have a vulnerable version of the Improved Layered Navigation plugin installed. Try visiting the path `/amshopby/adminhtml_filter` (e.g. [www.example.com/amshopby/adminhtml_filter](http://www.example.com/amshopby/adminhtml_filter)) and check if you are redirected to your admin login page. If so, follow the instructions above to restrict access to this path. +Do you have a Magento 1 shop and do you use the Amasty extension? You may be open to bruteforce attacks if you have a vulnerable version of the Improved Layered Navigation plugin installed. Try visiting the path `/amshopby/adminhtml_filter` (e.g. `www.example.com/amshopby/adminhtml_filter`) and check if you are redirected to your admin login page. If so, follow the instructions above to restrict access to this path. ## Need help? -We do not provide Magento consultancy ourselves, however we partnered with professional agencies that will be able to help you. Don’t hesitate to [contact one of these agencies](https://www.magereport.com/page/support). +We do not provide Magento consultancy ourselves, however we partnered with professional agencies that will be able to help you. Don’t hesitate to [contact one of these agencies](https://www.hypernode.com/en/our-partners/). diff --git a/docs/best-practices/security/how-to-recover-a-hacked-magento-shop.md b/docs/best-practices/security/how-to-recover-a-hacked-magento-shop.md index 360711e6..8cdc513e 100644 --- a/docs/best-practices/security/how-to-recover-a-hacked-magento-shop.md +++ b/docs/best-practices/security/how-to-recover-a-hacked-magento-shop.md @@ -64,4 +64,4 @@ suspicious and/or recently modified files. And you could compare with a new Mage ## Need help? -Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, we advise you to contact an expert in recovering hacked Magento shops, such as [Sansec](https://www.sansec.io/), or find [a local technical partner](https://www.magereport.com/page/support) to assist you. +Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, we advise you to contact an expert in recovering hacked Magento shops, such as [Sansec](https://www.sansec.io/), or find [a local technical partner](https://www.hypernode.com/en/our-partners/) to assist you. diff --git a/docs/best-practices/security/how-to-secure-magento-cacheleak.md b/docs/best-practices/security/how-to-secure-magento-cacheleak.md index 817c3da8..a0e47fc4 100644 --- a/docs/best-practices/security/how-to-secure-magento-cacheleak.md +++ b/docs/best-practices/security/how-to-secure-magento-cacheleak.md @@ -302,4 +302,4 @@ http { ## Need Help? -Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to [contact one of these agencies](https://www.magereport.com/page/support). +Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to [contact one of these agencies](https://www.hypernode.com/en/our-partners/). diff --git a/docs/best-practices/security/how-to-use-a-cloud-firewall-on-hypernode.md b/docs/best-practices/security/how-to-use-a-cloud-firewall-on-hypernode.md index 6e92afbc..80201779 100644 --- a/docs/best-practices/security/how-to-use-a-cloud-firewall-on-hypernode.md +++ b/docs/best-practices/security/how-to-use-a-cloud-firewall-on-hypernode.md @@ -67,4 +67,4 @@ To ensure that the Cloud Firewall can always connect to your Hypernode, we advis For optimal security, it is recommended to configure traffic between the Cloud Firewall and your Hypernode to always be encrypted, through an SSL certificate. For most Cloud Firewall setups you can simply use a regular SSL certificate, as you would normally. -In some cases you may be provided with an Origin SSL certificate by your Cloud Firewall provider. In this case, simply upload a Custom Certificate either via the Service panel, or via the Control Panel. +In some cases you may be provided with an Origin SSL certificate by your Cloud Firewall provider. In this case, simply upload a Custom Certificate via the Control Panel. diff --git a/docs/best-practices/testing/how-to-go-live-with-your-hypernode.md b/docs/best-practices/testing/how-to-go-live-with-your-hypernode.md index 861741cd..04ddbf34 100644 --- a/docs/best-practices/testing/how-to-go-live-with-your-hypernode.md +++ b/docs/best-practices/testing/how-to-go-live-with-your-hypernode.md @@ -87,17 +87,17 @@ Read more about Hypernode Managed Vhosts in [this article](../../hypernode-platf See our manual on configuring DNS for more information. As the DNS changes are propagated, traffic will go to your Hypernode. -There are 3 ways to handle your DNS. Only customers who have access to the Service Panel (service.byte.nl) can choose option 1. +There are 3 ways to handle your DNS. Option 1 is available if your domain is registered with (or moved to) Hypernode. -1. Move your domain(s) to Hypernode and let Hypernode  manage the DNS (Dutch customers only). +1. Move your domain(s) to Hypernode and let Hypernode manage the DNS. 1. Manage an external DNS by pointing your domain(s) to Hypernode by using CNAME and not A record. 1. Manage an external DNS by pointing your domain(s) to the IP-address of Hypernode via A record. Good to know: - Option 1 and 2 will prevent DNS downtime. -- Option 2 has an important disadvantage: your cannot use SSL in combination with your naked domain. People that directly visit , will get a certificate warning from the browser. -- Option 3 is the best option in case of an external DNS and you want to make use of , but you will encounter DNS downtime if the IP address of your Hypernode changes. +- Option 2 has an important disadvantage: your cannot use SSL in combination with your naked domain. People that directly visit `https://yourdomain.com/`, will get a certificate warning from the browser. +- Option 3 is the best option in case of an external DNS and you want to make use of `https://yourdomain.com/`, but you will encounter DNS downtime if the IP address of your Hypernode changes. As there are situations you cannot benefit from a dedicated IP on Hypernode, please decide for yourself what is the best way to handle DNS. Our recommendation is always to move your domains to Hypernode if possible. diff --git a/docs/best-practices/testing/hypernode-docker.md b/docs/best-practices/testing/hypernode-docker.md index 9f918439..8672c856 100644 --- a/docs/best-practices/testing/hypernode-docker.md +++ b/docs/best-practices/testing/hypernode-docker.md @@ -15,7 +15,7 @@ The official Hypernode Docker image for Magento development is now available. Th ## About the Hypernode Docker Image -We build this image multiple times a day (every time we do a [release](https://changelog.hypernode.com/)) by applying our configuration management on the [phusion/baseimage-docker](https://github.com/phusion/baseimage-docker) ["fat" container](https://blog.phusion.nl/2015/01/20/baseimage-docker-fat-containers-treating-containers-vms/). By treating the Docker as a lightweight VM instead of as a vehicle for a single process we stay close to what an actual Hypernode actually looks like. No micro-services or a multi-container application, but a single instance with minimal network overhead and all batteries included. +We build this image multiple times a day (every time we do a [release](https://changelog.hypernode.com/)) by applying our configuration management on the [phusion/baseimage-docker](https://github.com/phusion/baseimage-docker) ["fat" container](https://web.archive.org/web/2020/https://blog.phusion.nl/2015/01/20/baseimage-docker-fat-containers-treating-containers-vms/). By treating the Docker as a lightweight VM instead of as a vehicle for a single process we stay close to what an actual Hypernode actually looks like. No micro-services or a multi-container application, but a single instance with minimal network overhead and all batteries included. The `hypernode-docker` image has SSH, PHP, NGINX, MySQL, Redis, Varnish and Elasticsearch. The biggest difference between a real Hypernode and this container is that this environment does not have an [init system](https://en.wikipedia.org/wiki/Init). While it is possible to [run systemd within a Docker Container](https://developers.redhat.com/blog/2014/05/05/running-systemd-within-docker-container/) if the host is also runs [systemd](https://www.freedesktop.org/wiki/Software/systemd/), we choose not to do so to achieve greater compatibility and user-friendliness. @@ -56,7 +56,7 @@ Now you're ready to use the hypernode-importer to import a shop from a remote se hypernode-importer --host yourhypernode.hypernode.io --path /data/web/public --set-default-url ``` -To see the container in your browser you should change the base-url to “[http://127.0.0.1:8080/”](http://127.0.0.1:8080/%E2%80%9D) and don’t forget to flush your cache afterwards: +To see the container in your browser you should change the base-url to “[http://127.0.0.1:8080/](http://127.0.0.1:8080/)” and don’t forget to flush your cache afterwards: #### Magento 1 @@ -284,7 +284,7 @@ app@e4b7d958e69c:~$ ls /etc/hypernode/is_docker 5. Import application -Run the [hypernode-importer](../../hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md#option-2-for-all-customers-migrate-your-shop-via-shell-using-the-hypernode-importer) to import a shop from a real Hypernode: +Run the [hypernode-importer](../../hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md#migrate-your-shop-via-shell-using-the-hypernode-importer) to import a shop from a real Hypernode: ```bash hypernode-importer --host yourhypernode.hypernode.io --path /data/web/public --set-default-url diff --git a/docs/best-practices/testing/zero-downtime-deployment-on-hypernode.md b/docs/best-practices/testing/zero-downtime-deployment-on-hypernode.md index 7a1ec654..434e4fa3 100644 --- a/docs/best-practices/testing/zero-downtime-deployment-on-hypernode.md +++ b/docs/best-practices/testing/zero-downtime-deployment-on-hypernode.md @@ -18,7 +18,7 @@ For e-commerce shops like Magento or Shopware, uptime is key. Customers may perc On Hypernode, zero downtime deployment is supported. As we host a large number of very different shops, we do not want to interfere with the deployment processes of our customers and partners. We offer our customers full flexibility with their deployment processes. -Zero downtime deployment can be a challenge, but investing time in the set-up may absolutely pay off. Developers around the world exchange ideas and best practices on how to deploy new code without downtime. Not sure where to start? We recommend reading [this article](https://www.hypernode.com/blog/time-saving/how-to-choose-the-best-method-to-deploy-code) on how to deploy code first. +Zero downtime deployment can be a challenge, but investing time in the set-up may absolutely pay off. Developers around the world exchange ideas and best practices on how to deploy new code without downtime. Not sure where to start? We recommend reading our [Hypernode Deploy documentation](../../hypernode-deploy/getting-started.md) on how to deploy code first. ## Magento 2 diff --git a/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md b/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md index cef66fdb..d7e72fd7 100644 --- a/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md +++ b/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md @@ -103,6 +103,6 @@ After installing and configuring Nginx, you can visit your WordPress at `/blog/` ## Multisite -It is possible to set up a multisite environment in WordPress. To do this, refer to the [original WordPress documentation about creating multisites](https://codex.wordpress.org/Create_A_Network) and the article [about configuring WordPress on Nginx](https://wordpress.org/support/article/nginx/). +It is possible to set up a multisite environment in WordPress. To do this, refer to the [original WordPress documentation about creating multisites](https://wordpress.org/documentation/article/create-a-network/) and the article [about configuring WordPress on Nginx](https://wordpress.org/support/article/nginx/). *Please note that it won’t work in all cases due to the fact that certain Nginx configurations cannot be changed. At the moment we are still looking into a solution that will work for everyone.* diff --git a/docs/best-practices/usage/hypernode-magerun.md b/docs/best-practices/usage/hypernode-magerun.md index 151e3b37..009a6171 100644 --- a/docs/best-practices/usage/hypernode-magerun.md +++ b/docs/best-practices/usage/hypernode-magerun.md @@ -120,7 +120,7 @@ Building a .deb for release: ./build.sh ``` -Then if everything is alright, upload the new version to your repository with something like [dput](https://manpages.ubuntu.com/manpages/plucky/en/man1/dput.1.html) +Then if everything is alright, upload the new version to your repository with something like [dput](https://manpages.ubuntu.com/manpages/noble/en/man1/dput.1.html) ## n98-magerun2 compatibility 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 6e497256..5610250a 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 @@ -67,19 +67,14 @@ When the Magento Connect Manager is not available, Turpentine needs to be instal After installing Turpentine and flushing the Magento cache, you can start configuring Turpentine: -- Log on to your [Byte Service Panel](http://auth.byte.nl) -- Select your Hypernode plan -- Click on the tab **Instellingen** -- Select the option `Varnish` -- You’ll notice Varnish cache is non-active. This is necessary for testing your shop with Varnish. (See `Test your shop with Varnish` below) -- Don’t close this page, you’ll need this information later +- Note the Varnish cache is non-active by default. This is necessary for testing your shop with Varnish. (See `Test your shop with Varnish` below) - Log on to your Magento backend - Navigate to System -> Configuration - Select **Varnish Options** under `Turpentine` - In the `Servers`section, fill in the following information: - *Varnish version*: leave this on `auto` - *Varnish server list*: varnish:6082 - - *Varnish authentication key*: Paste the content from your Service Panel here + - *Varnish authentication key*: Paste the Varnish secret shown in your Control Panel here - Select `Caching Options` under `Turpentine` - Check if the following information is correct: - *Backend host*: This should say `varnish` diff --git a/docs/ecommerce-applications/magento-1/how-to-reset-your-magento-1-x-admin-password.md b/docs/ecommerce-applications/magento-1/how-to-reset-your-magento-1-x-admin-password.md index ecfd7012..02f885f1 100644 --- a/docs/ecommerce-applications/magento-1/how-to-reset-your-magento-1-x-admin-password.md +++ b/docs/ecommerce-applications/magento-1/how-to-reset-your-magento-1-x-admin-password.md @@ -81,7 +81,7 @@ Additionally you can change the passwords for admin users directly in the databa First, log in to phpMyAdmin: -- Go to phpMyAdmin on the hypernode by visiting or by clicking the link in our service panel. +- Go to phpMyAdmin on the hypernode by visiting `http://appname.hypernode.io/phpmyadmin` or by enabling it via the Control Panel. - Login with the username and password in `~/.my.cnf` - Select the prod database on the left side panel. - In the top bar, select the `SQL` tab. diff --git a/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md b/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md index cafd1375..3a6feff3 100644 --- a/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md +++ b/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md @@ -116,7 +116,7 @@ You can update symlinks using the `ln` tool with the `-f` (force) feature flag: ln -sf /data/web/staging/some_file /data/web/staging/some_other_file ``` -That's all! Now you should be able to reach your staging environment on +That's all! Now you should be able to reach your staging environment on `http://mynode.hypernode.io:8888` ### How to Limit Access to a Staging Environment diff --git a/docs/ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x.md b/docs/ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x.md index 2489cb62..d1e686e7 100644 --- a/docs/ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x.md +++ b/docs/ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x.md @@ -14,7 +14,7 @@ This feature allows you to store files in a remote storage location, such as an This can be useful for many reasons, such as: - Offloading storage from your server, reducing the load on your server, and improving performance. -- Allows you to make use of [horizontal scaling](../../hypernode-platform/autoscaling/how-does-horizontal-autoscaling-work), as you can easily add more servers without having to worry about syncing files between them. +- Allows you to make use of [horizontal scaling](../../hypernode-platform/autoscaling/how-does-horizontal-autoscaling-work.md), as you can easily add more servers without having to worry about syncing files between them. - Allows for effortless storage capacity scaling, as you can easily increase the storage capacity of your remote storage location. - Serving assets from a CDN, which can improve the performance of your website. diff --git a/docs/ecommerce-applications/magento-2/how-to-set-up-a-basic-staging-environment-for-magento-2.md b/docs/ecommerce-applications/magento-2/how-to-set-up-a-basic-staging-environment-for-magento-2.md index 8e41cd75..1c983556 100644 --- a/docs/ecommerce-applications/magento-2/how-to-set-up-a-basic-staging-environment-for-magento-2.md +++ b/docs/ecommerce-applications/magento-2/how-to-set-up-a-basic-staging-environment-for-magento-2.md @@ -114,7 +114,7 @@ python change_magento2_staging_baseurls.py #### Change the Base URLS' for All Your Storefronts Via MySQL -Another easy way to change the base URLs of all your stores is by running the [following database queries:](https://gist.github.com/experius-nl/8e5cfd21bbb407dfdaa79021ee1f3da1) +Another easy way to change the base URLs of all your stores is by running a series of database queries. See our article on [how to change your Magento 2 base URLs](how-to-change-your-magento-2-base-urls.md) for the queries and instructions. A big thank you to our partner [Experius](https://www.experius.nl/) for providing these. diff --git a/docs/ecommerce-applications/magento-2/how-to-update-magento-2.md b/docs/ecommerce-applications/magento-2/how-to-update-magento-2.md index bcea9289..2e6a3d38 100644 --- a/docs/ecommerce-applications/magento-2/how-to-update-magento-2.md +++ b/docs/ecommerce-applications/magento-2/how-to-update-magento-2.md @@ -81,4 +81,4 @@ bin/magento --version ## Need Help? -Magento is no easy open-source CMS. Although we’re skilled in hosting Magento shops, making them fast, and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to many agencies that [contact one of these agencies](https://www.magereport.com/page/support). +Magento is no easy open-source CMS. Although we’re skilled in hosting Magento shops, making them fast, and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to many agencies that [contact one of these agencies](https://www.hypernode.com/en/our-partners/). diff --git a/docs/ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md b/docs/ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md index 0f7da801..adeb69ed 100644 --- a/docs/ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md +++ b/docs/ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md @@ -25,7 +25,7 @@ Varnish can be enabled with a simple command using the [hypernode-systemctl CLI] ## Step Two: Enable Varnish for NGINX Vhost -The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts) (HMV) config allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts: +The [hypernode-manage-vhosts](../../hypernode-platform/nginx/hypernode-managed-vhosts.md) (HMV) config allows you to enable varnish for every vhost individually. So if you for example have a domain example.com. You should create 2 vhosts: - example.com - [www.example.com](http://www.example.com) diff --git a/docs/ecommerce-applications/shopware-5/how-to-install-shopware-5-on-hypernode-docker.md b/docs/ecommerce-applications/shopware-5/how-to-install-shopware-5-on-hypernode-docker.md index 12e5ddbb..8238a8f1 100644 --- a/docs/ecommerce-applications/shopware-5/how-to-install-shopware-5-on-hypernode-docker.md +++ b/docs/ecommerce-applications/shopware-5/how-to-install-shopware-5-on-hypernode-docker.md @@ -60,7 +60,7 @@ Download the latest Shopware version (version 5 in this example) to your Docker ## Step Five - Install Shopware via Your Browser -- Open your browser and browse to: “[http://127.0.0.1:8080/recovery/install”](http://127.0.0.1:8080/recovery/install/index.php%E2%80%9D) +- Open your browser and browse to: “[http://127.0.0.1:8080/recovery/install](http://127.0.0.1:8080/recovery/install)” - Click "Next" - Agree to the terms of service. - Make sure to configure your database correctly: diff --git a/docs/ecommerce-applications/shopware-6/how-to-configure-remote-storage-for-shopware-6-x.md b/docs/ecommerce-applications/shopware-6/how-to-configure-remote-storage-for-shopware-6-x.md index 825cdd97..f0c47f19 100644 --- a/docs/ecommerce-applications/shopware-6/how-to-configure-remote-storage-for-shopware-6-x.md +++ b/docs/ecommerce-applications/shopware-6/how-to-configure-remote-storage-for-shopware-6-x.md @@ -13,7 +13,7 @@ Shopware 6.x supports remote storage for different types of files, allowing you Using remote object storage in Shopware 6 provides several benefits, including: - Offloading storage from your server, reducing the load on your server, and improving performance. -- Allows you to make use of [horizontal scaling](../../hypernode-platform/autoscaling/how-does-horizontal-autoscaling-work), as you can easily add more servers without having to worry about syncing files between them. +- Allows you to make use of [horizontal scaling](../../hypernode-platform/autoscaling/how-does-horizontal-autoscaling-work.md), as you can easily add more servers without having to worry about syncing files between them. - Allows for effortless storage capacity scaling, as you can easily increase the storage capacity of your remote storage location. - Serving assets from a CDN, which can improve the performance of your website. diff --git a/docs/ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode-docker.md b/docs/ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode-docker.md index 086bc875..3ad9f0a4 100644 --- a/docs/ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode-docker.md +++ b/docs/ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode-docker.md @@ -75,7 +75,7 @@ ln -s /data/web/shopware/public/ /data/web/public ## Install Shopware 6 -Now open your browser and browse to [http://127.0.0.1:8080/recovery/install](http://127.0.0.1:8080/recovery/install/index.php%22%3Ehttp://127.0.0.1:8080/recovery/install/index.php%3C/a). At this point you can follow the install-guide through your browser. Make sure to fill in the right details at **Configure database:** +Now open your browser and browse to [http://127.0.0.1:8080/recovery/install](http://127.0.0.1:8080/recovery/install). At this point you can follow the install-guide through your browser. Make sure to fill in the right details at **Configure database:** - Database server: localhost - Database user: app @@ -87,4 +87,4 @@ Now open your browser and browse to [http://127.0.0.1:8080/recovery/install](htt **Demo data** -If you’d like you could install demo data as well. To do this you’ll need to login the backend: with the credentials you entered during the step: Basic shop set-up at the installation. At your first login you’ll see the “First Run Wizard”, make sure to install the Demo data at the “Demo data” menu. +If you’d like you could install demo data as well. To do this you’ll need to login the backend: `http://APPNAME.hypernode.io/admin/` with the credentials you entered during the step: Basic shop set-up at the installation. At your first login you’ll see the “First Run Wizard”, make sure to install the Demo data at the “Demo data” menu. diff --git a/docs/ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode.md b/docs/ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode.md index 5f284052..ce6eeff9 100644 --- a/docs/ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode.md +++ b/docs/ecommerce-applications/shopware-6/how-to-install-shopware-6-on-hypernode.md @@ -69,7 +69,7 @@ ln -s /data/web/shopware/public/ /data/web/public ## Install Shopware 6 -Now open your browser and browse to [https://APPNAME.hypernode.io/recovery/update/index.php](https://APPNAME.hypernode.io/recovery/install/index.php). At this point you can follow the guide through your browser. Make sure to fill in the right details at the **Configure database**: +Now open your browser and browse to `https://APPNAME.hypernode.io/recovery/update/index.php`. At this point you can follow the guide through your browser. Make sure to fill in the right details at the **Configure database**: - Database server: localhost - Database user: app @@ -81,4 +81,4 @@ Now open your browser and browse to [https://APPNAME.hypernode.io/recovery/updat **Done!** You’ve now successfully installed Shopware 6. **Demo data** -If you’d like you could install demo data as well. To do this you’ll need to login the backend: [http://APPNAME.hypernode.io/admin/](http://APPNAME.hypernode.io/backend/) with the credentials you entered during the step: Basic shop set-up at the installation. At your first login you’ll see the “First Run Wizard”, make sure to install the Demo data at the “Demo data” menu. +If you’d like you could install demo data as well. To do this you’ll need to login the backend: `http://APPNAME.hypernode.io/admin/` with the credentials you entered during the step: Basic shop set-up at the installation. At your first login you’ll see the “First Run Wizard”, make sure to install the Demo data at the “Demo data” menu. diff --git a/docs/ecommerce-applications/shopware-6/how-to-use-a-basic-staging-environment-with-shopware-6.md b/docs/ecommerce-applications/shopware-6/how-to-use-a-basic-staging-environment-with-shopware-6.md index 042cc9a1..8924c5e5 100644 --- a/docs/ecommerce-applications/shopware-6/how-to-use-a-basic-staging-environment-with-shopware-6.md +++ b/docs/ecommerce-applications/shopware-6/how-to-use-a-basic-staging-environment-with-shopware-6.md @@ -76,7 +76,7 @@ mysqldump $databasename | mysql staging editor /data/web/shopware_staging/.env ``` -Make sure you edit the value of APP_URL to your Hypernode-URL: APP_URL="" +Make sure you edit the value of APP_URL to your Hypernode-URL: APP_URL="http://APPNAME.hypernode.io:8888/" ### Step Eight: Change the URL in the `sales_channel_domain` Table for Your Staging Database diff --git a/docs/ecommerce-applications/woocommerce/how-to-install-woocommerce-on-hypernode.md b/docs/ecommerce-applications/woocommerce/how-to-install-woocommerce-on-hypernode.md index 849a8351..d16a53f8 100644 --- a/docs/ecommerce-applications/woocommerce/how-to-install-woocommerce-on-hypernode.md +++ b/docs/ecommerce-applications/woocommerce/how-to-install-woocommerce-on-hypernode.md @@ -80,7 +80,7 @@ $ wp core config --dbhost='localhost' --dbuser='app' --dbpass='your_mysql_passwo $ wp core install --admin_user='mynode_admin' --admin_password='insecure_wp_password' --admin_email='owner@example.com' --url='https://mynode.hypernode.io' --title='My WooCommerce Shop' ``` -At this point, you should be able to access your application at '', but you'll note that it's just a WordPress site. To change that into a WooCommerce site, run the following commands: +At this point, you should be able to access your application at `https://mynode.hypernode.io`, but you'll note that it's just a WordPress site. To change that into a WooCommerce site, run the following commands: ```console $ # Optional: before installing the WooCommerce plugin, we set the email from address so we can make sure that our mails arrive. diff --git a/docs/getting-started/how-to-order/how-to-get-started-with-your-hypernode-trial.md b/docs/getting-started/how-to-order/how-to-get-started-with-your-hypernode-trial.md index cd39b6ae..53e1d7d0 100644 --- a/docs/getting-started/how-to-order/how-to-get-started-with-your-hypernode-trial.md +++ b/docs/getting-started/how-to-order/how-to-get-started-with-your-hypernode-trial.md @@ -54,13 +54,13 @@ You are in control and can change some Hypernode settings yourself via [the Hype We have developed an awesome time saving tool, the Hypernode Importer tool. With 1 simple command you import a copy of an existing shop onto your Hypernode. This will not have a negative impact on your live shop. -Instructions can be found in the [Hypernode support documentation](../../hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md#option-2-for-all-customers-migrate-your-shop-via-shell-using-the-hypernode-importer). +Instructions can be found in the [Hypernode support documentation](../../hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md#migrate-your-shop-via-shell-using-the-hypernode-importer). ### Step 3b – Install a new application on your Hypernode In our support documentation you will find detailed information about installing the different applications on a Hypernode: -- [Akeneo 3](../../ecommerce-applications/akeneo/how-to-install-akeneo-3-on-hypernode) +- [Akeneo 3](../../ecommerce-applications/akeneo/how-to-install-akeneo-3-on-hypernode.md) - [Akeneo 4](../../ecommerce-applications/akeneo/how-to-install-akeneo-4-on-hypernode.md) - [Akeneo 5](../../ecommerce-applications/akeneo/how-to-install-akeneo-5-on-hypernode.md) - [Akeneo 6](../../ecommerce-applications/akeneo/how-to-install-akeneo-6-on-hypernode.md) @@ -91,12 +91,12 @@ Please note: when you have an SSL certificate and use the secure base URL you sh ### Step 6 – Configure DNS -There are 2 ways to handle your DNS. Only customers who have access to the Service Panel can choose option 2. +There are 2 ways to handle your DNS. You can choose option 2 if your domain is registered with (or moved to) Hypernode. 1. Point the DNS of your externally hosted domain to the Hypernode by adding two records: 1. An A-record to the direct IP of your Hypernode for your apex or naked domain. 1. A CNAME-record to example.hypernode.io for your www-domain, with example replaced by your appname of course. -1. Move your domain(s) to Hypernode and let us manage the DNS (Service Panel users only). +1. Move your domain(s) to Hypernode and let us manage the DNS. ### Step 7 – Configure Nginx diff --git a/docs/hypernode-deploy/applications/config-for-magento-1.md b/docs/hypernode-deploy/applications/config-for-magento-1.md index 88f097ab..3fd389b4 100644 --- a/docs/hypernode-deploy/applications/config-for-magento-1.md +++ b/docs/hypernode-deploy/applications/config-for-magento-1.md @@ -1 +1,30 @@ +--- +myst: + html_meta: + description: Example Hypernode Deploy deploy.php configuration for a Magento 1 + shop, using the Magento 1 application template. + title: Hypernode Deploy Config for Magento 1 | Hypernode +--- + # Config for Magento 1 + +This is a sample configuration that suffices for most Magento 1 installations: + +```php +addStage('production', 'magento1.komkommer.store'); +$productionStage->addServer('appname.hypernode.io'); + +return $configuration; +``` + +By using the Magento1 ApplicationTemplate, a bunch of default configuration gets set in Hypernode Deploy, and should work out-of-the-box for most Magento 1 shops. + +```{warning} +Magento 1 reached its end of life in June 2020 and no longer receives official security patches. If you still run Magento 1, we advise you to plan a migration to Magento 2 or another supported platform. +``` diff --git a/docs/hypernode-deploy/applications/config-for-magento-2.md b/docs/hypernode-deploy/applications/config-for-magento-2.md index 367a43ff..e8442838 100644 --- a/docs/hypernode-deploy/applications/config-for-magento-2.md +++ b/docs/hypernode-deploy/applications/config-for-magento-2.md @@ -1,6 +1,14 @@ +--- +myst: + html_meta: + description: Example Hypernode Deploy deploy.php configuration for Magento 2, including + themes, static content locales, shared files and custom build steps. + title: Hypernode Deploy Config for Magento 2 | Hypernode +--- + # Config for Magento 2 -This is a sample configuration that suffices for most magento2 installations: +This is a sample configuration that suffices for most Magento 2 installations: ```php addServer('appname.hypernode.io'); return $configuration; ``` -By using the Magento2 ApplicationTemplate, a bunch of default configuration gets set in Hypernode Deploy, and should work out-of-the-box for most magento 2 stores. +By using the Magento2 ApplicationTemplate, a bunch of default configuration gets set in Hypernode Deploy, and should work out-of-the-box for most Magento 2 shops. ## Common issues @@ -125,9 +133,12 @@ For more information, see the [Hypernode Deploy v4.8.0 changelog](https://change ### Defining custom steps -You potentially need to add custom steps to the deployment, for example to build npm assets or do server actions after deployment. +You potentially need to add custom steps to the deployment, for example to build npm assets or do server actions after deployment. Import the Deployer functions you use at the top of your `deploy.php`, otherwise PHP cannot resolve them inside the `Hypernode\DeployConfiguration` namespace: ```php +use function Deployer\run; +use function Deployer\task; + task('node:install', static function () { run("npm ci"); }); diff --git a/docs/hypernode-deploy/applications/config-for-nextjs.md b/docs/hypernode-deploy/applications/config-for-nextjs.md index dbc27ae8..f88a9616 100644 --- a/docs/hypernode-deploy/applications/config-for-nextjs.md +++ b/docs/hypernode-deploy/applications/config-for-nextjs.md @@ -1,3 +1,11 @@ +--- +myst: + html_meta: + description: Example Hypernode Deploy deploy.php configuration for a NextJS application + on Hypernode, including PM2, Nginx proxy and Hypernode settings. + title: Hypernode Deploy Config for NextJS | Hypernode +--- + # Config for NextJS Configuration to use as Hypernode Deploy deploy.php for a NextJS webserver application: diff --git a/docs/hypernode-deploy/applications/config-for-shopware-6.md b/docs/hypernode-deploy/applications/config-for-shopware-6.md index bc9c1ae5..d067050d 100644 --- a/docs/hypernode-deploy/applications/config-for-shopware-6.md +++ b/docs/hypernode-deploy/applications/config-for-shopware-6.md @@ -1,3 +1,11 @@ +--- +myst: + html_meta: + description: Example Hypernode Deploy deploy.php configuration for a Shopware 6 + shop, using the Shopware 6 application template. + title: Hypernode Deploy Config for Shopware 6 | Hypernode +--- + # Config for Shopware 6 This is a sample configuration that suffices for most Shopware 6 installations: diff --git a/docs/hypernode-deploy/pipelines.md b/docs/hypernode-deploy/pipelines.md index b82d0d53..7b141888 100644 --- a/docs/hypernode-deploy/pipelines.md +++ b/docs/hypernode-deploy/pipelines.md @@ -1,5 +1,17 @@ +--- +myst: + html_meta: + description: Set up a Hypernode Deploy CI/CD pipeline with Github Actions, Gitlab + CI or Bitbucket Pipelines, including build and deploy jobs per stage. + title: Hypernode Deploy CI/CD Pipelines | Hypernode +--- + # CI/CD Pipelines +Hypernode Deploy runs in your CI/CD pipeline: one job builds the artifact, another deploys it to the stage that matches the branch you pushed to. The articles in this chapter contain a complete pipeline configuration per CI/CD system, which you can copy into your repository and adjust. + +All three assume you already have a `deploy.php`. If you do not, start with [Install and configure Hypernode Deploy](getting-started/install-and-configure-hypernode-deploy.md). + ```{toctree} --- caption: Chapters diff --git a/docs/hypernode-deploy/pipelines/bitbucket-pipelines.md b/docs/hypernode-deploy/pipelines/bitbucket-pipelines.md index 10987bb1..605d9bd8 100644 --- a/docs/hypernode-deploy/pipelines/bitbucket-pipelines.md +++ b/docs/hypernode-deploy/pipelines/bitbucket-pipelines.md @@ -1,3 +1,11 @@ +--- +myst: + html_meta: + description: Complete Bitbucket Pipelines example to build and deploy your application + to Hypernode with Hypernode Deploy. + title: Hypernode Deploy With Bitbucket Pipelines | Hypernode +--- + # Bitbucket Pipelines ```{note} @@ -65,14 +73,14 @@ This workflow will be used in other workflows. # Here we use the latest Hypernode Deploy image with PHP 8.4 and Node.js 22 image: quay.io/hypernode/deploy:latest-php8.4-node22 -definition: +definitions: steps: - step: &hypernode-build name: Build - script: - - hypernode-deploy build - artifacts: - - build/** + script: + - hypernode-deploy build + artifacts: + - build/** ``` ````{note} @@ -109,10 +117,10 @@ pipelines: acceptance: # acceptance/staging branch - step: *hypernode-build - step: - name: Deploy to staging + name: Deploy to acceptance deployment: staging script: - - hypernode-deploy deploy staging + - hypernode-deploy deploy acceptance # Deploy acceptance stage defined in deploy.php ``` ## Next steps diff --git a/docs/hypernode-deploy/pipelines/github-actions.md b/docs/hypernode-deploy/pipelines/github-actions.md index c62d7bb5..5da0dbbe 100644 --- a/docs/hypernode-deploy/pipelines/github-actions.md +++ b/docs/hypernode-deploy/pipelines/github-actions.md @@ -1,3 +1,11 @@ +--- +myst: + html_meta: + description: Complete Github Actions workflow example to build and deploy your + application to Hypernode with Hypernode Deploy. + title: Hypernode Deploy With Github Actions | Hypernode +--- + # GitHub Actions ```{note} diff --git a/docs/hypernode-deploy/pipelines/gitlab-ci.md b/docs/hypernode-deploy/pipelines/gitlab-ci.md index ac247dff..a8761cb2 100644 --- a/docs/hypernode-deploy/pipelines/gitlab-ci.md +++ b/docs/hypernode-deploy/pipelines/gitlab-ci.md @@ -1,3 +1,11 @@ +--- +myst: + html_meta: + description: Complete Gitlab CI pipeline example to build and deploy your application + to Hypernode with Hypernode Deploy. + title: Hypernode Deploy With Gitlab CI | Hypernode +--- + # Gitlab CI ```{note} diff --git a/docs/hypernode-platform/autoscaling/how-does-horizontal-autoscaling-work.md b/docs/hypernode-platform/autoscaling/how-does-horizontal-autoscaling-work.md index b10ce8c5..6a6f9ca8 100644 --- a/docs/hypernode-platform/autoscaling/how-does-horizontal-autoscaling-work.md +++ b/docs/hypernode-platform/autoscaling/how-does-horizontal-autoscaling-work.md @@ -222,7 +222,7 @@ bin/magento setup:config:set \ Remote storage is a requirement for Horizontal autoscaling. This is because the media files should be stored on a remote storage location instead of the local filesystem. This way the media files are available across multiple Hypernodes when the app is scaled up, and after scaling down the media files are still available. -Follow our documentation on [remote storage for Magento 2](../../ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x) to configure remote storage. +Follow our documentation on [remote storage for Magento 2](../../ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x.md) to configure remote storage. ## Enabling Horizontal Autoscaling @@ -230,4 +230,4 @@ For detailed steps on enabling horizontal Autoscaling, please refer to our docum ## Horizontal Autoscaling Pricing -To know more about the pricing, you can visit our documentation: [Horizontal Autoscaling Pricing](pricing-for-horizontal-autoscaling). +To know more about the pricing, you can visit our documentation: [Horizontal Autoscaling Pricing](pricing-for-horizontal-autoscaling.md). diff --git a/docs/hypernode-platform/dns/dns-for-control-panel-users.md b/docs/hypernode-platform/dns/dns-for-control-panel-users.md index 098f1e1b..102d9f55 100644 --- a/docs/hypernode-platform/dns/dns-for-control-panel-users.md +++ b/docs/hypernode-platform/dns/dns-for-control-panel-users.md @@ -1,8 +1,8 @@ --- myst: html_meta: - description: You can edit the DNS setting for your domain names in the Control - Panel(Instellingen => DNS). It takes 24 hours for a DNS change to be implemented. + description: You can edit the DNS settings for your domain names in the Control + Panel. It takes 24 hours for a DNS change to be implemented. title: How to manage your DNS as a Control Panel user? redirect_from: - /en/support/solutions/articles/48001153093-dns-for-service-panel-users/ @@ -12,7 +12,7 @@ redirect_from: 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). +You can edit the DNS settings for your domain names in the Control Panel under **Domains** > your domain > **DNS manager**. It takes 24 hours for a DNS change to be implemented everywhere. Take this into account. @@ -24,7 +24,7 @@ Please note that Hypernode cannot provide uptime guarantees for external DNS, so If your domain name is registered with an external provider, please be aware that Hypernode has no control over the availability or functioning of that provider’s DNS services. -If you prefer not to transfer your domain name to Hypernode, a good alternative is to update your domain’s nameservers to the Hypernode nameservers. To manage your DNS through the Service Panel, you will need a Presence plan. +If you prefer not to transfer your domain name to Hypernode, a good alternative is to update your domain’s nameservers to the Hypernode nameservers. To manage your DNS through the Control Panel, you will need a DNS only plan. Once your DNS has been configured correctly, you can ask your domain provider to update the nameservers to the Hypernode nameservers: @@ -98,7 +98,7 @@ Different DNS records have been created for the different types of internet traf ### 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: +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 Hypernode'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 Hypernode name servers are: ns1.hypernode.com @@ -106,13 +106,13 @@ ns2.hypernode.com ns3.hypernode.com -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). +If you have set up other name servers, the DNS data will be downloaded from that server. Hypernode always recommends using the Hypernode 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 Control 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. +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.example.nl) neither. Www.example.com is seen as a subdomain by DNS. ### AAAA Records diff --git a/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md b/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md index 8fe98d34..416e4b93 100644 --- a/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md +++ b/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md @@ -31,7 +31,7 @@ If you're likely to switch between Falcon and Eagle plans in the future, we reco ## Three ways to handle your DNS -There are three ways to handle your DNS. Only customers who have access to a Service Panel can choose option 1. +There are three ways to handle your DNS. Option 1 is available if your domain is registered with (or moved to) Hypernode. 1. Move your domain(s) to Hypernode and let Hypernode manage the DNS 1. Manage an external DNS by pointing your domain(s) to Hypernode by using CNAME and not A record @@ -145,7 +145,7 @@ You can read how this works [in this article](../nginx/how-to-redirect-from-or-t ## Shop on a subdomain? -If you host your shop on a subdomain (for example, shop.example.com), and you don’t want to be available on [www.shop.example.com](http://www.shop.example.com), you can forget all about the wwwizer service, and there’s no need to add the two IP addresses in your A records as explained above. Simply create a CNAME-record pointing to your Hypernode, and it will work: +If you host your shop on a subdomain (for example, shop.example.com), and you don’t want to be available on `www.shop.example.com`, you can forget all about the wwwizer service, and there’s no need to add the two IP addresses in your A records as explained above. Simply create a CNAME-record pointing to your Hypernode, and it will work: ``` shop.example.com CNAME example.hypernode.io diff --git a/docs/hypernode-platform/dns/how-to-set-up-your-spf-records-for-hypernode.md b/docs/hypernode-platform/dns/how-to-set-up-your-spf-records-for-hypernode.md index d1e9fd53..dab105e1 100644 --- a/docs/hypernode-platform/dns/how-to-set-up-your-spf-records-for-hypernode.md +++ b/docs/hypernode-platform/dns/how-to-set-up-your-spf-records-for-hypernode.md @@ -133,7 +133,7 @@ The From header is part of the message body and is only used for display purpose There are web based tools available that can help you generate an SPF record. As there are always corner cases which the generator does not take into account, blindly generating an SPF record with one of these tools and copy paste it in your DNS zone is never a good idea. If you know what you are doing however, this generators can be of great assistance. -The best generators we’ve found so far are the one on [spfwizard.net](https://www.spfwizard.net), and the one on [unlock the inbox.](https://www.unlocktheinbox.com/spfwizard/) Both tools are free of use for anyone. +The best generator we’ve found so far is the one on [unlock the inbox.](https://www.unlocktheinbox.com/spfwizard/) This tool is free of use for anyone. ### Finding your current SPF record @@ -158,7 +158,6 @@ We list a few that can help you solving SPF problems: - [Kittermans SPF validation](https://www.kitterman.com/spf/validate.html) – This is the first SPF checker ever, and still well known for it’s completeness - [The SPF Check @ MX Toolbox](https://mxtoolbox.com/spf.aspx)– This is the most complete online email utility -- [Mailcleaner Batch SPF Tester](https://www.mailcleaner.net/tools/test_spf.html) – Very useful to verify if all your domains are setup correctly. ## Differences compared to DKIM diff --git a/docs/hypernode-platform/dns/your-dns-is-misconfigured.md b/docs/hypernode-platform/dns/your-dns-is-misconfigured.md index 74402c1d..e3f43422 100644 --- a/docs/hypernode-platform/dns/your-dns-is-misconfigured.md +++ b/docs/hypernode-platform/dns/your-dns-is-misconfigured.md @@ -13,6 +13,6 @@ redirect_from: # Your DNS is misconfigured -You’ve reached this page because the DNS for this domain has been misconfigured. The administrator of this domain has pointed [www.domain.com](http://www.domain.com) to our DNS service, instead of appointing a CNAME to his/her Hypernode. +You’ve reached this page because the DNS for this domain has been misconfigured. The administrator of this domain has pointed `www.domain.com` to our DNS service, instead of appointing a CNAME to his/her Hypernode. If you are the administrator of this domain, please refer to the documentation on how [to configure DNS for Hypernode correctly](how-to-manage-your-dns-settings-for-hypernode.md). diff --git a/docs/hypernode-platform/email/how-to-activate-a-virus-filter-for-your-email-box.md b/docs/hypernode-platform/email/how-to-activate-a-virus-filter-for-your-email-box.md index c49a7a53..2a515cdb 100644 --- a/docs/hypernode-platform/email/how-to-activate-a-virus-filter-for-your-email-box.md +++ b/docs/hypernode-platform/email/how-to-activate-a-virus-filter-for-your-email-box.md @@ -24,15 +24,7 @@ When a virus is detected, it is possible that only the infected attachment is de ## Disable Virus Filter -We do not recommend deactivating the virus filter, but if you want to do this, you can do so via the Service Panel: - -- Log in to the [Service Panel](https://service.byte.nl/protected/overzicht/). -- Select your domain name. -- Click the 'Instellingen' tab. -- Click on the 'Email' option. -- Click on the 'virus- en spamfilterinstellingen' icon -- Deselect the box after Virus Filter. -- Click Save. +We do not recommend deactivating the virus filter, but if you want to do this, please contact [support@hypernode.com](mailto:support@hypernode.com). The virus filter cannot be disabled from the Control Panel. ## Blocked Files diff --git a/docs/hypernode-platform/email/how-to-configure-the-spam-filter.md b/docs/hypernode-platform/email/how-to-configure-the-spam-filter.md index a0c66392..bad8e4bf 100644 --- a/docs/hypernode-platform/email/how-to-configure-the-spam-filter.md +++ b/docs/hypernode-platform/email/how-to-configure-the-spam-filter.md @@ -13,8 +13,6 @@ redirect_from: # How to Configure the Spam Filter -**Please note that this only applies to Service Panel users who log in via service.byte.nl.** - Spam is unsolicited email, usually with a commercial content. If you receive a lot of spam in your email box, we recommend you to configure a spam filter. ## How Does the Spam Filter Work @@ -43,14 +41,8 @@ The diagram below shows an approximation of what happens when you set up the spa ## Configuring the Spam Filter -If you use Hypernode's mail servers, you can set the spam filter yourself on the Service Panel using this step-by-step plan: +If you use Hypernode's mail servers, you can configure the spam filter per mailbox. These settings are not available in the Control Panel; please contact [support@hypernode.com](mailto:support@hypernode.com) to change them for you. When contacting us, we advise you to set the following: -1. Log into the Service Panel. -1. Select the desired domain. -1. Go to the tab *Instellingen*\*.\*\*\* -1. Select *E-mail*. -1. Click the virus- and spam settings icon located next to each mailbox (you can have different settings for each mail box). -1. On the virus and spam filter settings page you can use the dropdown menu to configure the spam settings. We advice you to set the following: 1. \*\*Marking spam: High.\*\*For example, most of the spam (about 98%) is marked in the subject line and you can have it set aside by your email program 1. **Blocking spam: Low**. Only obvious spam is blocked and the chance that you will lose a legit email is negligible. @@ -64,7 +56,7 @@ Our spam filter contains many hundreds of tests that are performed to determine - The text of the mail is searched. If words such as Viagra and Get Rich Quick appear, there will be penalty points. If it contains URLs of well-known spam sites, there will be penalty points. Above a certain number of penalty points, the mail will be rejected. - Via a statistical method (so-called Bayesian Spam Filtering) the mail gets a spam score. Above a certain score, the mail will be rejected. -These are only a few examples. Please see [this website](http://www.spamassassin.org/) for more information. We also use [this Sender Verification](http://www.postfix.org/). We also use this blacklist. +These are only a few examples. Please see [this website](https://spamassassin.apache.org/) for more information. We also use [this Sender Verification](https://www.postfix.org/). We also use this blacklist. ## Frequently Asked Questions @@ -101,4 +93,4 @@ Use the filters of your mail program to filter out this header. **Can I disable the spam filter completely?** -You can disable the spam filter via the Service Panel. Your email will still be checked for Sender Address Verification and with a blacklist (only Spamhaus at the moment). +You can have the spam filter disabled by [support@hypernode.com](mailto:support@hypernode.com). Your email will still be checked for Sender Address Verification and with a blacklist (only Spamhaus at the moment). diff --git a/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md b/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md index e165804e..6422e7ba 100644 --- a/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md +++ b/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md @@ -17,14 +17,13 @@ When you want to use Office365 and your domain is registered with Hypernode or h ## Validation Record -When you add your domain to Office365 they wil provide you with a verification string that you need to add to the DNS for your domain, the string will look something like this \*MS=ms#########.\*You need to add this at a TXT record. To do so login to your [Service Panel](https://my.hypernode.com/) and follow the next steps: +When you add your domain to Office365 they wil provide you with a verification string that you need to add to the DNS for your domain, the string will look something like this \*MS=ms#########.\*You need to add this at a TXT record. To do so open the DNS manager in your [Control Panel](https://my.hypernode.com/) and follow the next steps: -1. Log in to the Service Panel (my.hypernode.com). -1. Select the domain from the domain overview. -1. Click the tab **Instellingen**. -1. Then select **DNS**. -1. Click **Voeg Record Toe** -1. Switch the record type to TXT and for the content add the string Office365 generated for you. Then click **Save Record** +1. Log in to the [Control Panel](https://my.hypernode.com/). +1. Select **Domains** in the sidebar and open the domain you want to configure. +1. Click **DNS manager**. +1. Click **Add new record**. +1. Switch the record type to TXT and for the content add the string Office365 generated for you. Then save the record. ## DNS Records for Office365 @@ -46,6 +45,6 @@ When you want to keep using the Hypernode name servers while using Office365 you You don't need to add a new SPF record if you already have one (for example for your Hypernode) you can just edit the current one (with the pencil icon) and add the Outlook value to the current record -Please note that if you had created email boxes and email addresses at Hypernode, you must delete them. You can do this under **Instellingen > Email**in the Service Panel. Make sure to [export the emails](../../best-practices/email/how-to-export-your-emails.md) in the inbox if you want to save them to your new Office365 account before deleting the accounts at Hypernode. +Please note that if you had created email boxes and email addresses at Hypernode, you must delete them. Please contact [support@hypernode.com](mailto:support@hypernode.com) to remove them. Make sure to [export the emails](../../best-practices/email/how-to-export-your-emails.md) in the inbox if you want to save them to your new Office365 account before deleting the accounts at Hypernode. Do you have any questions about how Office 365 works? Then it is best to visit the [Office 365 Community](https://techcommunity.microsoft.com/t5/office-365/bd-p/Office365General). diff --git a/docs/hypernode-platform/email/how-to-use-dmarc.md b/docs/hypernode-platform/email/how-to-use-dmarc.md index 86f7871a..80c4e099 100644 --- a/docs/hypernode-platform/email/how-to-use-dmarc.md +++ b/docs/hypernode-platform/email/how-to-use-dmarc.md @@ -12,8 +12,6 @@ redirect_from: # How to Use DMARC -**Please note that this only applies to Service Panel users who log in via service.byte.nl. This functionality isn't available in the Control Panel yet.** - Hypernode offers DMARC (Domain-based Message Authentication, Reporting and Conformance). With SPF and DKIM you indicate which mail is real and which is fake. With DMARC you then indicate what the recipient of the mail should do if it doesn't pass the inspection. ## What Is DMARC? 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 b62f9e37..658c8db8 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 @@ -226,5 +226,5 @@ Similar to FTP you can also grant other users access to only certain directories ## Troubleshooting - When using SFTP, you are always chrooted to the homedir. This implies that when you want to copy a file to `/tmp`, you will receive an error, as the `tmp/` directory does not exist in the configured homedir. -- If you experience a ‘Connection timed out’ error, please check in our service panel if your IP address is whitelisted. +- If you experience a ‘Connection timed out’ error, please check in the Control Panel (Hypernode > **Allowlist**) if your IP address is whitelisted. - If the IP is whitelisted and you still get this error: Check your local firewall and antivirus logs. diff --git a/docs/hypernode-platform/mysql/how-to-free-disk-space-from-mysql-ibdata1.md b/docs/hypernode-platform/mysql/how-to-free-disk-space-from-mysql-ibdata1.md index 1bbc7a7b..15dbcb78 100644 --- a/docs/hypernode-platform/mysql/how-to-free-disk-space-from-mysql-ibdata1.md +++ b/docs/hypernode-platform/mysql/how-to-free-disk-space-from-mysql-ibdata1.md @@ -43,6 +43,6 @@ This procedure includes: - restarting MySQL - re-importing the databases from the backup -As mentioned [in this Stack Exchange article](http://dba.stackexchange.com/questions/24942/how-do-i-shrink-the-innodb-file-ibdata1-without-dumping-all-databases) there sadly is no other solution than the aforementioned procedure. +As mentioned [in this Stack Exchange article](https://dba.stackexchange.com/questions/24942/how-do-i-shrink-the-innodb-file-ibdata1-without-dumping-all-databases) there sadly is no other solution than the aforementioned procedure. **If you're encountering this problem on a Hypernode, please contact support@hypernode.com so we can help you reclaim your disk space!** diff --git a/docs/hypernode-platform/mysql/how-to-use-phpmyadmin.md b/docs/hypernode-platform/mysql/how-to-use-phpmyadmin.md index e4d32706..bfc1309a 100644 --- a/docs/hypernode-platform/mysql/how-to-use-phpmyadmin.md +++ b/docs/hypernode-platform/mysql/how-to-use-phpmyadmin.md @@ -112,7 +112,7 @@ deny all; Now make sure to set a symlink from within your webroot: `ln -s /usr/share/phpmyadmin/ dbadmin` -And finally visit phpMyAdmin on +And finally visit phpMyAdmin on `https://yourdomain.nl/dbadmin` **This will only add another URL where phpMyAdmin is accessible. If you only want to use this endpoint, block all access to `/phpmyadmin` too** diff --git a/docs/hypernode-platform/nginx/how-to-use-nginx.md b/docs/hypernode-platform/nginx/how-to-use-nginx.md index af011b5a..5d8207d4 100644 --- a/docs/hypernode-platform/nginx/how-to-use-nginx.md +++ b/docs/hypernode-platform/nginx/how-to-use-nginx.md @@ -125,7 +125,7 @@ For example, you want every URL starting with `/fr` to redirect to ). +This will also maintain subfolders and query strings (such as `http://yourshop.com/fr/subfolder?arguments`). If the move is only temporary, you should use redirect instead of permanent. diff --git a/docs/hypernode-platform/ssh/how-to-log-in-to-the-hypernode-with-ssh.md b/docs/hypernode-platform/ssh/how-to-log-in-to-the-hypernode-with-ssh.md index 0ee8a161..c9ba3270 100644 --- a/docs/hypernode-platform/ssh/how-to-log-in-to-the-hypernode-with-ssh.md +++ b/docs/hypernode-platform/ssh/how-to-log-in-to-the-hypernode-with-ssh.md @@ -23,7 +23,7 @@ NB: If you want to create SSH keys, please read the article: [Create SSH Keys on ### Log in Using PuTTY -To use PuTTY you need to download this program from the [PuTTY website](http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html). To connect to Hypernode you’ll have to use your SSH hostname (name.hypernode.io) and username (app). +To use PuTTY you need to download this program from the [PuTTY website](https://www.putty.org/). To connect to Hypernode you’ll have to use your SSH hostname (name.hypernode.io) and username (app). If you ordered your Hypernode plan or trial via Hypernode.com, you received your SSH hostname and IP address via email as soon as your Hypernode is ready for use. diff --git a/docs/hypernode-platform/ssh/how-to-use-ssh-keys-on-hypernode.md b/docs/hypernode-platform/ssh/how-to-use-ssh-keys-on-hypernode.md index 1cbf8b10..f8e5a9fc 100644 --- a/docs/hypernode-platform/ssh/how-to-use-ssh-keys-on-hypernode.md +++ b/docs/hypernode-platform/ssh/how-to-use-ssh-keys-on-hypernode.md @@ -17,7 +17,7 @@ This tutorial shows how to create a keypair and use PuTTY (for Windows users) or ## For Windows Users (PuTTY) -To generate an SSH keypair and connect to your Hypernode, you’ll need to use three different programs; PuTTY, PuTTYgen and Pageant. Download these programs from the [PuTTY website](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html). Follow the next steps. +To generate an SSH keypair and connect to your Hypernode, you’ll need to use three different programs; PuTTY, PuTTYgen and Pageant. Download these programs from the [PuTTY website](https://www.putty.org/). Follow the next steps. ### Generate the Keypair With PuTTYgen diff --git a/docs/hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md b/docs/hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md index 8ceaab29..5f614e9d 100644 --- a/docs/hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md +++ b/docs/hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md @@ -143,7 +143,7 @@ All files in /data/web/nginx starting with public.\* will be included in front o ## 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 [https://example.com](https://yourdomain.com) directly will get an error message, either indicating that there is no https available or a plain connection refused error. +If you use the www-izer forwarders in the DNS settings for your domain name, people that visit [https://example.com](https://example.com) 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 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 8c21d0ac..0026bec5 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 @@ -13,7 +13,7 @@ redirect_from: ## What Kind of Certificates Can I Order via Hypernode? -At Hypernode you can request various SSL certificates via the [Control Panel](https://my.hypernode.com/login/). There are three types of certificates: +At Hypernode you can request various SSL certificates via the [Control Panel](https://my.hypernode.com/). There are three types of certificates: - SSL single certificate; you can use this on a single domain for the naked domain and the www domain (`example.com` and `www.example.com`). - SSL wildcard certificate; You can use this to secure all subdomains (`*.example.nl`) for your domain name, but also on `www.example.nl` and the naked domain (ie `example.nl`). However, this certificate does not work on `*.*.example.nl`. @@ -31,7 +31,7 @@ The costs for an SSL certificate consist of two aspects: the costs for the actua | Wildcard | € 75,00 | € 80,00 | € 155,00 | | EV | € 95,00 | € 80,00 | € 175,00 | -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)). +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 the Control 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 link the SSL certificate to the right Hypernode (which can be done with [one click](../ssl/how-to-use-a-custom-ssl-certificate-on-hypernode.md#link-a-custom-ssl-certificate-to-a-hypernode)). @@ -51,7 +51,7 @@ If the company validation step fails, for example because the company name at Hy ### Domain Validation -For a domain validated certificate, the certificate issuer only performs domain validation. When the domain name runs on the Byte name servers, we can do the validation for you. If not, the default method of doing this will be email validation. You will receive an email for this on a standard email address; admin, administrator, hostmaster, postmaster, or webmaster@example.nl. In some cases the address from the whois data is also possible. Unfortunately, other email addresses cannot be used for this, because only these emails are accepted by the CA/B forum. If it is not possible to use one of these email addresses, you can also choose CNAME validation. To do this, a CNAME record must be added to the domain name's DNS that can be verified by the certificate issuer. To request this option, you can send an email to support@hypernode.com, you will then receive the record that needs to be added to the DNS. +For a domain validated certificate, the certificate issuer only performs domain validation. When the domain name runs on the Hypernode name servers, we can do the validation for you. If not, the default method of doing this will be email validation. You will receive an email for this on a standard email address; admin, administrator, hostmaster, postmaster, or webmaster@example.nl. In some cases the address from the whois data is also possible. Unfortunately, other email addresses cannot be used for this, because only these emails are accepted by the CA/B forum. If it is not possible to use one of these email addresses, you can also choose CNAME validation. To do this, a CNAME record must be added to the domain name's DNS that can be verified by the certificate issuer. To request this option, you can send an email to support@hypernode.com, you will then receive the record that needs to be added to the DNS. ### Whois Validation @@ -61,7 +61,7 @@ The Whois register records who owns a domain name. Nowadays it is no longer requ When applying for EVs, it is necessary to sign the EV Documents. These documents consist of a Certificate Request Form & Certificate Subscriber Agreement (contract). You will receive a link by email to sign the Sectigo Subscriber Agreement online. -If the EV Documents are not signed, the certificate cannot be delivered. If you do not receive these documents, you can have resend them via the Service Panel. +If the EV Documents are not signed, the certificate cannot be delivered. If you do not receive these documents, please contact [support@hypernode.com](mailto:support@hypernode.com) to have them resent. ### Phone Validation diff --git a/docs/hypernode-platform/tools/how-to-configure-lesti-fpc.md b/docs/hypernode-platform/tools/how-to-configure-lesti-fpc.md index 99fe125b..ada84dd6 100644 --- a/docs/hypernode-platform/tools/how-to-configure-lesti-fpc.md +++ b/docs/hypernode-platform/tools/how-to-configure-lesti-fpc.md @@ -22,7 +22,7 @@ This module also works in combination with `Redis`. This article will explain how to configure Lesti::FPC and use it on Hypernode. It is however recommended to first enable [Redis Cache](../../ecommerce-applications/magento-1/how-to-configure-redis-for-magento-1.md) as your caching backend before proceeding with this tutorial. -**NB: When you used the [hypernode-importer](how-to-migrate-your-shop-to-hypernode.md#option-2-for-all-customers-migrate-your-shop-via-shell-using-the-hypernode-importer) and you were already using `Lesti::FPC`, you can skip this tutorial, as we already added the configuration for caching using `Lesti::FPC`.** +**NB: When you used the [hypernode-importer](how-to-migrate-your-shop-to-hypernode.md#migrate-your-shop-via-shell-using-the-hypernode-importer) and you were already using `Lesti::FPC`, you can skip this tutorial, as we already added the configuration for caching using `Lesti::FPC`.** ## Download Lesti::FPC diff --git a/docs/hypernode-platform/tools/how-to-copy-your-hypernode-to-another-hypernode.md b/docs/hypernode-platform/tools/how-to-copy-your-hypernode-to-another-hypernode.md index 1af316c9..6db35a4e 100644 --- a/docs/hypernode-platform/tools/how-to-copy-your-hypernode-to-another-hypernode.md +++ b/docs/hypernode-platform/tools/how-to-copy-your-hypernode-to-another-hypernode.md @@ -39,7 +39,7 @@ hypernode-importer --user app --host old-appname.hypernode.io --path /data/web/m ## 4. Base-URLS -One last step is to change the Base-URLS into the right URL for example: [https://newappname.hypernode.io/](https://appname%28new%29.hypernode.io/) +One last step is to change the Base-URLS into the right URL for example: `https://newappname.hypernode.io/` You're able to request Let's Encrypt for this vhost: ```bash diff --git a/docs/hypernode-platform/tools/how-to-debug-long-running-php-processes-with-livestack.md b/docs/hypernode-platform/tools/how-to-debug-long-running-php-processes-with-livestack.md index 7912a3ae..f9dd20f2 100644 --- a/docs/hypernode-platform/tools/how-to-debug-long-running-php-processes-with-livestack.md +++ b/docs/hypernode-platform/tools/how-to-debug-long-running-php-processes-with-livestack.md @@ -41,7 +41,7 @@ app 1614969 0.0 0.0 2584 932 ? S 10:39 23:51 /usr/bin/php The ps output shows this process has been running for a long time. It may be in a loop, or waiting on something, or just processing way too many things---but you don't know yet. -If you knew where to look you could use XDebug locally or on your [staging server](/hypernode-platform/php/remote-debugging.md), but the first step is knowing where to look. +If you knew where to look you could use XDebug locally or on your [staging server](../php/remote-debugging.md), but the first step is knowing where to look. Using livestack.py you can pause the program momentarily and print out a stacktrace. Now you have an idea what the program is currently running. By running livestack.py a few times, you can see in which area of the code PHP is spending the most time. @@ -92,7 +92,7 @@ You may not yet know what exactly is causing the problem, but you can start your ## Examining long running web requests -You may already know how to use livefpm and hypernode-fpm-status to see [what kinds of requests your Hypernode is currently serving](/hypernode-platform/tools/what-kind-of-request-is-my-hypernode-serving.md). +You may already know how to use livefpm and hypernode-fpm-status to see [what kinds of requests your Hypernode is currently serving](what-kind-of-request-is-my-hypernode-serving.md). You can investigate any long running requests further using livestack.py. As `hypernode-fpm-status | grep '/some/url'` would give you current PHP process generating some url, you can also run `livestack.py --fpm '/some/url'` to find the current stack trace of that PHP process. diff --git a/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md b/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md index f97061b4..d96e7632 100644 --- a/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md +++ b/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md @@ -32,38 +32,13 @@ If your vhost isn't the right `type`, you should chance the type of the vhost. Y hypernode-manage-vhosts example.com --type TYPE ``` -## Option 1: for Service Panel users: Use the Shop Importer on [service.byte.nl](https://service.byte.nl) - -**Service Panel** customers have access to the importer tool via [service.byte.nl](https://service.byte.nl). -If you use the Shop importer on our Service Panel, all you have to do is to fill in the correct information on the form, click "Importeer shop" and in the background your shop will be automatically imported on your Hypernode. - -If you use the Shop importer on our Service Panel, locally on the node the `hypernode-importer` utility is ran. This is a fully scripted migration tool that executes all the tasks that need to be done when migrating a shop. This includes: - -- Copying the database -- Copying all the content -- Replacing caching through `memcached` with `Redis` -- Adjusting symlinks and paths -- Repairing the modman directory if existent -- Set old/current shop in Maintenance mode -- And several other options. - -### Selecting the Maintenance Mode in the Shop Importer Tool - -Please only select this option if you run the Importer tool for the second time, to do a last sync before going live on Hypernode. - -When you select the maintenance box in the importer tool in the Service Panel, the importer wil create a maintenance flag (file: maintenance.flag) in the root of your current/old Magento shop (this function isn't Shopware compatible yet). Please be aware that your current website won't be available for your visitors. When the migration has been finished you need to modify your DNS settings: - -\*If your domain is hosted at Hypernode, there is a quick and easy way to switch your DNS to the Hypernode. Login into the [Service Panel](https://service.byte.nl). Make sure your Hypernode is selected in the dropdown menu -> Instellingen -> SSL & DNS instellingen -> Find your domain in the list -> change the 'Beschikbaar' value into 'Koppel domeinnaam aan deze Hypernode'. Repeat these steps for all the domains that should be linked to your Hypernode. - \*If your domain is being hosted externally, you need to change the DNS settings manually. Read [this article](../dns/how-to-manage-your-dns-settings-for-hypernode.md) to see which records you need to modify. -\*Although the Shop importer is a very easy way to import a shop, please keep in mind that is using the command line is a requirement. So if needed, find yourself an [experienced developer](https://www.byte.nl/partners#specialisms=Hypernode&cms=Magento) that can assist you with these tasks. - -\*The import isn't 100% foolproof so there could be situations in which it doesn't work and you'd have to use the importer-tool via the Shell. +\*Although the importer is a very easy way to import a shop, please keep in mind that it uses the command line. So if needed, find yourself an [experienced developer](https://www.hypernode.com/en/our-partners/) that can assist you with these tasks. -## Option 2: for all Customers: Migrate Your Shop via Shell Using the `hypernode-importer` +## Migrate Your Shop via Shell Using the `hypernode-importer` -Are you a Control Panel (my.hypernode.com)user? Please use the Hypernode Importer tool via Shell. +Please use the Hypernode Importer tool via Shell. *The `hypernode-importer` tool is suitable for both Magento 1 and 2 shops as well as for Shopware 5 and 6 shops* This tool executes the following tasks: @@ -85,7 +60,7 @@ Please follow these steps: - `--user` Enter the SSH user - `--path` Enter the full path to the rootfolder of the shop - `--port`\* Enter the SSH-portnumber, if not given is uses the default: 22 - - `--set-default-url`\* Sets the Base-URL to *.io/* + - `--set-default-url`\* Sets the Base-URL to `http://APPNAME.hypernode.io/` - `--skip-db-import`\* Skips the database import - `--skip-file-import`\* Skips the files import - Use `--help` to list additional options @@ -102,6 +77,6 @@ Done? Now it's time to [check if everything works](../../best-practices/testing/ ## Tips and Tricks - You could also use `screen` or `tmux` to migrate your shop in a terminal session. Use `man screen` or `man tmux` to learn more about these commands. -- The Shop importer first uses `rsync` to copy the file content and retrieves the database credentials required to dump the database from the copied configuration files. This implies that if you already imported another shop before, you should first remove the old content of the other shop before migrating a new one. +- The importer first uses `rsync` to copy the file content and retrieves the database credentials required to dump the database from the copied configuration files. This implies that if you already imported another shop before, you should first remove the old content of the other shop before migrating a new one. *Starting over and need a fresh Magento or Shopware install? With the `preinstall` option can start over with just one single command* 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 782584aa..19a0ab98 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 @@ -74,7 +74,7 @@ default "Development restricted area"; Do you want to check a webshop on a development plan using MageReport? Add the username, the password and the domain name to the URL like this: - +`https://www.magereport.com/scan/?s=username:password@dev.example.com` Alternatively you can whitelist add the IP’s MageReport uses to scan your Hypernode. diff --git a/docs/hypernode-platform/tools/how-to-use-mailhog-on-hypernode.md b/docs/hypernode-platform/tools/how-to-use-mailhog-on-hypernode.md index c64dbca1..5f8c7e0e 100644 --- a/docs/hypernode-platform/tools/how-to-use-mailhog-on-hypernode.md +++ b/docs/hypernode-platform/tools/how-to-use-mailhog-on-hypernode.md @@ -47,7 +47,7 @@ If HMV ([Hypernode Managed Vhosts](../nginx/hypernode-managed-vhosts.md)) is ena hypernode-manage-vhosts mailhog.example.hypernode.io --https --force-https --type mailhog ``` -After you've whitelisted your IP-address in ~/nginx/mailhog.example.hypernode.io/server.basicauth.conf, MailHog will be accessible through +After you've whitelisted your IP-address in ~/nginx/mailhog.example.hypernode.io/server.basicauth.conf, MailHog will be accessible through `https://mailhog.example.hypernode.io` ## How to Deactivate Mailhog diff --git a/docs/hypernode-platform/tools/how-to-use-periodic-tasks-cronjobs-on-hypernode.md b/docs/hypernode-platform/tools/how-to-use-periodic-tasks-cronjobs-on-hypernode.md index 2fd5b86d..8f236b34 100644 --- a/docs/hypernode-platform/tools/how-to-use-periodic-tasks-cronjobs-on-hypernode.md +++ b/docs/hypernode-platform/tools/how-to-use-periodic-tasks-cronjobs-on-hypernode.md @@ -100,7 +100,7 @@ When you use `crontab -e` for the first time, you’ll be asked which editor you ## Recommendations - Idem-potency: When you write your own cron script, make sure the script is idempotent. When a script should only be run after a certain time or when a new import file is present, always make sure to exit the script when the conditions are not met. This avoids things breaking down when people run cron scripts manually to debug cron issues. -- Time is always based on UTC (= GMT). This might differ from your local time: Dutch time is UTC+1 in winter and UTC+2 in summer. Or use this [handy converter](http://www.timeanddate.com/worldclock/)) +- Time is always based on UTC (= GMT). This might differ from your local time: Dutch time is UTC+1 in winter and UTC+2 in summer. Or use this [handy converter](https://www.timeanddate.com/worldclock/)) - Do not run the Magento crons using `wget` or `curl`, as this is slow, might give partial results, and occupies webslots for real visitors). See above how to invoke the non-HTTP Magento cron. - Do not run the same cron simultaneously on multiple hosts, as results are unpredictable. When migrating, do not forget to disable the old crons. - Be carefull when using day of month and day of week together. Using `Dom` and `Dow` without wildcards makes this an `OR` condition and not an `AND`, running the job more often then you’d expect. 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 3c793662..9673151b 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 @@ -13,7 +13,7 @@ redirect_from: # How to Use the hypernode-systemctl CLI Tool -The `hypernode-systemctl` tool allows you to set certain values for your Hypernode via the command line interface. In the past we asked you to contact support or to go to your Service Panel or Control Panel to change a setting. The `hypernode-systemctl` tool saves valuable time and makes developing and maintaining a Magento shop even more easier. +The `hypernode-systemctl` tool allows you to set certain values for your Hypernode via the command line interface. In the past we asked you to contact support or to go to your Control Panel to change a setting. The `hypernode-systemctl` tool saves valuable time and makes developing and maintaining a Magento shop even more easier. ## Which Settings Can Be Changed on Your Hypernode? @@ -239,7 +239,7 @@ Besides changing settings, the hypernode-systemctl tool also allows you to white `hypernode-systemctl whitelist --help` -This tool works with the same whitelists (FTP, WAF and external database) as the Service and Control Panel. So if you would whitelist a certain IP through the hypernode-systemctl tool, it would then also show in the Service and Control Panel and vice versa. You can use the two tools interchangeably. +This tool works with the same whitelists (FTP, WAF and external database) as the Control Panel. So if you would whitelist a certain IP through the hypernode-systemctl tool, it would then also show in the Control Panel and vice versa. You can use the two tools interchangeably. ### Seeing Your Current Whitelists diff --git a/docs/hypernode-platform/varnish/how-to-enable-varnish-on-hypernode.md b/docs/hypernode-platform/varnish/how-to-enable-varnish-on-hypernode.md index 862db2b0..381130c5 100644 --- a/docs/hypernode-platform/varnish/how-to-enable-varnish-on-hypernode.md +++ b/docs/hypernode-platform/varnish/how-to-enable-varnish-on-hypernode.md @@ -16,7 +16,7 @@ Customers with a Trial, Falcon S (or up) or Eagle plan can use Varnish to boost ## Enable Varnish 4.0, 6.0 or 7.x -At Hypernode it’s possible to enable Varnish 4.0, 6.0 or 7.x via the Control Panel, Service Panel or CLI. The Varnish version needed depends on the application version you’re running. +At Hypernode it’s possible to enable Varnish 4.0, 6.0 or 7.x via the Control Panel or CLI. The Varnish version needed depends on the application version you’re running. **Enable Varnish via the [Control Panel](https://auth.hypernode.com/)** diff --git a/docs/services/control-panel/how-to-change-your-hypernode-settings.md b/docs/services/control-panel/how-to-change-your-hypernode-settings.md index 9c04d671..e53c2415 100644 --- a/docs/services/control-panel/how-to-change-your-hypernode-settings.md +++ b/docs/services/control-panel/how-to-change-your-hypernode-settings.md @@ -17,7 +17,7 @@ The Control Panel offers an overview of your Hypernode’s statistics and settin ## How to Change These Settings -The settings below can be configured through our hypernode-systemctl tool. The hypernode-systemctl tool allows you to set certain values for your Hypernode via the command line interface. In the past we asked you to contact support or to go to your Service Panel to change a setting. The hypernode-systemctl tool saves valuable time and makes developing and maintaining a Magento shop even more easier. +The settings below can be configured through our hypernode-systemctl tool. The hypernode-systemctl tool allows you to set certain values for your Hypernode via the command line interface. In the past we asked you to contact support or to go to your Control Panel to change a setting. The hypernode-systemctl tool saves valuable time and makes developing and maintaining a Magento shop even more easier. ## The Settings in the Control Panel diff --git a/docs/services/control-panel/how-to-use-the-dns-check.md b/docs/services/control-panel/how-to-use-the-dns-check.md index eb7498b8..a668abd6 100644 --- a/docs/services/control-panel/how-to-use-the-dns-check.md +++ b/docs/services/control-panel/how-to-use-the-dns-check.md @@ -75,7 +75,7 @@ This means that [www.example.com](http://www.example.com) will point to wherever ### A Record -One way to redirect your apex (or naked) domain, when the domain is not hosted on the Byte name servers, is to use the www-izers: +One way to redirect your apex (or naked) domain, when the domain is not hosted on the Hypernode name servers, is to use the www-izers: | | | | | | ------------------------------------- | -------- | ------- | ------------- | diff --git a/docs/services/domain-procedures/everything-about-presence-plans-and-domains.md b/docs/services/domain-procedures/everything-about-presence-plans-and-domains.md deleted file mode 100644 index bc63535f..00000000 --- a/docs/services/domain-procedures/everything-about-presence-plans-and-domains.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -myst: - html_meta: - description: 'If you want to register a domain name with Hypernode, you can do - this using our Presence plan. Read everything there is to know about it here. ' - title: Presence Plans and Domains | Hypernode -redirect_from: - - /en/services/domains/everything-about-presence-plans-and-domains/ ---- - - - -# Everything About Presence Plans and Domains - -**Please note that this only applies to Service Panel users who log in via service.byte.nl. We don't offer domain registration for our international customers at the moment.** - -If you want to register a domain name with Hypernode, you can do this using our Presence plan. A Presence plan does not come with hosting space, but it does offer the possibility to create email aliases (addresses) and easily set up a forward address. Do you have multiple domain names that you want to register? Then you also need multiple Presence plans. This article explains what you can do with your Presence plan. - -## Why Do I Need a Presence Plan? - -With a Presence plan you can register a domain name with us. A Presence plan is required for every separate domain name that you want to register. In short, it's a plan to register domain names and link multiple domain names to your website. - -## Features - -In addition to registering a domain name with a Presence plan, you can also use it as a forwarding option. In other words, when people visit yourdomain.com, you can automatically forward them to another domain / website. A Presence plan can also be used as a "virtual host". Suppose you have registered a domain externally but want to order an SSL certificate from Hypernode. You need a Presence plan for this, as your domain needs to  be in the Hypernode administration. You do not necessarily have to transfer the domain to Hypernode to purchase an SSL certificate. - -We offer two different Presence plans: - -- *Presence - 1 year* - In addition to the features listed above, you can create 100 email aliases that you forward to existing email addresses. You cannot create email boxes with a Presence plan, because you do not have email storage. The contract term for this plan is 1 year. -- *Presence Plus* - The Presence Plus plan has all the features of a Presence 1 year plan, plus email storage. In addition to the option to create 2000 email aliases, you also have access to 100 mailboxes. This plan is very suitable for our Hypernode customers who, in addition to webshop hosting, also want to purchase domain registration and / or email hosting from Hypernode. The contract term of this package is 1 year. - -## Forward Options - -A Presence plan offers three different forward options: - -- Frames -- Forwarder (redirect) -- Server Alias - -### Frames - -With a frame you ensure, just like with a Server Alias, that the address (url) remains in the address bar. A frame of 100% is placed in the page, where the website you are referring to will be placed. This method can cause problems with Javascripts on the target page (javascript errors). - -### Forward (redirect) - -If you are using a forwarder (also called Location or 301 redirect), the address of the target domain will appear in the address bar of the browser. For example, when a visitor types [www.forwarder.nl](http://www.forwarder.nl) in the address bar, [www.goalpage.nl](http://www.goalpage.nl) will appear in the address bar. The visitor thus sees that he is being forwarded. However, the target page does not have to be hosted by Hypernode. - -### Server Alias - -With a [Server Alias](https://www.byte.nl/kennisbank/doorverwijzen/server-alias) you make sure that the address (url) remains in the address bar. For example, it is possible to forward a visitor from apple.nl to the website under strawberry.nl, but the visitor will see apple.nl in their address bar. Behind the scenes, the strawberry.nl site is displayed. This method only works if both domain names are hosted at Hypernode. - -## Set a Forward - -To use one of the three referral options mentioned above, follow the steps below: - -1. Log in to the [Service Panel](https://service.byte.nl/). Forgot Password? Create a new password. -1. Click on the desired domain name. -1. Click the Instellingen tab. -1. Click on Presence. -1. At **WEB address** enter the location to which the Presence plan should refer. -1. Check Frames, Forwarder (redirect) or Server Alias. -1. Click on Save. - -## Changing the Name Servers - -Do you want to change the name servers of your domain? Please shoot us an email and we can make this change for you. diff --git a/docs/services/domain-procedures/how-to-transfer-your-domain-away-from-hypernode.md b/docs/services/domain-procedures/how-to-transfer-your-domain-away-from-hypernode.md index 30872f00..dbab84d9 100644 --- a/docs/services/domain-procedures/how-to-transfer-your-domain-away-from-hypernode.md +++ b/docs/services/domain-procedures/how-to-transfer-your-domain-away-from-hypernode.md @@ -6,14 +6,13 @@ myst: title: How to transfer your domain away from Hypernode? redirect_from: - /en/services/domains/how-to-transfer-your-domain-away-from-hypernode/ + - /en/services/domains/how-to-transfer-your-domain-name-to-another-provider/ --- # How to Transfer Your Domain Away From Hypernode -**Please note that this only applies to Control Panel users who log in via my.hypernode.com. If you use the Service Panel (service.byte.nl), you can use [this article](how-to-transfer-your-domain-away-from-hypernode.md) to transfer your domain away from Hypernode.** - ## **I Want to Transfer My Domain Name to Another Provider** To transfer your domain name to another hosting provider, take the following steps: diff --git a/docs/services/domain-procedures/how-to-transfer-your-domain-name-to-another-provider-service-panel.md b/docs/services/domain-procedures/how-to-transfer-your-domain-name-to-another-provider-service-panel.md deleted file mode 100644 index 670c3504..00000000 --- a/docs/services/domain-procedures/how-to-transfer-your-domain-name-to-another-provider-service-panel.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -myst: - html_meta: - description: Moving your domain to a different provider doesn't have to be difficult. - With the Service Panel, you can easily transfer your domain in a few simple - steps. - title: How to transfer your domain to another provider? | Service Panel -redirect_from: - - /en/services/domains/how-to-transfer-your-domain-name-to-another-provider/ ---- - - - -# How to Transfer Your Domain Name to Another Provider (Service Panel) - -**Please note that this only applies to Service Panel users who log in via service.byte.nl. If you use the Control Panel (my.hypernode.com), you can use this article to transfer your domain to Hypernode.** - -## **I Want to Transfer My Domain Name to Another Provider** - -To transfer your domain name to another hosting provider, take the following steps: - -### **Step 1 – Cancel Your Subscription With Hypernode** - -Most domain names need an authorization code or token to initiate the transfer. This code or token will be emailed to your customer account  registrant email address when you cancel your subscription: - -- Log on to the [Control Panel](https://my.hypernode.com/) with your customer number and password -- Click the domain you wish to transfer -- Click “Opzeggen” under the tab ‘Administratief’. -- Choose: “Ik wil het domein wegverhuizen naar een andere provider” -- Please provide us with your feedback as to why you wish to terminate your contract. -- Check the box: “Ik verklaar kennis te hebben genomen van het bovenstaande en ga hiermee akkoord. “ -- Fill in your Service Panel password and click: “Bevestigen” -- If an AUTH code is needed, it will be sent to the ‘Registrant’ email address. - -**If you don’t cancel the subscription, you will keep receiving invoices and will not receive an AUTH/transfer code.** - -### **Step 2 – Request the Transfer at Your New Hosting Provider** - -Please contact your new provider to initiate the transfer. They will explain what you’ll need to do to transfer the domain name. We can not transfer the domain name for you. The responsibility of the transfer of a domain name lies with the new Provider. - -**My new provider says that Hypernode has to initiate the transfer** - -The new provider has to start the transfer. The procedure has been designed so that the **owner** can order **any new provider** to transfer the domain. If you have any doubts concerning this, please check at [ICANN](http://www.icann.org/). Hypernode will not discuss the standard policies of ICANN or the gTLD operators. - -## **Procedure** - -- Hypernode will fully cooperate with any transfer that has correctly been passed in writing. -- If the proper documents are received, Hypernode  allows the transfer by changing the status of the domain to ACTIVE. -- The **new hosting provider** initiates the transfer at **their registrar**. -- Hypernode will accept the request for transfer within 1-2 days, after that the domain name will be transferred. -- In case of **.nl/.com/.net/.org/.biz/.info/.de/.nu** domain names: Hypernode will sent the AUTH code to the registered e-mail address on transfer. -- In case of **.be** domains we will not send the auth code automatically after you cancelled your subscription. Because a code for a.be domain is only valid for 7 days, we urge you to request the code at the moment that you want to initiate the transfer with the [Belgium registry](https://www.dnsbelgium.be/nl). The code will then be sent to the Registrant email address. If this is still our e-mail address, we will forward the code to the registrant address known to us. -- In case of **co.uk**domains you'll need the registrar-tag for the new provider to push the domain to. Your new provider needs to let you know which tag to use so you can inform us. We will then process this Registrar Tag and “push” the domain to your new hosting provider. diff --git a/docs/services/domain-procedures/how-to-undo-the-cancellation-of-a-domain-name.md b/docs/services/domain-procedures/how-to-undo-the-cancellation-of-a-domain-name.md index e4be9452..991e5eb3 100644 --- a/docs/services/domain-procedures/how-to-undo-the-cancellation-of-a-domain-name.md +++ b/docs/services/domain-procedures/how-to-undo-the-cancellation-of-a-domain-name.md @@ -12,8 +12,6 @@ redirect_from: # How to Undo the Cancellation of a Domain Name -**Please note that this only applies to Service Panel users who log in via service.byte.nl. We don't offer domain registration for our Control Panel users at the moment.** - For 40 days after you cancel a domain name, it can't be re-registered by anyone except you. It's 'in quarantine'. So, if your cancelled your domain by mistake, or you change your mind, you can get your domain back. ## My Domain Is in Quarantine diff --git a/docs/services/domain-procedures/how-to-use-domains-in-the-control-panel.md b/docs/services/domain-procedures/how-to-use-domains-in-the-control-panel.md index 4c90cfce..17d857c0 100644 --- a/docs/services/domain-procedures/how-to-use-domains-in-the-control-panel.md +++ b/docs/services/domain-procedures/how-to-use-domains-in-the-control-panel.md @@ -6,6 +6,7 @@ myst: title: How to use Domains in the Control Panel? | Hypernode redirect_from: - /en/services/domains/how-to-use-domains-in-the-control-panel/ + - /en/services/domains/everything-about-presence-plans-and-domains/ --- diff --git a/docs/services/magereport/magereport-premium.md b/docs/services/magereport/magereport-premium.md index f63aa22f..7bf3de94 100644 --- a/docs/services/magereport/magereport-premium.md +++ b/docs/services/magereport/magereport-premium.md @@ -27,7 +27,7 @@ Anyone can scan their Magento shop with [MageReport.com](http://magereport.com/) The Performance checks and charts offer specific information about your shop’s performance and help you optimize your Hypernode. That’s why MageReport for Hypernode users is called MageReport Premium. -Accessing [MageReport Premium](http://magereport.com/) is easy by logging on to MageReport.com with your Hypernode customer account. Choose ‘Sign in with Byte’(for Service Panel users) or 'Sign in with Hypernode' (for Control Panel users) on your top right. +Accessing [MageReport Premium](http://magereport.com/) is easy by logging on to MageReport.com with your Hypernode customer account. Choose 'Sign in with Hypernode' on your top right. ## Security Level diff --git a/docs/troubleshooting/performance/how-to-fix-invalid-form-key-error.md b/docs/troubleshooting/performance/how-to-fix-invalid-form-key-error.md index 1fff7e0e..3e5fee50 100644 --- a/docs/troubleshooting/performance/how-to-fix-invalid-form-key-error.md +++ b/docs/troubleshooting/performance/how-to-fix-invalid-form-key-error.md @@ -82,4 +82,4 @@ However, this should only be used as a temporary measure, so you can figure out ## Need help? -Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to [contact one of these agencies](https://www.magereport.com/page/support). +Magento is no easy open source CMS. Although we’re very skilled in hosting Magento shops, making them fast and keeping conversion high, we’re no Magento developers. Luckily, we know a lot of agencies that do know a lot about how Magento works. If you need help, don’t hesitate to [contact one of these agencies](https://www.hypernode.com/en/our-partners/). diff --git a/docs/troubleshooting/performance/how-to-optimise-your-magento-disk-performance.md b/docs/troubleshooting/performance/how-to-optimise-your-magento-disk-performance.md index 4a14f2af..543dba06 100644 --- a/docs/troubleshooting/performance/how-to-optimise-your-magento-disk-performance.md +++ b/docs/troubleshooting/performance/how-to-optimise-your-magento-disk-performance.md @@ -63,7 +63,7 @@ Apart from the flat I/O usage line in the MageReport graph, you will likely expe ### Short Term Solution -Upgrade your Hypernode through our Service Panel. This will not only increase your base I/O capacity, but also reset the burst pool, so you will start with a clean slate. +Upgrade your Hypernode through the Control Panel. This will not only increase your base I/O capacity, but also reset the burst pool, so you will start with a clean slate. Important: From 444462eef01c50b910fbb57a8876f867175271fa Mon Sep 17 00:00:00 2001 From: poespas Date: Wed, 16 Sep 2026 11:57:52 +0200 Subject: [PATCH 2/2] Fix markdown formatting in docs --- docs/hypernode-deploy/applications/config-for-magento-2.md | 4 ++-- docs/hypernode-deploy/applications/config-for-shopware-6.md | 4 ++-- .../email/how-to-configure-the-spam-filter.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/hypernode-deploy/applications/config-for-magento-2.md b/docs/hypernode-deploy/applications/config-for-magento-2.md index e8442838..e5840130 100644 --- a/docs/hypernode-deploy/applications/config-for-magento-2.md +++ b/docs/hypernode-deploy/applications/config-for-magento-2.md @@ -1,8 +1,8 @@ --- myst: html_meta: - description: Example Hypernode Deploy deploy.php configuration for Magento 2, including - themes, static content locales, shared files and custom build steps. + description: Example Hypernode Deploy deploy.php configuration for Magento 2, + including themes, static content locales, shared files and custom build steps. title: Hypernode Deploy Config for Magento 2 | Hypernode --- diff --git a/docs/hypernode-deploy/applications/config-for-shopware-6.md b/docs/hypernode-deploy/applications/config-for-shopware-6.md index d067050d..68011d6e 100644 --- a/docs/hypernode-deploy/applications/config-for-shopware-6.md +++ b/docs/hypernode-deploy/applications/config-for-shopware-6.md @@ -1,8 +1,8 @@ --- myst: html_meta: - description: Example Hypernode Deploy deploy.php configuration for a Shopware 6 - shop, using the Shopware 6 application template. + description: Example Hypernode Deploy deploy.php configuration for a Shopware + 6 shop, using the Shopware 6 application template. title: Hypernode Deploy Config for Shopware 6 | Hypernode --- diff --git a/docs/hypernode-platform/email/how-to-configure-the-spam-filter.md b/docs/hypernode-platform/email/how-to-configure-the-spam-filter.md index bad8e4bf..cfaf8517 100644 --- a/docs/hypernode-platform/email/how-to-configure-the-spam-filter.md +++ b/docs/hypernode-platform/email/how-to-configure-the-spam-filter.md @@ -43,8 +43,8 @@ The diagram below shows an approximation of what happens when you set up the spa If you use Hypernode's mail servers, you can configure the spam filter per mailbox. These settings are not available in the Control Panel; please contact [support@hypernode.com](mailto:support@hypernode.com) to change them for you. When contacting us, we advise you to set the following: - 1. \*\*Marking spam: High.\*\*For example, most of the spam (about 98%) is marked in the subject line and you can have it set aside by your email program - 1. **Blocking spam: Low**. Only obvious spam is blocked and the chance that you will lose a legit email is negligible. +1. \*\*Marking spam: High.\*\*For example, most of the spam (about 98%) is marked in the subject line and you can have it set aside by your email program +1. **Blocking spam: Low**. Only obvious spam is blocked and the chance that you will lose a legit email is negligible. ## Tests by Our Spam Filter