Release 8558: Newer Node.js versions, NGINX tweaks and new aliases
With this release, we have added quite some changes we can be proud of! It’s a collection of various improvements, but let’s start with the biggest change! Newer Node.js versions After receiving quite some feedback from our users to include a newer Node.js version, we are proud to announce that we have finally added support […]
Read moreRelease 8546: Redis 6 support!
With this release, we have added support for Redis 6.0 (see Redis release blog post). This version of Redis has many changes and improvements: Performance improvements ACL support Longest Common Subsequence commands Newest Redis protocol RESP3 We have added support for this major Redis version, because Magento >= 2.4.2 has a soft requirement (yes soft, […]
Read moreRelease 8479: Now supporting WooCommerce
With this release we’d like to announce that we’ve added support for WooCommerce on the Hypernode platform! Since WooCommerce (or even WordPress) is just a PHP + MySQL application, we didn’t have to change a lot to add support for this open-source e-commerce solution. While the generic-php vhost type could technically be used, we wanted […]
Read moreRelease 8455: Generic PHP NGINX VHost Type
In this release we have added a new hypernode-manage-vhosts type: Generic PHP. While we mainly support eCommerce applications like Magento, Shopware and Akeneo, the Hypernode platform can be used for other types of applications like Laravel and Symfony as well. To use the new VHost type, use the following command: app@uaikoq-example-magweb-cmbl:~$ hypernode-manage-vhosts app.example.hypernode.io –https –force-https […]
Read moreRelease 8445: Magento 2 preinstall, Varnish 6 thread pools, phpMyAdmin 5.x and NGINX OCSP caching
Magento 2 preinstall improvements It is possible to order a Hypernode with a preinstalled Magento 2 application, or even preinstall Magento 2 on an existing Hypernode. This preinstall has received some changes lately: The store email addresses are now configured with noreply@<appname>.hypernode.io, so now emails sent will actually arrive in your inbox. The preinstall is […]
Read moreRelease 8403: PHP 7.4.28, 8.0.16 and 8.1.3
In this release we’re updating PHP versions to 7.4.28, 8.0.16 and 8.1.3. This is to counter the new CVE-2021-21708, where a bug was found in the PHP function php_filter_float. The changes in the new versions are covered in the PHP changelogs. Please refer to either the PHP 7.4.28 changelog, PHP 8.0.16 changelog or PHP 8.1.3 […]
Read moreRelease 8396: More bash auto completing and logfile monitoring
Bash autocomplete In this release we have added bash auto completion for command line interfaces supervisorctl and varnishadm. supervisorctl With the supervisorctl auto completion, you probably don’t need to lookup the CLI documentation as often anymore. And perhaps you might learn about new subcommands too! varnishadm The varnishadm CLI can be a bit confusing, so […]
Read moreRelease 8341: Logfile monitoring
With this release we’ve started monitoring the /data/web/ directory for log files bigger than 1 GB. When we find such log files, you’ll receive an e-mail once a week with instructions to start rotating your logs using logrotate. But why? We believe that rotating log files is a win-win to both parties. Our backup processes […]
Read moreRelease 8333: Composer 2 as the default system composer
A while back we added composer 2 in a separate path so that users could keep using composer 1 for backwards compatibility. app@levka6-appname-magweb-cmbl:~$ which composer /usr/local/bin/composer app@levka6-appname-magweb-cmbl:~$ which composer2 /usr/local/bin/composer2 Recently we’ve had some users experience issues because software like Shopware 6 which requires composer 2 couldn’t find this alternative composer path. Some of […]
Read moreRelease 8325: Automatic clearing of SOAP WSDL cache when changing PHP version
In this release we’ve added the automatic clearing of the SOAP WSDL cache when changing PHP versions. This prevents users from running into fatal PHP SOAP WSDL errors after running a PHP upgrade and makes sure that such system changes happen even more smoothly. These errors can be caused by the fact that the WSDL […]
Read more