Repository navigation
Support App Engine local server #104
Description
Activity
- added this to the milestone
on Aug 8, 2014 b/16902970 and b/16906501
And b/17065187.
Blockers are resolved.
Our strategy:
If project ID and credentials are set, use them.
Otherwise,
- If GAE_VM is set, this is GAE prod. See GAE_LONG_APP_ID for project ID.
- Else, this is GAE dev. Skip authorization. (You don't need a project ID.)
- modified the milestones: ,
on Oct 1, 2014 - changed the title
[-]datastore: Support App Engine local server[/-][+]Support App Engine local server[/+]on Jan 20, 2015 Possibly related to https://github.com/GoogleCloudPlatform/gcloud-meta/issues/4
Out of curiosity, how would this work? Would you have to run
gcloud preview app run .; meaning you can't easily make use of tooling such as nodemon? Is there a way to run a local dev datastore instance by itself, without having to buy into the (a little bit too prescriptive)gcloud preview app run .thing?"Should be able to talk to a Datastore local development server."
83 remaining items
- added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 17, 2026 - added a commit that references this issue
on Mar 5, 2026 - added a commit that references this issue
on Mar 17, 2026
If user is running this client library from GAE context locally, we should turn authorization off and use local server for Datastore operations.