Release 2902: Solr for Excellence plans, fixed session cleaner
11 April 2017: due to low demand we deprecated SOLR in favor of sphinx. Starting now we don’t sell SOLR plans anymore. In today’s release we have: Solr is available on request for all Excellence Hypernodes. Please contact Support if you’d like it enabled. We moved the sessions from one place to the other. We…
Read moreRelease 2856: New Relic 6.2, now also for PHP 7.0
We’ve updated the New Relic agent to the latest version, which is compatible with PHP 7.0. So we’ve also added New Relic to PHP 7.0 when you enable it on the Service Panel. Also, we’ve made some tweaks to the OOM killer, which is a piece of software that is triggered when your Hypernode runs…
Read moreRelease 2498: Magento2 support
Support for Magento2 has been in the works for a while. It started with the update to PHP 5.5 in release 2451. And now we have a first version of Magento2 support for Hypernodes. To get an Nginx config for Magento2: place a file named magento2.flag in /data/web/nginx/ Our Nginx config reloader will pick that…
Read moreRelease 2192: No more PHP memory limits, blocking certain bots entirely
No more memory limits on PHP processes A while ago, we introduced a global cgroup limit on memory. This is a safeguard that makes sure the app user does not use more memory than is healthy for the Hypernode. The total of memory used by processes owned by the app now cannot exceed a certain…
Read moreRelease 1810: Varnish fixes, Turpentine continuous integration
So it’s been a busy week at Hypernode headquarters. There’s been lots of development on internal processes and customers testing Varnish brought up lots of interesting bugs to fix 🙂 This release brings you: Migrating nodes that have Varnish enabled will now just work ™ instead of crashing. We’ve created Jenkins jobs that test Hypernodes…
Read moreRelease 1767: Varnish support
This release features preliminary support for Varnish using the Turpentine module for Magento. The change should not affect current Hypernodes, because Varnish is disabled by default (requests are not routed through Varnish, nor is it started by default so it does not use up any memory). Customer overrides of Nginx should all still work. To…
Read moreRelease 771: vagrant image available, correct blocking of PHP in /media/ and /var/
Vagrant image is now available By popular demand, we’ve been working on a Vagrant image for Hypernode. This image allows you to develop your site on an environment exactly like a Hypernode, only on your own your laptop or PC. Have a look at our Github repo for the Vagrant image and give it a…
Read moreRelease 641: SSLv3 no longer supported
Deprecated SSL protocol SSLv3 no longer supported Many techblogs have reported that a big security hole named POODLE was found in SSL version 3. This protocol version has been deprecated for years in favor of TLS. To keep our Hypernodes safe and care-free, we’ve decided to disable SSLv3 support. Impact The impact will be negligible:…
Read moreRelease 640: 404 optimization, Nginx config warnings in prompt
Missing media no longer triggers Magento 404 Our Nginx configuration contained a flaw that caused all missing media files (images, css, js) to be routed to Magento. Magento then renders a nice 404, but nobody is interested in that page. So we’ve changed the configuration to be more like the standard Magento config for Apache…
Read moreRelease 573: connect suppliers through FTP, Cloudflare support
You can now connect your suppliers through FTP As you might well know, FTP is an old protocol that is, at it’s core, unsafe to use. The protocol uses passwords, and worse, these are sent in plaintext. So up to now, we only offered an SSH logging, thus supporting SFTP, rsync and scp. Unfortunately, there…
Read moreRelease 540: New Relic for Hypernode, set base url in importer
New Relic for Hypernode We’ve added New Relic to our Hypernode stack. You can now inspect the performance of your shop with just a mouseclick. To enable this feature, go to the Service Panel and activate New Relic for your Hypernode now! Thanks, Gertjan! Other fixes Set the base URL when importing One common pitfall when…
Read moreRelease 535: rate limit for bots and more tools
Making sure you can handle bad bots #2 Update March 2016: we have changed the 503 response code (temporarily unavailable) to the – now standard – 429 (too many requests). A few of our customers experienced a scenario where all available PHP worker slots were full. Mostly caused by errant bots, this scenario typically results in…
Read moreRelease 473: begin FPM worker depletion monitoring
Making sure you can handle bad bots A few of our customers experienced a scenario where all available PHP worker slots were full. Mostly caused by errant bots, this scenario typically results in a slow site in mild cases, or timeouts for clients in heavy cases. We want to empower you and make sure you…
Read moreRelease 423: Updated HHVM fixes all currently known problems
Updated HHVM fixes all currently known problems We’ve updated our HHVM binary to the latest daily build. This build includes fixes for all currently known problems with HHVM. The HHVM team fixed a lot (!) of things, but our HHVM guru Daniel Sloof fixed the specific problems below for us. Thanks for championing them, Daniel!…
Read moreRelease 418: Importer now flushes Redis after import
Hypernode Importer tweaks We’re releasing two small fixes to our Hypernode Importer today. This is the tool that imports an existing Magento installation into your Hypernode. It now flushes the Redis cache after it has finished importing. It can now properly handle modules that rewrite the Varien/Autoloader; most notably ExtendWare and AITOC modules. …
Read moreRelease 410: properly set MAGE_RUN_TYPE and MAGE_RUN_CODE
We now properly set MAGE_RUN_TYPE and MAGE_RUN_CODE We’ve corrected an error in our Nginx configuration. We used to always set MAGE_RUN_TYPE to “store” and MAGE_RUN_CODE to “default” in your Magento environment. Luk van den Borne asked us to change this behaviour because it is incorrect. It leads to notorious problems with getting error 404 codes when…
Read moreRelease 405: magento sessions now properly cleaned up
Magento sessions now properly cleaned We’ve recently experienced a couple of outages for individual customers that exhausted the inode capacity on their Hypernode. That is techno-babble for “there were so many files that the disk was full” 🙂 This is an especially hard-to-detect problem for customers, because the maximum-number of files is difficult to monitor and…
Read moreRelease 399: phpMyAdmin now available for use
phpMyAdmin now available for use By popular request we’ve added phpMyAdmin to all Hypernode nodes. It is available at http://myapp.hypernode.io/phpmyadmin Note that phpMyAdmin is only available on the hypernode.io URL, but not on any of your storefronts. This ensures that our phpMyAdmin does not collide or interfere with any of your stores. Read more about…
Read more