https://bugzilla.wikimedia.org/show_bug.cgi?id=363

Aaron Schulz <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |[email protected]
         Resolution|---                         |WONTFIX

--- Comment #7 from Aaron Schulz <[email protected]> ---
This is pretty much a performance anti-pattern. If someone really wants it they
could make a DBFileBackend subclass of FileBackendStore and point
$wgLocalFileRepo at it (via the 'backend' field).

(In reply to Brion Vibber from comment #0)
> Although there are good reasons to use the filesystem for uploaded files,
> there are also problems with it in 
> some situations:
> 
> * Security -- world-writable directories on multi-user hosts
> * Security -- dangerous filetypes may slip through and execute scripts
> server-side
> * Inconvenient filesystem naming limitations (eg bug 362)
> * Stupid configurations -- PHP 'safe mode' and other such things that may
> make it difficult for some 
> installations to have a writable directory tree for uploads

Since this report was filed, it is possible to use other backends like S3,
Azure, Ceph, Swift, Gluster (Swift compat code). This handles 1 and 3-4.

https://gerrit.wikimedia.org/r/#/c/125573/ is able to handle encoding issues
(3). https://gerrit.wikimedia.org/r/#/c/127460/ could also handle long names.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to