Skip to content

Hypernode features

8 results found

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Ability to rename SSH Keys

    Ability to rename SSH Keys without removing the key and add it again.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Add existing Hypernodes to existing Teams of which I'm an admin

    Make it possible to add existing Hypernodes of which I am admin to an existing team. Right now I only see Hypernodes of which I am an owner, so the Teams structure is now all over the place and I can't make sense of it.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Add more history to MageReport charts

    At the moment, the MageReport charts only go back 7 days. When troubleshooting problems, it's often required to go back further in time.
    Disk space, CPU usage, PHP requests, ...

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Hypernode features

Categories

Feedback and Knowledge Base