On Jun 6, 2006, at 9:53 AM, Umbrae wrote:
>
> If Django follows symbolic links on upload (and you're running linux),
> you could use a symbolic link in the directory that would point to
> wherever you'd like to store the files. Just make sure your apache
> configuration is set to not follow symb
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> 1) Create two separate media directories: /media/public and
> /media/restricted
> 2) Configure Apache to serve /media/public directory directly
> 3) Configure Apache to serve the /media/restricted directory using
> mod_python
> 4) Set a url entry
> 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 t
If Django follows symbolic links on upload (and you're running linux),
you could use a symbolic link in the directory that would point to
wherever you'd like to store the files. Just make sure your apache
configuration is set to not follow symbolic links and you're set.
Just a thought.
--~--~--
"Adrian Holovaty" <[EMAIL PROTECTED]> writes:
> Are you using the Django admin for the file uploads? If not, you can
> just write your own views that upload the data to a place of your
> choosing. You'd be dealing with request.FILES for this.
Unfortunately (?), I am using the Django admin for th
On 6/6/06, Jason F. McBrayer <[EMAIL PROTECTED]> wrote:
> 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
6 matches
Mail list logo
