2 years ago
Besides the automatic app sleeping, we sometimes want to manually force instances or whole enviroments to sleep / pause / stop without removing it. So you will not lose all config.
Use-case: using staging environments for projects. Depending on the project, ongoing development on a specific project can be idle for a while. For that period of time you want to shutdown or pause the staging environment (or all instances in it) without losing all configuration. Whenever the development on a project picks up and you need a staging environment again, you want to reactivate it easily.
12 Replies
2 years ago
I would also like it for running a game server but only a few hours of each day
2 years ago
Its not sleeping, but you can simply remove the active deployment via its 3-dot menu.
2 years ago
wouldn't that delete all the persistent data though? which I don't want
2 years ago
oooh awesome. still, a clearer UI would be nice
2 years ago
Yeah, and additionally it is inconvenient when you have an environment with many instances to delete each deployment.
2 years ago
@Brody any chance we could add this to a feature request log? I also think a manual sleep button to keep costs right-sized when testing in dev would be very nice.
2 years ago
+1, would be awesome to have a way to configure sleep/wake in PR environments
2 years ago
It's not manual, but you can enable automatic sleep for services in PR / Staging / Development environment with config as code using environment overwrites.
2 years ago
Thanks as always for the reply brody 
The autosleep is great, but I have lots of services that have frequent outbound traffic. For these, getting them to work with autosleep will be significant engineering work to add special ways to manually shut the services down; it'd be a lot easier if I could have a environment-wide setting to put everything to sleep. Simplest would just be an easy toggle to insta-sleep everything in an environment, but other customization (eg. autosleep after X time of no dashboard/UI activity on a PR environment) would be appreciated too.
a month ago
I think this is a must have to be able to hold the cost down, as we have ton of CMSes that never sleeps because of job checks to the db, so it will never sleep. And these sites dont have visitors at night, so it would be ideal to add a schedule like the auto update function only with sleep/wake. And also an api and manual button in the GUI.
I see that this is a very old request, but i think it is more relevant now then ever.
Is this a difficult feature to achieve?