Message from discussion
serving assets directly from couchdb
Received: by 10.229.84.69 with SMTP id i5mr1990332qcl.7.1246516200347;
Wed, 01 Jul 2009 23:30:00 -0700 (PDT)
Return-Path: <mattaimone...@gmail.com>
Received: from mail-qy0-f186.google.com (mail-qy0-f186.google.com [209.85.221.186])
by gmr-mx.google.com with ESMTP id 22si222081qyk.14.2009.07.01.23.29.59;
Wed, 01 Jul 2009 23:29:59 -0700 (PDT)
Received-SPF: pass (google.com: domain of mattaimone...@gmail.com designates 209.85.221.186 as permitted sender) client-ip=209.85.221.186;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mattaimone...@gmail.com designates 209.85.221.186 as permitted sender) smtp.mail=mattaimone...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by mail-qy0-f186.google.com with SMTP id 16so1583600qyk.3
for <couchrest@googlegroups.com>; Wed, 01 Jul 2009 23:29:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:date:message-id:subject
:from:to:content-type;
bh=pU4EIKk2rVvBS/ahQf1nC59r4p67/EzceOzIhCjlNqo=;
b=VBSd00SzP9DhQjAvqfIfrMVeLDaA9n3tNrGrNAJUJI+ksDdQ0gtkXtkEalPFwmuKDr
ad8Y6WwCDOviLeG0O/+dFJmZ4cHtAZ3XiyNUKndkSl5nRn9tkanrFIqp9gngVxyDryit
8ZEgI5kfkNRETUZbXVMrSaNIe5bDw4jcH7lZc=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:date:message-id:subject:from:to:content-type;
b=gKe2uuIfNyevAdNi4nZdt01kB5l02wxPiYSr3jCYzlpdGmtuJbhtzhGdMOS05UFH1G
aYf496bt4fPWFMcwE88rCZ4vLbkIiMPLZ7eFST6UmF96nXWCAhXCdWKNdUUG1N1Lgy8+
2Yl2tvw8N6QGx/chp80pZRA7/+iqVPHdH/O18=
MIME-Version: 1.0
Received: by 10.224.11.142 with SMTP id t14mr10054808qat.356.1246516199275;
Wed, 01 Jul 2009 23:29:59 -0700 (PDT)
Date: Wed, 1 Jul 2009 23:29:59 -0700
Message-ID: <20fefa50907012329h15f45c16k420d2bc758131509@mail.gmail.com>
Subject: serving assets directly from couchdb
From: Matt Aimonetti <mattaimone...@gmail.com>
To: couchrest@googlegroups.com
Content-Type: multipart/alternative; boundary=0015175cdaf043bf0d046db32bc0
--0015175cdaf043bf0d046db32bc0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Here is a great post explaining out to safely serve attachments directly
from couchdb using nginx.
http://vermicel.li/blog/2009/06/16/efficiently-serving-couchdb-attachments.html?dsq=12023120
See my comment to see how to do the same using Merb's awesome router. (Same
feature should be available in Rails3)
Just FYI, we benchmarked the Merb router and its as fast as serving static
files using Apache.
So, in other words, if you need an advanced authentication/logging system
for couchdb, it's really easy to do using nginx, merb (use merb-flat, the
one file app version) and thin (should be better for this kind of stuff).
- Matt
--0015175cdaf043bf0d046db32bc0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Here is a great post explaining out to safely serve attachments directly fr=
om couchdb using nginx.<br><br><a href=3D"http://vermicel.li/blog/2009/06/1=
6/efficiently-serving-couchdb-attachments.html?dsq=3D12023120">http://vermi=
cel.li/blog/2009/06/16/efficiently-serving-couchdb-attachments.html?dsq=3D1=
2023120</a><br>
<br>See my comment to see how to do the same using Merb's awesome route=
r. (Same feature should be available in Rails3)<br>Just FYI, we benchmarked=
the Merb router and its as fast as serving static files using Apache.<br>
<br>So, in other words, if you need an advanced authentication/logging syst=
em for couchdb, it's really easy to do using nginx, merb (use merb-flat=
, the one file app version) and thin (should be better for this kind of stu=
ff).<br>
<br>- Matt<br>
--0015175cdaf043bf0d046db32bc0--