Skip to content

Hypernode features

Which Hypernode features would you like to see?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

48 results found

  1. Give hypernode-managed-vhosts --type a option for a webroot'less type

    I would like to have a type that does not have a webroot in the managed vhosts, so I can add a custom proxy that can be used to connect to a podman container.

    For a client where we run a podman container we would like to have a option to give this pod its own subdomain.
    To route this through the server we need a seperate entry in the managed vhosts list.
    Only for this we do not require a webroot.
    And as far as I can see we only have types that contain a webroot.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Allow team management via API

    I would like the ability to assign or remove users from Hypernode teams via API.
    As an agency we have moved to using individual user accounts for every employee. The Hypernode admin currently does not allow assigning one user to multiple Hypernode teams at once, so this takes a lot of manual work to maintain.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Enable AVIF images in PHP

    AVIF is a modern image format, which generate smaller images. In most cases the generated images are smaller and parsed faster than WebP images.

    AVIF can be supported in PHP as part of the GD library, but PHP has to be compiled using the --with-avif option.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Support for OpenSearch

    Because in Magento 2.4.6 the default search engine is OpenSearch it's good to have OpenSearch v2 support

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Easily manage SSH key access

    Allow to easily access SSH key access in the control panel, like the way it used to work in the old control panel.

    Allow for easy enabled/disabling of an SSH key for any Hypernode, without having to remove the key all together. This is sort of possible on the Hypernode itself right now, but this should also be available for non-technical users through the control panel.

    In the old control panel it was possible to just select which SSH keys should have access to which Hypernode and this worked perfectly.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. Mount S3 bucket as a file storage folder with s3fs

    To simplify integration with AWS S3 buckets, it would be very usefull to be able to use s3fs. It allows you to connect your media folders to an S3 bucket without needing any further Magento/Akeneo/etc... platform configurations.

    Example setup https://upcloud.com/resources/tutorials/mount-object-storage-cloud-server-s3fs-fuse

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. Elasticsearch 8

    At the moment Elasticsearch 7 is only supported. To match the latest Magento requirements, please add Elasticsearch 8 support.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Assign multiple teams to one Hypernode

    Where in the past we could ask for the public key and add it to our company account we now invite every developer separately in My.hypernode.com

    Client are owner of the Hypernode, we are owner of our agency.

    We would love to allow multiple teams on one Hypernode.

    This makes on-/off-boarding new co-workers more convenient.

    Currently we need to invite the new co-worker for each team separately.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Install Cronitor by default on hypernodes

    Make sure Cronitor is installed by default. Cronitor is a cronjob monitoring tool. https://cronitor.io/docs/using-cronitor-cli%23installation

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. Add an extra deploy environment (INT/ACC/PRD) - so 3 instead of 2.

    We currently have two environments on your servers.
    Live and Staging. (:8443)

    However, we use three "pipelines":
    - master (Production; live)
    - acceptance ("prelive") (mirror of production environment)
    - integration / Develop (staging)

    1) Please make sure we can easily have that other environment where we can deploy the ACC --> so 3 instead of 1.

    2) The staging is now always running on port :8443.
    Please make it possible to use subdomains instead.
    I suggest:
    - www (production; live)
    - pre-live (acc)
    - staging (int)

    Jos Jonkeren

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. Ability to use latest (managed) Magerun version

    Since https://changelog.hypernode.com/changelog/release-6828-pinning-magerun-2-to-3-2-0/, the n98-magerun2 version has been pinned to 3.2.0. There have been many releases ever since: https://github.com/netz98/n98-magerun2/releases.

    The pindown has been done to make sure n98-mageurn2 can be used on PHP 7.1/Magento 2.2 environments.

    I'd like to tell my Hypernode to use the latest n98-magerun2 version, using hypernode-systemctl. That way, we can have the latest version, while the tool does not break for all PHP 7.1/Magento 2.2 Hypernode environments.

    I know we can install the latest version ourselves in ~/.local/bin, but then we have to:
    1). Keep the tool up to date manually.
    2). Change all paths…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Support for Cloudflare Railgun

    Hypernode is very flexible and powerful with Cloudflare, especially for security, however we would like to use Railgun to improve the performance too.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. Support For Gitlab Runner

    We want to integrate CI/CD into Hypernode using Gitlab.
    With the possibility of installing a gitlab runner directly on the Hypernode we are able to run our integration tests and deploy directly on the Hypernode server with Shell execution

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Allow Google PageSpeed Insights on development-nodes

    During development of a new project, we want to check how Google PageSpeed Insight perceives a yet to go-live environment. Due to the default http authentication the PageSpeed Insights scan cannot be completed. Whitelisting the useragent for Google Pagespeed from http authentication is, apparently, not possible.

    Currently we need to move the Hypernode into production mode before we can run the scan, but that's a bit cumbersome and makes the environment open to the public (while we're still in development phase).

    Ofcourse we can use Google Lightspeed, but this gives us mixed-results. Having the possibility to whitelist the Google PageSpeed…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  16. 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 MySQL

    waarin 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
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  17. See document root when using `hypernode-manage-vhosts --list`

    It would be great to see the document root in the table

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  18. Keep Datadog installation unaffected after system upgrades

    At TechTribe we make use of Datadog for system monitoring. However, after each system upgrade Datadog need to be reinstalled. For our organization, this means that we have to contact the support team, and we cannot access Datadog for a certain period.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. Add an option to manage IP's for a custom allowlist via portal

    Add an option to manage IP's (which are used for the staging environment or the back-end firewall) at the Hypernode portal so our customers could add their own IP addresses.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. Add functionality to specify the return-path for multiple stores, instead of default "noreply@hypernode.io"

    Add functionality to specify the return-path for multiple stores, instead of default "noreply@hypernode.io"

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
2
  • Don't see your idea?

Hypernode features

Categories

Feedback and Knowledge Base

(thinking…)