Hacker News Reader

Comment by afeiszli | Hacker News Reader

I think you'll be happy with the Enterprise version based on your list, we've had very similar thoughts. One question on the final point, where do you see the need to install the server on Windows? We've had one other user ask for this, but not sure if I see the need.

View on HN

Company uses Windows exclusively and there are no in-house Linux ops/admin skills. We have good ops/admins resources for Windows and we need to leverage that. A native solution (even if running behind Apache/Nginx) is preferable. In addition this would be a critical part of the infrastructure so we would want that piece to be somewhat familiar to the ops/admin resources for debugging (access the box, restart a service, troubleshoot networking issues, etc).

Edit: This is a requirement for self-hosted but if your enterprise solutions offers it as a highly available service that would by-pass this issue. It would need to be HA and spread in such a way that a single cloud provider going down does not affect things.

I think until we get more users requesting this, it will probably stick on the back burner for some time. We've designed several server components assuming it's deployed on Linux, and it's streamlined for containers. However, if there's an org interested in pursing this (and has some golang + ops skills) it should be do-able with a bit of effort, and we can provide some advice. It might make for a good community project.

> One question on the final point, where do you see the need to install the server on Windows?

Can any client be an egress node?

Currently just Linux machines can be egress nodes.

What is an 'egress node'?

An exit node; if node a is an exit node, node b can route its traffic through a - which among other things can allow access to resources whitelisted to node a's public ip from b.

Reply on news.ycombinator.com