serving configuration

[Andy Lo A Foe]

Hi,

These days I use nginx which can handle both the reverse proxy  stuff
(mongrel workers on the back) and the reproxying needed for serving
out MogileFS based content i.e. the same cluster handles both the
normal dynamic pages and the MogileFS X-Reproxy-URL stuff: single app
instance.

There are AFAIK no "lightweight" tools for this because it's really
very application specific (e.g. URL to MogileFS key mapping).

Gr,
Andy

On Mon, May 5, 2008 at 8:27 PM, Andrew McClain <andrew at fluther.com> wrote:
> I know this has been touched on before, but I'm getting hung up on serving
> files (specifically step 4 in
> http://lists.danga.com/pipermail/mogilefs/2008-April/001571.html)
>
>  Right now, I'm able to write my files to mogileFS through my app using the
> python client.
>
> We have a bunch of apache servers load-balanced behind perlbal running on a
> separate machine. We have another box running lighttpd serving static files.
>
> The thing that's tripping me up is the whole user-facing URL -> mogile path
> -> actual file data step. It seems really overkill to me to run a separate
> perlbal instance, another instance of my django app (or a stripped down
> version of it) to construct the correct headers and get the URL, just to
> serve an image file (not to mention figuring out where to plug in memcached
> so I'm not bouncing requests all over my architecture). I'm sure that there
> are ways to configure mogile so that it's as fast as just serving an image
> file from lighttpd, right?
>
> Are there any pre-built, lightweight tools for this step?
>
> I apologize for sounding down -- the server migration was supposed to be
> done at the beginning of April. :)
>
>
>
> --
> Tap the collective.
> http://www.fluther.com