[RFC|Merged] No db storage of stylesheets and templates

These requests for comments/change have lead to an implemented feature that has been successfully merged into the 3.1/Ascraeus branch. Everything listed in this forum will be available in phpBB 3.1.
User avatar
naim
Registered User
Posts: 50
Joined: Thu Oct 13, 2011 7:21 pm
Location: Isolation
Contact:

Re: [RFC|Merged] No db storage of stylesheets and templates

Post by naim » Fri Oct 14, 2011 6:47 am

Storing "compiled" style-sheets in the cache is a good idea,
but letting the client to load a few files just increases the load on the server (why make 7 requests when you can make only 1?)
and +1 to VSE+!

When "Compiling" style-sheets, can we add an optimizer to remove unneeded characters? (white-spaces, etc..)

Oleg
Posts: 1150
Joined: Tue Feb 23, 2010 2:38 am
Contact:

Re: [RFC|Merged] No db storage of stylesheets and templates

Post by Oleg » Fri Oct 21, 2011 2:50 am

Currently cache does not have any files that need to be served by the web server, and it is therefore possible to prevent web server from reading the cache directory. Putting assets in cache will also potentially expose other files in cache, e.g. the mail queue, to the web.

User avatar
naim
Registered User
Posts: 50
Joined: Thu Oct 13, 2011 7:21 pm
Location: Isolation
Contact:

Re: [RFC|Merged] No db storage of stylesheets and templates

Post by naim » Fri Aug 24, 2012 3:35 pm

Oleg wrote:Currently cache does not have any files that need to be served by the web server, and it is therefore possible to prevent web server from reading the cache directory. Putting assets in cache will also potentially expose other files in cache, e.g. the mail queue, to the web.
So make 2 cache directories, one with public access and the other with .htaccess or Web.config block (or outside install directory).

User avatar
callumacrae
Infrastructure Team
Infrastructure Team
Posts: 1046
Joined: Tue Apr 27, 2010 9:37 am
Location: England
Contact:

Re: [RFC|Merged] No db storage of stylesheets and templates

Post by callumacrae » Fri Aug 24, 2012 6:48 pm

naim wrote:
Oleg wrote:Currently cache does not have any files that need to be served by the web server, and it is therefore possible to prevent web server from reading the cache directory. Putting assets in cache will also potentially expose other files in cache, e.g. the mail queue, to the web.
So make 2 cache directories, one with public access and the other with .htaccess or Web.config block (or outside install directory).
It would probably need to be more assets/generated than a cache-public, in my opinion.
Made by developers, for developers!
My blog

Post Reply