Here's a link to the thread from January
and here's a brief summary I made when I decided on Rackspace
One thing I didn't mention was that Cloud Files doesn't have any version
control or any way to roll back files. To compensate for that I am using
Git on a local repo (not uploaded to GitHub, etc). It is a bit clunky, but
for the small number of changes I need to make, it suffices.
On Thu, Mar 28, 2013 at 12:09 PM, Josh Wilson <[log in to unmask]>wrote:
> Would you mind sharing what CDNs you seriously considered as alternatives,
> and what led you to go with Rackspace?
> On Thu, Mar 28, 2013 at 11:35 AM, Tom Keays <[log in to unmask]> wrote:
> > A couple of months ago I asked for suggestions for a CDN that a library
> > without its own web server (other than our OPAC) might use to deploy
> > LibGuides, Serials Solutions A-Z journal lists, etc.
> > We're a small institution and I have just a handful of files I needed to
> > deploy, so I figured that using a CDN could be much less expensive than
> > contracting for a full-fledged web hosting solution. I weighed several
> > suggestions sent to this list and decided to give Rackspace Cloud Files
> > a try. Pricing is 10 cents/Gigabyte/month.
> > It doesn't have a true nest folder file structure, but if you use
> > Cyberduck, which supports the Rackspace API , it represents the
> > directory structure of your original local repo in the URL -- e.g.,
> > I didn't purchase anything but Cloud Files, so I don't have access to
> > Rackspace CNAMES to give my URLs more friendly names (and campus IT isn't
> > interested in providing that service for us). I decided this was not a
> > problem on the whole.
> > The system has been very fast and stable, with none of the intermittent
> > outages I experienced when I was testing the idea by hosting some of
> > files on my hobby website on Bluehost.
> > The only gotcha is that if you need to upload a file, there is some
> > for changes to propagate across the CDN. The Rackspace technician I
> > too was surprised how long an old copy was hanging around after one of my
> > updates, but we concluded that, ultimately, that's the proper function of
> > the service (at least on this CDN). You can speed things up by deleting
> > original and re-upping it, but changes are not instantaneous.
> > After 2 complete billing cycles, we've yet to have enough traffic to
> > generate a charge. This surprised me, since I thought there might be a
> > minimum usage charge hidden somewhere, but we've not seen any to date.
> > not anticipating this situation will change drastically. It will take
> > a bit of traffic for us to hit the 10 cent mark.
> > I'm pretty happy so far.
> > Tom
> > : http://www.rackspace.com/cloud/public/files/technology/
> > : http://trac.cyberduck.ch/wiki/help/en/howto/cloudfiles