> 1) Shared filesystem between the two hosts to hold the static content

I just found out that I can do that on linode. Thanks for bringing this idea up!

Here's a solution:
Using NFS, mount on the Dynamic server the Static server's directory
for static files (/images /user-uploads etc). Have nginx on Dynamic
with proxy_pass to Static for all static content. All uploads go to
the mounted drive on Dynamic (which points to Static).

Does that sound reasonable?

Cheers

Leonardo

On Mon, Apr 12, 2010 at 12:17 PM, Arvind Jayaprakash
<work@anomalizer.net> wrote:
> On Apr 12, Leonardo Crespo wrote:
>>To make it simpler, here's a scenario:
>>
>>Server A is static.domain.com ip 10.10.10.10 servers ALL static
>>content (jpegs, gifs, pngs, mp3s etc... including user uploaded
>>content like photo albums)
>>Server B is www.domain.com ip 10.10.10.20 servers DYNAMIC content, php files.
>>
>>If user submits a jpg to his photo album, it'll get uploaded to B, as
>>page's going to run on server B because it's a .php file (upload.php).
>>How can the image possibly be served from server A without
>>synchronization issues?
>
> You options are:
>
> (1) Shared filesystem between the two hosts to hold the static content
>
> (2) Use nginx with caching proxy on the static machine
> In this setup, a cache miss will result in a request for the static
> resource from the dynamic server (which I assume is also capable of
> serving static content). This should work as long you expect to have a
> high cache hit ratio
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx