I probably wasn't clear. latest.myapp.appspot.com always points to the, well, latest deployed *default* version. Say, if you have deployed awesome.myapp.appspot.com and make it default version, then accessing latest.myapp.appspot.com will actually route internally to awesome.myapp.appspot.com anyway. It's like an alias.
On Sun, Sep 23, 2012 at 8:43 PM, alex <[email protected]> wrote: > Upload a new version, e.g. "mynewawesomeversion" and set the default > to that so that users will access your app at myapp.appspot.com (or a > custom domain) and not latest.myapp.appspot.com. It's the best > approach, I believe. "latest" has a special meaning for app versions > routing. > > If you have some changes that you can't make backward compatible with > mobile client, you could always do something like > myapp.appspot.com/v1/... and /v2/... I believe it's much better than > making your mobile client connect to a specific version-based > subdomain. > > -- alex > > On Sun, Sep 23, 2012 at 8:28 PM, Iaco86 <[email protected]> wrote: >> I can't do that, since i need to update the version that is called *latest*. >> If i try doing that, by setting the version to *latest* in my yaml file, >> even if the version *latest* already exists, the server replies i can't have >> a version called *latest*. >> >> Moreover the default version (version called *1*) serves an older version of >> my app that still has a couple of users. >> >> On Sunday, September 23, 2012 8:20:46 PM UTC+2, alex wrote: >>> >>> You can always set the *default* to whatever version you have >>> deployed. What's wrong with that? >>> >>> >>> On Sun, Sep 23, 2012 at 7:52 PM, Iaco86 <[email protected]> wrote: >>> > Hi everyone, >>> > I have a version of my python appengine server that is named "latest". >>> > This >>> > is the version used by the web applications that interface with the >>> > service. >>> > >>> > Now it looks like I can't update anymore the version, since Google >>> > suddently >>> > decided that "latest" is not a valid version name anymore... >>> > Can anyone tell me why? Since I use the server for a mobile app, I will >>> > have >>> > a 10 days blackout on my app, since the server is not working anymore >>> > and i >>> > can't update it anymore. >>> > I will therefore have to deploy a new version of the server, with a >>> > different name, deploy a new version of my mobile application and wait >>> > for >>> > it to be certified. >>> > >>> > Why couldn't google allow the version name anymore????? It is causing a >>> > major hassle + lot of negative votes on the market.... >>> > >>> > Thanks for replies. >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups >>> > "Google App Engine" group. >>> > To view this discussion on the web visit >>> > https://groups.google.com/d/msg/google-appengine/-/33FIcnJG7YkJ. >>> > 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 view this discussion on the web visit >> https://groups.google.com/d/msg/google-appengine/-/MFxAzMjD3dkJ. >> 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.
