Turns out, in order to create and configure a backend, its not sufficient to just add it in the backends.yaml file and deploy the app. I had to run this appcfg command to create the backend:
appcfg.py backends <location of app.yaml> update <backend name in backends.yaml> On Fri, Sep 9, 2011 at 2:20 PM, Rishi Arora <[email protected]>wrote: > 1. Configuration: When I add my first backend for the first time, and > introduce the backends.yaml file for the first time, is it important that > the associated version in the app.yaml file be the currently active version? > > 2. Addressing: I know of three ways of addressing backends: > a) an HTTP Get/Put request to https://[backend name].[appID]. > appspot.com/[path <http://appspot.com/%5Bpath> to any RequestHandler > defined in app.yaml] (as long as the request is from an admin when the > backend is private) > b) a taskqueue.add() with URL = [path to any RequestHandler defined in > app.yaml], and target=https://[backend name].[appID].appspot.com > c) a crob job defined in cron.yaml, with a fully qualitified > url=https://[backend > name].[appID].appspot.com/[path <http://appspot.com/%5Bpath> to any > RequestHandler defined in app.yaml] > > Am I correct about these alternatives? I'm assuming only a single backend > instance (specified in backends.yaml), so I have ommitted the [instance] > from any URLs above. Also, as long as my app is using one of the above 3 > alternatives, am I assured that my backend won't get started by any other > means? I don't want my backend running in-advertently, because it costs > money, and the new pricing scheme is forcing me (in a good way) to treat > these resources as precious :) > > Thanks in advance. > -Rishi > > -- 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.
