I just want to purchase software these days. Not another subscription.
Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
11–20 of 84 posts
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#12Why are we still using Java for these kinds of solutions today?
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#13Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#14I'm particularly interested in this "field". I've build something similar many moons ago [1], in the same spirit, but much more primitive. I later started a company around an evolved idea, where the structure you sort of see in your screenshots is effectively a DAG with arbitrary depth (we didn't manage to release it unfortunately, complexity overtook us).
In any case, much congratulations + good luck with the launch!
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#15Your website is really cool.
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#16/me blinks. An OS is an OS... so, access to developer licenses for these are Professional use too?
> connections to those systems are only possible starting from the homelab plan: Oracle Linux systems
/me blinks even more ...
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#17I'm a freelancer working with different clients with a mix of the technologies you listed (Docker/Kubernetes) and I'm using Tailscale for mostly personal use-cases, so this hits all the right spots.
Up until now I proxied most of my stuff on a macOS client via "SSH Tunnel Manager", which has quite a clunky UI, and whenever I have to reconfigure something there the current feedback of the current connection state isn't always right. I just moved all those settings to XPipe, and it works like a charm.
Previously I also used the same solution for accessing some internal websites via a combination of the SSH tunnels + /etc/hosts entries + header rewrites, which depending on the complexity of the websites sometimes works great and sometimes doesn't at all. With XPipe I was easily able to set up a SOCKS proxy, which I previously gave up on trying to figure out. Paired that with FoxyProxy on Firefox and now all the websites work like a charm!
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#18Hey, I just wanted to congratulate you with a very impressive release, the software looks amazing, and I think I will give it a try pretty soon. A question: I see only subscription pricing; is a lifetime licence possible, or a licence like the way jetbrains does it (you pay for version, and maintain the right to keep using the version that was available when the license/subscrition expires, you can re-activate any ti…
It's cool to see that there are also other people in that space. And about the complexity, I definitely know what you mean. It took a long while before this approach even worked and also took a while until it was actually stable. One of the main points of consideration whenever I think of adding something is the added complexity, because it's very important for me to keep that as low as possible. Otherwise I will end up with an unmaintainable workload. There were definitely a few interesting features I discarded to keep the application as lean as possible.
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#19Why are we still using Java for these kinds of solutions today?
Can you elaborate on that? Then I can better respond to your specific points on why it shouldn't be used
I believe Java is no longer an appealing choice for these types of tools, but I still like the project and its development process.
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#20> connections to those systems are only possible starting from the professional plan: Red Hat Enterprise Linux systems, etc /me blinks. An OS is an OS... so, access to developer licenses for these are Professional use too? > connections to those systems are only possible starting from the homelab plan: Oracle Linux systems /me blinks even more ...