Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Cannot read the CSS - Alpha 2
« Reply #15, on January 6th, 2013, 05:13 PM »
Does nginx support per folder rules specified by a file in that folder? If not, Wedge can't fix it at install time.
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

MultiformeIngegno

  • Posts: 1,337
Re: Cannot read the CSS - Alpha 2
« Reply #16, on January 6th, 2013, 05:52 PM »
With the include parameter there should be a way, maybe a script that checks if that file exist in all the folders, writes in another file all the folders in which this file exist and then rearranging this list of folders to be included in a "location" parameter.
http://wiki.nginx.org/HttpCoreModule#location
http://wiki.nginx.org/CoreModule#include
Posted: January 6th, 2013, 05:51 PM
Quote from Arantor on January 6th, 2013, 05:13 PM
Does nginx support per folder rules specified by a file in that folder? If not, Wedge can't fix it at install time.
Uhm no :(

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Cannot read the CSS - Alpha 2
« Reply #17, on January 6th, 2013, 06:05 PM »
Yup, that's the thing - we use htaccess to do non-standard handling of .gz files on specific types of request. Yes, it's possible to remap that in nginx, I just don't know what configuration you'd need. But we can't deploy per-folder rules in nginx, that's one of the things that makes it faster, it doesn't do the massive hit of folder traversal finding .htaccess files...

MultiformeIngegno

  • Posts: 1,337

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Cannot read the CSS - Alpha 2
« Reply #19, on February 20th, 2013, 12:07 AM »
I should add, after my experimentation in recent times on a shared host, I'm strongly motivated to set this hard-core caching to off (leave parsing etc. running, but not gzipping the files on the server by default)

It was not a particularly exciting test run to start with.