BaGet VS winsw

As others have mentioned, you want NuGet. However, beyond the directory approach that was already mentioned, people may be interested to know that you can also do a web hosted version or if you prefer you can use the full NuGet Gallery project that powers nuget.org. At this point there's like 20 different ways to do it now. Hanselman had a list of some options a while back. BaGet is kind of interesting on that list.

Yeah I know all this, you can even use BaGet[1] symbol server to cache or manage private dependencies in an enterprise network. That is not the point... I think that the most used tool / platform should provide more flexibility for non-enterprise or less expierienced developers.

No offense, I like nuget, but I recently made a typo and checked in 0.0.23 instead of 0.0.2. Now, everytime I add a dependency that is < 0.0.23 to a project, that has not been synchronized / validated yet (the other problem I described), it automatically takes the best match, which is 0.0.23 assuming to be the newest package, even if unlisted.

I also burned a 1.0.0 because of a failing script like that... not really bad, but annoying...

https://github.com/loic-sharma/BaGet

NuGet server - BaGet (https://github.com/loic-sharma/BaGet)

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

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.

We use https://github.com/winsw/winsw without any problems for years.