+1 for app.example.yaml if it weren't for source control i would have been
SOL a crap-ton of times. :)
On Mar 8, 2011, at 7:35 PM, Richard Baron Penman wrote:
> yes also worked for me.
>
> People will need to change the application name, so should this be included
> in app.yaml but commented out?
I think that app.yaml needs to become app.example.yaml (along the lines of
routes.example.py and log
yes also worked for me.
People will need to change the application name, so should this be included
in app.yaml but commented out?
On Wed, Mar 9, 2011 at 2:03 PM, Jonathan Lundell wrote:
> On Mar 8, 2011, at 6:36 PM, Plumo wrote:
> > thanks John, that makes sense.
>
> I tested it on the stock
On Mar 8, 2011, at 6:36 PM, Plumo wrote:
> thanks John, that makes sense.
I tested it on the stock welcome app, and it seems to work fine. I'll send
Massimo a patch for the example app.yaml, since this is a fairly common
requirement.
thanks John, that makes sense.
On Mar 7, 2011, at 11:33 PM, Plumo wrote:
> I have the following listing in routes:
> ('/robots.txt', '/cms/static/robots.txt')
>
> This lets me access /robots.txt on my local computer, but returns "invalid
> request" when I upload this to GAE. Are there meant to be any differences
> when using
6 matches
Mail list logo