views:

48

answers:

2

This is more of a strategy question instead of a 'help with code' question.

I have a content server and need to supply content to various shared hosting and would love to know how you guys would set this up. We would like the content to be 'cached' on the servers so that is appears as static (and to reduce the load on the content server).

Any help would be appreciated. The basic question is regarding how you would deliver and then handle the content for the shared hosting.

A: 

The usual way is to use rsync to keep the "slave" servers in sync with the "master" server. The slaves are then configured to simply display the local files. rsync will make sure that files are copied efficiently and correctly (including time stamps and permissions). It will also make sure that clients don't see partial files and it will return useful error codes, and many more issues that only someone who has been doing this for decades would think of.

Aaron Digulla
A: 

I believe rsync needs shell or at least ftp access. How could I do this without using either? At the most we would use ftp but shell is not available for shared hosting.

So there is content on Box A (dedicated) and Box B, C, D, E, etc need to display some of that content (topic specific shared server accounts) what is the most seamless way to accomplish that.