dev-appserver-2

To access a remote datastore locally using the original dev_appserver I would set --default_partition=s as mentioned here In March 2013 Google made devappserver2 the default development server, and it does not support --default_partition resulting in the original, dreaded: BadRequestError: app s~appname cannot access app dev~appname's data It appears like the first few requests are served correctly with os.environ["APPLICATION_ID"] == 's~appname' Then a subsequent request results in a call to /_ah/warmup and then os.environ["APPLICATION_ID"] == 'dev~appname' The docs specifically mention

I have an application which has rest end point and web end point. I want to run both REST and WEB service locally using dev_appserver.py I have tried the following dev_appserver.py rest_app.yaml --port=5010 --admin_port=8000 dev_appserver.py web_app.yaml --port=5011 --admin_port=8001 I see the following error on one of my services (rest service) `OperationalError: database is locked` Do I have to do anything special to make sure both those services can read/write to a shared database without any conditions (or similar bad things !!) My goal is to run multiple services (rest and web in this

I'm developing a Google App Engine application and I am encountering references to both an App Engine SDK and a Cloud SDK . How do these two SDKs relate to each other? There is definitely some overlap between the two. There is a dev_appserver.py and appcfg.py is both of them. I can run a development server using dev_appserver.py , and also with gcloud preview app run . Why are there two tools that do the same thing? Is one being deprecated in favor of the other? Is there a roadmap for merging the toolsets, or are they going to be maintained in parallel? Do I need both, or just one? It seems