Moved static content to Cloud Files

I've moved all of this blog's CSS, javascript, and most of the images to Rackspace's Cloud Files so they can be served via the Limelight CDN. So far, this has cut the load times in half.

Most of the edits aren't supported by WordPress, so I ventured into the source code for my plugins as well as my theme and adjusted the links to point to the mirrored files on the Cloud Files service.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Printed from: http://rackerhacker.com/2008/12/30/moved-static-content-to-cloud-files/ .
© Major Hayden 2010.

4 Comments   »

  • It appears, according to FireBug, that there are several missing files on page load.

    I was reading up about Mosso - it looks like the containers for uploaded files dont actually support nested folders. The missing files according to FireBug are all in a folder called "i" (images I assume).

    The Mosso CloudFiles looks very interesting though...

  • major says:

    Good catch, Nicholas! I guess I should have moves the files to Cloud Files while I was more alert. :-) I corrected it and the changes should be up shortly.

    Thanks!

  • Trent says:

    cool - doesnt look like the Rack has configs here in AU though :(

  • Andrew says:

    Looks good, but doesnt seem your static content has been served compressed with either gzip or deflate, and none of your images, css, or js have been timestamped.

    Is this an option in cloud files ? and if it isnt, is that because CDN is so fast and bandwidth so cheap that its not worth doing it ?

    Also, can you do mod-rewrite to make it look as if the static content has come from your own servers ?

    Cheers!

RSS feed for comments on this post , TrackBack URI

Leave a Reply