I would like to submit a new feature request. Currently, the Sandbox stack_manager has the ability to be Stopped/Started/Reboot from the Windows Tray. This makes it really easy for me to remote administer an a simple instance without the need for command-line ninja-fu. (better to have it and not need it, than to need it and not have it… )
The system expectations of Interface are quite high. My solution to allow new team members the ability to test things within interface is to allow them to remotely access a very high-end machine. To do this; interface must be started on-site prior to their engagement. Most of you that have suffered through 2014-15 alpha years already see where this is going.
So what happens if the interface crashes? (it does still happen btw…)
Well, the current solution is it needs to be restarted in Windows somehow…
But what if the Stack_Manager could reboot Interface on my behalf ???
I can’t make it into the Friday meetups anymore to share my little suggestions so I’m putting this one here. I need a way to Reboot Interface such that if a remote user of interface closes or crashes, it can startup on it’s own without failing due to Remote Desktop graphics. (anyone that has attempted to run Substance Designer or Interface remotely knows exactly what I’m talking about)
Any other recommendations welcome, @OmegaHeron, @Cracker.Hax, @Menithal possibly a windows service could be authored that simply sniffs the status and reboots if needed? Could this be a Windows problem that is currently unsolvable?