Filebrowser doesn't respect the FILEBROWSER_MEDIA_ROOT setting about django-filebrowser HOT 3 CLOSED

that´s a misunderstanding (probably the documentation is not clear enough):

FILEBROWSER_MEDIA_ROOT: basically the same as djangos MEDIA_ROOT (definition-wise).
FILEBROWSER_DIRECTORY: folder withhin MEDIA_ROOT

it´s good to save "uploads" with the filebrowsefield, because when you need to serve your media, "uploads" is not within djangos MEDIA_ROOT and therefore needs to be saved to the database.

from django-filebrowser.

Then there is no point of having FILEBROWSER_MEDIA_ROOT setting if it can't be changed.

It's good to keep "uploads" out of database if

FILEBROWSER_MEDIA_URL = "/uploads/"

or

FILEBROWSER_MEDIA_URL = "http://uploads.example.com/"

from django-filebrowser.

The commit above adresses this issue. You can now set FILEBROWSER_MEDIA_ROOT in order to browse files from a path different from Django's MEDIA_ROOT.

However, the preferred way to customize FB's media root and media url is to set these parameters on a custom storage object (see http://readthedocs.org/docs/django-filebrowser/en/latest/file_storages.html). It can be expected that FILEBROWSER_MEDIA_ROOT and FILEBROWSER_MEDIA_URL will not be used in the next major release of FileBrowser.

Regarding the other issue of having DIRECTORY (e.g., 'uploads/') saved in a database: This will stay as it is. Backward compatibility is one reason. The other reason is that you may work around the problem you're facing by setting FILEBROWSER_DIRECTORY='' (an empty string) and changing the storage engine's location (FILEBROWSER_MEDIA_ROOT) to whatever you like (e.g. MEDIA_ROOT + 'uploads/').

from django-filebrowser.