How to manually stop the clock on Starter plan usage?
I've read some posts that say we can manually remove the latest deployment and it should stop the hours usage on the starter plan. Can anyone please elaborate exactly what to do?
I tried removing the latest deployment for both my app and DB backup cron job. (I don't see any option to remove the DB itself.)
When I checked back a few hours later I could see that my usage allotment was still going down.
How can I make sure I'm stopping the clock?
9 Replies
Project ID:
83791c3c-35a4-439c-96ea-34c41b9aed33
83791c3c-35a4-439c-96ea-34c41b9aed33
Maybe I have to remove all previous deploys, not just the latest? Trying that now and we'll see if it works...
any service presence will keep the hours being used
Unfortunately since you have still have a db active, your hours won't stop going down unless you remove the db.
Ah that's too bad. It would be great to have an option to easily put all services to sleep and stop using hours. I know there isn't an automated sleep like other services but still it would be great to have a manual option that doesn't require removing the entire DB!
Agreed, you could always upgrade to the dev plan
The free plan is more of a trial plan than a legitimate production-facing option. If you need 24/7 operation, upgrade
Yes the whole reason I want to be able to turn it on and off is because it's not yet a production-facing app. I want it to be in a trial mode while I'm working on it, meaning not up 24/7. But the way the trial plan is currently structured it makes it really difficult because I basically can't work on it for 10 days out of the month...
It would be a more attractive trial option if I had an easy way to be in development during the work days but not up 24/7. If I could manually shut it down in an easier way or automatically sleep that would serve my use case much better.
The free plan isn't meant to be a development plan, which is what you seem to be looking for. That would be the Developer plan.
The free plan is a trial, meant for you to test out the service. Not develop your projects and only pay when they are production ready
Got it, thanks for the explanation of the reasoning