Don't charge for sites that are stopped
When a site is created, but in a "stopped" state, don't charge for that site. This would be beneficial for the following situations:
1) A user creates a site for testing and experimentation purposes but only wants to use it when actively working on it. The user stops the site and the resources get de-allocated so the user is not charged.
2) A user creates a secondary site to use as a staging area to ensure the code functions properly on GearHost prior to publishing it to the production site. After verification, the user stops the staging site and is not charged until it is needed again, and started.
damccull
shared this idea
-
I believe this is resolved with a new feature we're coming out with called Deployment Slots which will allow you to have multiple deployed sites that you can toggle as live without missing a beat. Regardless however when a site is stopped doesn't mean it's resources are deleted. We're still having to keep disk, cpu, memory, netowork, etc all allocated for your site so you can start it up at a moments notice. As such since a site is still using resources in an offline state (albeit not as much as when active) it cannot be set to free. Sorry about that however thank you very much for your suggestion!
-
Hrvoje Grabušić
commented
So instead of stoping it you switch it to free mode and then it will be suspended and it wont charge you anything then switch back to shared when you work on it.
