Converting ACE to run as a Windows service

[mcreedjr]

Envisioning how this server will eventually be run and/or deployed, I suspect that most would like the opportunity to have the server run as a Windows service. This will allow automated starting of ACE at Windows startup. This will require a separate monitoring application to monitor any "console" output. I offer this only from a sysadmin point of view who has an aversion to having to interactively start applications which others use. I'm not sure what architectural changes will be required, but thought it would be worth mentioning early in the development process.

[firesickle]

As an alternative, You can run it in its current state with a scheduled task, which I think you can set up to execute upon start up. Additionally, you can set a scheduled task to run again if it is not already running, to get the client to start back up if it threw an exception and ended. Not sure myself what extra steps would need to make this into a service. In my past experience, I have had never-ending problems with custom built windows services that do web interactions, had a lot more success when switching to scheduled tasks

[Mogwai-TheFurry]

Windows services are a real pain for development. This won't need to be done for a really long time.

[Mag-nus]

We discussed this at length on Discord in October.

May chimed in with feedback, and the result was that running ACE as a windows service opened up a lot of exploit risk.

ddevec: Anon's opinions are consistent with 99.99% of the security experts you'll ever meet, and ACE should likely follow teh principal of least-privilege. If you want autostart, make a dedicated and small privileged piece of code to do it, don't increase the privilege of teh entire codebase.

Closing this as it's not something we're visiting right now.