It should be created by dev_appserver when you run the queries. Each
query will add to the file the index it needs.

On Mar 17, 3:44 pm, Richard <rco...@rm-digital.net> wrote:
> Thanks for responding. I seem to have data persistence now whether I
> use the datastore_path parameter or not (!?)
>
> However, I still can't get the index.yaml generated. I have tried
> creating an index.yaml as described and put this in my ../web2py
> folder where the app.yaml and queue.yaml files already exist. Although
> the modified time stamp gets updated when I run the dev_appserver the
> contents don't change. I have tried adding new entries into my
> database to trigger some kind of change but still no joy.  Deleting
> the index.yaml again doesn't result in this be re-created either.
>
> The web2py book says: "index.yaml is created automatically by the
> Google deployment software."  Am I mis-understanding this, should it
> be created when I run the dev_appserver in the SDK, or is this
> generated by some other process?
>
> Also, I'm using Ctrl+C to stop the dev_appserver, is this okay?
>
> Thanks.
>
> On Mar 16, 11:17 pm, howesc <how...@umich.edu> wrote:
>
>
>
>
>
>
>
> > Richard, implies that this file will be created automatically by the GAE
>
> > by default GAE dev_appserver saves the datastore in temp by default.  this
> > will tend to get deleted by the OS.  I run my dev_appserver with the
> > --datastore_path parameter and pointing to a spot where i can be sure the
> > file is not deleted.
>
> > check that your index.yaml starts like:
>
> > indexes:
>
> > # AUTOGENERATED
>
> > # This index.yaml is automatically updated whenever the dev_appserver
> > # detects that a new type of query is run.  If you want to manage the
> > # index.yaml file manually, remove the above marker line (the line
> > # saying "# AUTOGENERATED").  If you want to manage some indexes
> > # manually, move them above the marker line.  The index.yaml file is
> > # automatically uploaded to the admin console when you next deploy
> > # your application using appcfg.py.
>
> > if not GAE gets confused and does not update the index.yaml file.  you might
> > get it to work just be deleting the index.yaml file and seeing if GAE
> > re-creates it.
>
> > good luck!  once it is working it is quite nice.
>
> > cfh

Reply via email to