Hypernode features
54 results found
-
add Node version 12 and 14 to hypernode-systemctl settings nodejs_version
Add Node version 12 and 14 to hypernode-systemctl settings nodejs_version.
At the moment it is possible to use version 8, 10, 16 and 18.Snowdog theme use version 12 or 14 for frontools.
Now it breaks on deployment, because deployer use another node version then is set at the the .profile of the app user
3 votes -
honoreren van bepaalde sql settings in my.cnf
het zou fijn zijn als je in de /data/web/my.cnf sql settings zet soals slow log time dat deze ook door de node gehonoreerd worden.
dit kom weg uit de hypernode automatic mail :
Extreme logfiles van MySQLwaarin de index van de customer_price _table ongeveer 4.3 seconden duurt en daar krijg ik dus best wat mail van.
er is nu geen manier voor gebruiker om iets van mysql te dresseren .3 votes -
See used PHP version when using `hypernode-manage-vhosts --list` when alternate PHP versions is enabled
See used PHP version when using
hypernode-manage-vhosts --listfor each vhost when alternate PHP versions is enabled2 votesWe are really thankful for your problem input. Solving this problem aligns with our Product strategy and we have planned to pick the problem up in Q1 2025.
-
Allowlist - updated date
Since allowlisting is not a regular thing it would be good to know when the allowlist rule was added
2 votes -
Restart PM2 after Server Reboot
Restart / resurrect PM2 properly after server Reboot. This should be done by default and not be dependant on a custom cronjob.
2 votes -
Ability to enable horizontal auto scaling on develop nodes
To be able to fully (load) test horizontal auto scaling on a test/accept environment before enabling it for production
1 vote -
Per alert niveau, interne als externe technische ondersteuning attenderen
Blijkbaar is het per 14/7 mogelijk om alerts in te stellen die tevens gemaild worden, een logische feature, graag zie ik dat deze ook per alert een mailadres kunnen krijgen zodat externe technische ondersteuning geïnformeerd kan worden
1 vote -
Garbage Collector
Upon testing Blackfire tool, it was "recomended" to have the garbage collector disable (zend.enable_gc = off)
It would be nice to have a feature to enable/disable this feature
Regards
1 vote -
Keep MySQL minor versions up to date
currently supported MySQL version on Hypernode is 8.0.35
but latest available - 8.0.43, see https://dev.mysql.com/doc/relnotes/mysql/8.0/en/it would be nice to be able to get latest version of the MySQL, so latest performance improvements are available for customers
1 vote -
Horizontal autoscaling compatibility with Fastly (or other CDN's)
Ideally trough comprehensive documentation to use the CDN for load balancing, or a cacheless Varnish implementation, since Magento 2 only supports 1 cacheing application simultaniously
1 vote -
MariaDB support
MariaDB is a faster alternative to MySQL, especially since query caching was removed in MySQL 8
For example, MySQL lacks the following features for optimizing performance:
- optimizerswitch: "rowidfilter=off"
- optimizerusecondition_selectivity: 1So it would make a lot of sense to migrate from MySQL to MariaDB for high-load projects and be up-to-date after MySQL 5.7 was deprecated
1 vote -
Add some more base packages for troubleshooting
Please add support for the following packages for more in depth troubleshooting.
- iftop
- nload
- iotop
If someone has more packages they use for troubleshooting that are not part of the standard install please add a comment.
1 vote -
Add support for Restic and Rclone on all Servers
To create external backups that one can manage themself please install the following packages in the base;
restic
rcloneWith restic we create fast backups to our own repository so we always have a copy of the important data within reach so we don't have to wait long times for a restore from Hypernode.
Also with Rclone it will be possible to backup things to more online services.
1 vote -
Disable access to phpmyadmin by default
When requesting a new Hypernode, phpmyadmin comes pre-installed and is directly accessible via example.hypernode.io/phpmyadmin/ without any whitelisting making it a target for bruteforcing.
We do not use phpmyadmin, meaning that it requires us to disable access to phpmyadmin via nginx for each new hypernode we request. Something that is easily overseen.
For us, ideal is to have its access blocked by default. Even better would be if we can toggle this in the Hypernode panel.
1 vote
- Don't see your idea?