On Wed, 2011-11-02 at 09:25 -0700, John Duddy wrote: 
> Certainly there is s simpler way to talk to an already running
> instance of rocket (mine) and tell it to serve more static files? I
> could also do it via apache, if I could talk to apache and tell it to
> serve from locations not listed in its config. I need to do this at
> runtime, though.

To serve anything anywhere in the filesystem, you can do something like:

    Alias /reports /

And then append the file path. Of course be aware of the risks of
letting users browse the whole filesystem..

If that's in a small intranet to which only trusted people can have
access, plus you tweak permissions on filesystem in order to limit where
the www-data user can have access, plus limit cgi/php/.. file execution
to only some locations, and maybe even add http authentication, this
could be a valid solution..

Better if you can restrict more the accessible path, eg. if your users
will create reports only in their home dirs, you can use something like:

    Alias /reports /home

And maybe even limit which user can access which directory (there are
several ways to do this, depending on where you get the users, etc.)

-- 
Samuele ~redShadow~ Santi
----------------------------------------------------------------
     redshadow[at]hackzine.org - redshadowhack[at]gmail.com

  Blog: http://hackzine.org

  GPG Key signature:
       050D 3E9F 6E0B 44CE C008 D1FC 166C 3C7E EB26 4933
----------------------------------------------------------------
/me recommends:
    Squadra Informatica - http://www.squadrainformatica.com
----------------------------------------------------------------
 - Proud ThinkPad T-Series owner
 - Registered Linux-User: #440008
      * GENTOO User since 1199142000 (2008-01-01)
      * former DEBIAN SID user
----------------------------------------------------------------
      "Software is like sex: it's better when it's free!"
                              -- Linus Torvalds

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to