Symfony currently has these Apache-writable folders in a standard setup:

web/uploads
cache
log

web/uploads is in webspace where users could access it directly, like it or not.
cache is managed by 'symfony cc'.
And log is for log files and is subject to rotation etc.

What symfony does not have is a folder for data files that are written
to by the web server dynamically as needed and are NOT meant to be web
accessible by the user.

Before you say "you should always use the database for that," please consider:

Zend search indexes (which are files, not in a SQL database, and are
used by Jobeet etc)
Large as-yet-unapproved uploads (simulated persistence for upload
fields - pkPersistentFileUploadPlugin)
Temporary files guaranteed to be rename-able into not-so-temporary
folders also in Symfony space (system tempdirs often useless for this)
Large blobs that a particular database does not handle well

(Using the database for everything, no matter what, is a religious
debate but it's clear that there are times and places where we are
stuck putting certain kinds of data in files, even if we would rather
not. So hopefully we can set that debate aside.)

For our own plugins we used to have a dangerously growing collection
of separate writable folders. We thought it through and consolidated
them like this:

web/uploads: everything apache-writable that should be directly web
accessible (Symfony standard)
data/pk_writable: everything apache-writable that should NOT be
directly web accessible

My recommendation is that an sf_writabledata_dir key and a
corresponding default data/writable dir be added to Symfony as
"standard equipment." This will allow others to avoid going through
the same gymnastics. Also, the project:permissions task would then
take care of chmodding it.

-- 
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
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/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to