ianlivingstone
commented
6 years ago We looked into running Torus as a service; while it's a good option for a server deployment scenario it didn't fit well with the "local development" story we've been focusing on w.r.t. to the initial windows support.
Perhaps in future we can enable installing Torus as a service through choco or as an argument?
Windows, like many operating systems, offer a robust service model for starting, stopping, and restarting long running back ground processes such as the Torus Daemon.
It would be awesome if Torus could be registered as a service during install (#212). However, one thing for us to sort out is how this would work on a per-user basis (to copy the security model that we use in *nix of tying the socket to the current user/group).
Another thing to consider is how this would work in a Windows Server environment where you'd most likely want to run Torus as a machine wide service similar to the default setup we have on Debian/Ubuntu and RHEL/CentOS with our yum/apt packages via systemd.