Thanks for your answer. Doing what you suggested does create a new instance for it, but once the instance is up and running it does a redirect to the current version since our app is on facebook.
Joshua Smith wrote: > Deploy the new version. > > Go to the versions panel and launch it directly. > > Change the default version. > > In my experience, that pattern avoids the server error. It still takes > several seconds for all servers to start showing the new version, but you > don't get the 500's. > > On Feb 25, 2011, at 11:53 AM, footy wrote: > > > I was wondering what is the best to manage a new release on App Engine. > > Say for example we have a live version (default) as 1.0.0 and we make > > changes to our code and deploy to a new version as 1.0.1. > > > > When I change the default from 1.0.0 to 1.0.1 it takes GAE to propogate > > changes across the cluster. > > During this period all of our users recieve 'Server Error' > > > > I was wondering how can this managed in a better way. > > 1. Is there a way to have some sort of 'Down for maintenance' page? > > 2. Is there a possibility to control the propogation? > > > > Looking forward to your answers and help. > > Cheers > > > > -- > > 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. -- 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.
