you could minimize your expenses by having a cron task at those times respectively turning OFF and then turning back on some FLAG. Then if you have all your requests go through a filter, the first thing it should do is check for this flag to see if it's on or not. If it isn't, stop execution and return a "app not in service" page or something similar. This won't totally stop billing, but should reduce the cost if you implement it well.
Tristan On May 7, 6:36 am, Tim Hoffman <[email protected]> wrote: > Nope > > Why don't you check the time on access and redirect to a static or > simple page when out of the operational times > > T > > On May 6, 4:56 pm, kyle <[email protected]> wrote: > > > Hi, > > > Is it possible to set the up / down time of apps? For example, I would > > like my app start service at 2200 and down at 0100 everyday > > automatically so that I can avoid my billed quota being run out during > > my "non-service" time. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
