🚀 [Release] GLKVM-Cloud: A Lightweight Self-Hosted KVM Remote Cloud Platform

[clannad]

We are sorry that this use case is currently rare and not supported yet.
We’ll consider adding support in future updates if there is more user demand.

[clannad]

@kjb

Correct, I can use a subdomain. My concern is the need to use *.example.com. I want unknown subdomains to go to a dedicated ‘unknown’ page and not the KVM cloud plattform.

Thank you for showing the version now.

@kjb The issue has now been resolved in v1.8.0. Release details: https://github.com/gl-inet/glkvm-cloud/releases/tag/v1.8.0

[kjb]

Good work, thank you for actively developing the self-host part.

In the .env example File for docker compose, the line with «GLKVM access IP seen by devices/users.» should be commented out.

Also, it would be nice to be able to sort the new column «Associated Device Group»

[clannad]

@kjb

Good work, thank you for actively developing the self-host part.

In the .env example File for docker compose, the line with «GLKVM access IP seen by devices/users.» should be commented out.

Also, it would be nice to be able to sort the new column «Associated Device Grou

Thanks for your suggestion. We welcome valuable feedback from our users, and we will do our best to include them in future releases.

[clannad]

@kjb

In the .env example File for docker compose, the line with «GLKVM access IP seen by devices/users.» should be commented out.

Also, it would be nice to be able to sort the new column «Associated Device Group»

you can try this feature in v2.4.0

[esysky]

Hello,

We’ve been using the comet pro on our repair bench since December, and I’m really liking the direction the self hosted platform is going. Would it be possible to request a few features for the next release?

1. Ability to have multiple kvm sessions open in browser tabs. Currently opening a second tab to a different device through the platform causes both tabs to display the second sessions kvm.
2. Display the comet pro’s hostname or description from the platform on its opened tab?
3. When connecting to a session I’m prompted to supply the comet pro’s password. Would it be possible to store this password for the group of comets in the platform so the user can just click through to the session? I can use ldap to control what groups our tech’s are assigned so the extra password is a bit of a hassle.
4. Possibly have a way to batch upgrade firmware for all devices in a group?

Looking forward to the next update!

[clannad]

Hello,

1. For the first three requests, they sound reasonable, but may require some bigger changes to the current session handling, so we probably won’t work on them in the short term. If more users ask for the same features, we’ll consider adding them in a future release.
2. For batch firmware upgrades, the self-hosted cloud already supports batch device operations, but it’s still quite basic and currently requires running shell commands manually. We can consider wrapping this into a more user-friendly firmware upgrade feature.