Thanks for your comment. At the moment, Cloud Sites has client library support for memcached, but does not offer a place to run the memcached server. That’s what the article was about. You can run the server in Cloud Servers and connect to it from Cloud Sites. There are two key reasons why right now you can’t simply use memcached directly on Cloud Sites today:

1) The current stable release of memcached does not have any user authentication features. There are development versions that have this feature, so this problem will go away soon.

2) Cloud Sites is intended for interpreted code, not long running processes. In order to run memcached, you need to be allowed to run processes that don’t quit after your HTTP request finishes.

So for those of you that are looking for a super easy way to use memcached from cloud sites (no CLI tricks) you will have a way in the future when memcached is added as one of the included features of Cloud Sites as part of the base platform. That solution is still a way down the road because of a few other products that will launch before it, but keep your eye open on The Rackspace Cloud Blog for announcements that will come out when that service is ready to be launched.

Cheers,

Adrian

I saw your article on setting up memcached on Cloud Sites using Cloud Servers:
http://www.rackspacecloud.com/blog/2009/07/30/setting-up-memcached-on-cloud-sites/

I have no experience with all the command line stuff, but I spent hours setting up my first Rackspace Cloud Server on Debian 4.0 and figuring out how to install memcached on it. I was able to successfully install memcached on my cloud server, and I uploaded your example.php test script using the hostname of my Cloud Server but I got a “Could not connect” message.

Is there no way to enable memcached directly on Cloud Sites? And why?