[google-appengine] Re: app.yaml not being recognized by my app

Hi David, Dev app server was previously used to test your application on local environment replicating the App Engine First Generation’s behavior however as GO 1.11 is now running on the Second Generation there is no need

[google-appengine] Re: app.yaml not being recognized by my app

I didn't have 'api_version' in the app.yaml. I don't think the app.yaml was being read at all. With Go 1.11, what is the correct way to start the app locally? Is it 'go run .', or is it 'goapp serve'? 'goapp serve' isn't working for me on Windows, because I have a space in my path: > "\User

[google-appengine] Re: app.yaml not being recognized by my app

Hi David, The reason it does not work for runtime go111 is because 'api_version' is not a supported element for Go 1.11. For full list of supported elements for Go 1.11 click here . The supported el

[google-appengine] Re: app.yaml not being recognized by my app

If I modify the app.yaml like this: #runtime: go111 runtime: go api_version: go1 then I can run "dev_appserver.py ./app.yaml", and I can see my static content. I don't know why runtime:go111 doesn't work, but I suppose this works for now. Thanks again! David On Wednesday, January 16, 2019

[google-appengine] Re: app.yaml not being recognized by my app

Hi George, Thanks for the help. I did find the documentation on serving static content, but I think there's something more basic that I'm missing. If I delete app.yaml from the directory entirely, then I don't see any errors--just the same behavior. My directory looks like this: src/myapp/ap

[google-appengine] Re: app.yaml not being recognized by my app

Hello David, What is your app's directory structure? What directory were you in, when running go run? What happens if you run dev_appserver.py app.yaml in the directory where your app.yaml resides? Is it ignored as well? You may refer to the "Serving Static Content" documentation page