winsw VS frp

And then set that up as a windows service with WinSw

I am using Windows Service Wrapper to convert some net programs (tor, frp, etc.) into autostart background services. It seems I can choose which user to use when launch these custom services. Coming from a Linux background, I am a little bit confused and overwhelmed by the Windows account and permission systems. I am wondering what's the best practice? Use Local System (probably not, it has very high privileges)? Local Service? Network Service? Or create separate local user account for each service? Ideally I would like to give them minimal permissions (just open and listen a few local ports, connect to the internet, read/write certain local files) and auto start them before logon. Thanks for your advice!

We use a third party library (winsw) to package our exe as a windows-serice

It's been a while since I don't do anything similar, but one of the most popular is NSSM (the Non-Sucking Service Manager) and another open and free alternative would be WinSW (Windows Service Wrapper).

And you look into winsw.

winsw

There are projects which wrap an existing exe file and handle the service stuff for you, for example winsw or DaemonMaster. Another option is to write the service yourself, there's a Go package for that: https://pkg.go.dev/golang.org/x/sys/windows/svc

No idea about RunAsService, but I too have a Dart executable running as a service and I am using WinSW and it runs without issue.

If the program can't run directly as a service itself, you need a wrapper. Back in the day a program called NSSM was popular for this, but it's been unmaintained for many years so now you should use WinSW which is MIT-licensed, modern, actively maintained and easy to use

If you want to self-host, there are many options. For something production ready frp is probably what you want. If you're a developer, I'd recommend starting with my own SirTunnel project and modifying it for your needs. For non-developers and those wanting more of a GUI experience, I created boringproxy. It's my take on a comprehensive tunnel proxy solution. It's in beta but currently solves almost everything I want. Once the server is running this is a very easy tool to use and has some nice features.

Seems to be the exact opposite of https://github.com/fatedier/frp which is a reverse tunnel over a variety of protocols (including HTTP).

I've been self-hosting https://github.com/fatedier/frp on my little box, and it feels insane to think of the times where I didn't have it set up. There are many choices in the space as others pointed out, but frp's capabilities and lightweight packaging blows all other setups out of the water. I placed mine behind nginx with Let's Encrypt for SSL support. Hella fresh!

My setup to do the same:

- small Hetzner instance

- my domain's dns pointing to that instance

- frps[1] running on that instance

- frpc running on my local machine and connected to the cloud frps

[1] https://github.com/fatedier/frp

An easy service to use is FRP, recently found it and it basically handles making the connection out of the network and is really easy to setup. https://github.com/fatedier/frp I personally having it running on a VPS and the client then running on my local network pointing at a reverse proxy which then handles sending it to the diffrent clients.

No, FRP - https://github.com/fatedier/frp

Another way around is to use reverse proxy like frp but since you need SSH anyway, all you need is already comes with SSH (reverse SSH)

Take a look also onto popular, similar to yours project: frp