It's better for you to use python27 since it is multithreaded. That's means
an instance can handle more than one request simustaneously. Also increase
"default_expiration" when you be ready to deploy to the public your
website. default_expiration: "7d" (7 days) is a good value.
On Tuesday, June 19, 2012 3:48:10 AM UTC-6, Apra Barua wrote:
>
> Hey, I got it to work, it is not creating instance now. Thanks. The
> following app.yaml file worked.
>
> application: myappname
> version: 1
> runtime: python
> api_version: 1
>
> default_expiration: "12m"
>
> handlers:
> - url: /(.*\.(gif|png|jpg|ico|js|css|pdf|html))
> static_files: \1
> upload: (.*\.(gif|png|jpg|ico|js|css|pdf|html))
>
> - url: /
> static_files: index.html
> upload: index.html
>
>
> On Monday, June 18, 2012 10:08:32 PM UTC+5:30, Kyle Finley wrote:
>>
>> Have you mapped the root ('/') to a template? If so, App Engine will have
>> to start an instance to handle this request. Also any request that are not
>> specified in the app.yaml file will be sent to the instance causing it to
>> start up. Be sure to account map the *favicon.icon* for example.
>>
>> Generally I would not worry about it consuming frontend instance hours
>> unless your site is geting more then 1 or 2 request / sec. App Engine
>> graciously gives you 28hrs / day more then enough to fulfill 1 to 2 request
>> / sec.
>>
>> If you still have questions post your app.yaml file so we'll have a
>> better idea of your set up.
>>
>> - Kyle
>>
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/5sR8SAHUfGoJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
