> > I was thinking that there seems to be instances when images would be > served from outside of the static directory, like an app's custom upload > directory, dynamically generated imagery similar to those you'd get from > PHP's GD or Imagick libraries, etc. I can think of circumstances where > those might not be best stored in the static directory. Perhaps two static > location blocks would be beneficial. One to cover the whole static folder > and one to cover any static file types you may find yourself wanting to > store outside of the static directory.
it's quite unclear why should you do such a thing by default with web2py, given usually everything that is not /application/static/ is a dynamic page. Uploads dirs are for files that need to go through web2py's auth system (so, no nginx serving). That being said, you're free to edit your own config to match your particular url scheme, but it's clearly not something "universally" valid. It looks like the zip_static_files.py script only gzips css and js files. > There's a lot more that can be compressed, such as web fonts and vector > graphics. I understand why jpg and png images are left out, but why only > css and js? > > because as anything in web2py there's a sane default. you can tune as you wish. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
