I've got an unusual situation with an app, and I'm wondering if anyone could make a suggestion. The app will have a number of file upload fields for uploading files that are _not_ supposed to be made available to the webserver (as they are private). I'd like for particular FileFields to be able to upload to somewhere that is not a subdirectory of MEDIA_ROOT.
The obvious solution is to just set MEDIA_ROOT to someplace that is not visible to the webserver (making MEDIA_URL somewhat irrelevant), and let the webserver serve media from someplace else, that Django doesn't know about. I can do this if I have to. However, I'd like to be able to use my apps that require this setup in the same project as more typical apps that need MEDIA_ROOT to be visible to the webserver. So, is there some straightforward way to put file uploads outside of MEDIA_ROOT? Should I write my own field class for the purpose? Move the file someplace else in the model's save() method? Use the normal setup, but lock down that subdirectory of MEDIA_ROOT in the webserver's configuration? Something else? -- +----------------------------------------------------------------+ | Jason F. McBrayer [EMAIL PROTECTED] | | "If you wish to make Pythocles wealthy, don't give him more | | money; rather, reduce his desires." -- Epicurus | --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
