Actually I did have two versions of my application. Both of them went down, including the production version that hadn't been updated in nearly a week. It was never a problem with my code; the problem is quite clearly with google's infrastructure, although I'm willing to be proven wrong.
I uploaded my code (both production and latest) to a new application instance by changing the app.yaml file and it ran perfectly. I pulled out all datastore touches from the code on the broken instance to see if that was the issue, it wasn't. If you look at the stack traces they appear to be happening during module import, not during my application running. I do appreciate the input though, it is good advice. On Sep 2, 8:40 pm, "Brandon N. Wirtz" <[email protected]> wrote: > > Google, how am I supposed to run a business on this platform? > > That is why there is versioning. Upload to one version, test that it works, > push the button to change the default version. > > Always have two copies of your application, so you don't risk corrupting > your live data. > > Make sure you only have one guy with the rights to deploy to your primary > app so that a momentary lapse in Yaml configuration doesn't bork your site. > > "With Great power comes great responsibility" :-) so make sure that when > leveraging the Power of the Goog, you don't break the baby, cause it can be > a real pain if your have 100 megs of application and screw it up, cause it's > kind of slow to put back. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
