- Joined
- Dec 28, 2005
- Messages
- 11,460
- Likes received
- 1,218
- Thanks received
- 233
- Location
- European Union (Yorkshire)
Is there any sensible way of doing this:
I have a subversion server working over https that's connected behind a netgear ADSL router. It gets occasional use, by remote and local clients, maybe only once a week for a short time.
Ideally I'd like to set it up so that it can power up in response to a request, and then switch itself back off again after half an hour or so of inactivity.
I did find a way of doing a remote power on before, but it involved connecting over VPN and then using remote desktop to a PC already on on a LAN and running a program to send something over a LAN. All a bit long winded, and in this case the only thing being left on is the router.
I have a subversion server working over https that's connected behind a netgear ADSL router. It gets occasional use, by remote and local clients, maybe only once a week for a short time.
Ideally I'd like to set it up so that it can power up in response to a request, and then switch itself back off again after half an hour or so of inactivity.
I did find a way of doing a remote power on before, but it involved connecting over VPN and then using remote desktop to a PC already on on a LAN and running a program to send something over a LAN. All a bit long winded, and in this case the only thing being left on is the router.