: Separating static/uploaded content from the site I have a site where I anticipate to have a large amount of users. I've heard that it is a good idea to separate user content (uploaded images)

@Cugini213

Worry about Rsync later - for now you can do it all on the one box.

Your main domain is www.example.com/ on this domain you serve cookies (yum!).

The non-www redirects to the above.

Your static domain is static.example.com/ and on this domain you don't serve cookies or any other header items that are not really needed. Put js+css on there compressed and images served uncompressed. Set anything served on static to be public cache-able and with an expiry date some time into the future.

Now setup your domains to point to the same place on the file system, i.e. if you really want to load test.jpg you can get exactly the same file from either place. Do this with httpd.conf settings and two virtual server entries.

When your traffic gets to big levels you can migrate your static content server to a different box and rsync the whole document root to the new box. A cron job can be setup to do this every 5 minutes or so and the 404 of the static can redirect to the www to pick up on any resources not yet rsynced.

Vote Up Vote Down