While working with caching, I noticed what seems to me like a caveat in
web2py's current design.
When serving static files from the webserver, you can either :
- use the "static" pseudo-controller (it's actually a route built directly
above the WSGI), in which case you can't set your own cachin
speaking about optimization , here is my homework
https://github.com/ramstein74/Coffee_Jade_Stylus_inside_web2py
2015-09-14 15:11 GMT+01:00 Louis Amon :
> Indeed I should look into contributing the book at some point. Still feel
> a bit too noobish for that just yet ^^
>
> As for Heroku & Gzip, h
Indeed I should look into contributing the book at some point. Still feel a
bit too noobish for that just yet ^^
As for Heroku & Gzip, here's the official source to my info:
https://devcenter.heroku.com/articles/http-routing#gzipped-responses
On Monday, September 14, 2015 at 5:26:07 AM UTC+2, Ki
Hi Louis, good tutorial. I usually try serve my static (and uploaded)
files directly, without pass for the web2py layer.
About the gzip, maybe this Stackoverflow threads can help:
http://stackoverflow.com/questions/8506897/how-do-i-gzip-compress-a-string-in-python
http://stackoverflow.com/quest
Louis,
Thanks for putting this together. There are a bunch of performance tips
in the web2py book too. Wondering if your compilation can find a home
there. Also, in another thread, you had mentioned about Heroku
deployments, and how it requires the web application to perform
compression of ass
5 matches
Mail list logo
