Peter's Blog

A short update on my Slicehost vps which I have had for two months now. I love it. It's fast, reliable and I have no criticisms of it whatsoever. I've cancelled my vpslink vps and I will cancel site5 once the contract runs out. All my eggs in one basket (ok, two if you count the rsync.net backups). Slicehost offer backups but:

• they cost $15 a month
• you only get three
• they are snapshots of your live system and hence will back up the trojans, root kits or whatever your system has succumbed to
• rsync.net is independent

TODO: learn capistrano.

Peter's Blog: No affiliate links.

This site was offline yesterday while site5 moved the hosting to a server in Texas (yee ha). Everything was offline for a few hours during which time I changed the DNS so the domains (four in all on this host) pointed to the new server on a different IP address.

When the server came up my generic domain which I use for forgettable experiments was ok but the domain pointers (i.e. secondary mappings of domain names to the same ip address as the primary domain name), including petersblog.org were still broken. I tried to kick petersblog.org into life by deleting the domain pointer and creating it again but then I ran into site5's checking against a whois database, presumably to make sure I wasn't trying to hijack someone else's domain name. It seems that this whois database updates comparatively slowly: when I did a whois lookup the records were already up to date. It wouldn't let me create the domain pointer.

Another domain name on a domain pointer started working later in the day so I ought to have been more patient.

This morning I was able to create the domain pointer and hence I am writing this. Fortunately deleting and recreating the domain pointer has not zapped the awstats log history which is recording half a million hits on petersblog.org over the last year.

A third site was running on Ruby on Rails and Radiant and that was broken: it loaded a page that was totally blank. I presumed that the rails on the new site5 server is different or broken so I did something that was on my todo list anyway, move it to the vpslink server which I have as a better Rails platform.

I've had the site5 account for a year, the contract is up and I may be in a position to abandon it or upgrade. Right now they are doing a special offer of 750g for $7.50 a month (yes, that's 750 GIGABYTES) which is almost irresistable. 750g backup space anyone?

Site5 have been ok up to now for basic web hosting and php stuff. Their rails is not totally hassle free (you can get things running if you spend enough time poring through the forums) and I prefer root access for this. It is still hosting a couple of drupal sites including this blog, mainly because they are tied to php4 which I don't want on my vpslink server (less is more).

The vpslink box has apache randomly crashing, presumably through lack of burst memory. I'm not sure I want to commit myself to it long term. I'm tempted again to get a dedicated host and one of these huge bucket site5 accounts for rsync backups while they are still available.

Disclosure: I was in the site5 affiliate program at one time and even earned a few $$$ from it. I'm not actively in it now, although there may be some old affiliate links knocking around here. I'd rather not take their money and be in a better position to criticise them.

I've had a few emails from people wanting to pay to put links here but I haven't taken them up. You will note that this is one of the few sites on the net not plastered with google ads. I like it that way.

I've got a nice Rails development setup going now. Aptana is a very nice IDE, very powerful, very rich. The Rails development aspect is most useful in being able run applications in development mode on my PC. I use the mysql server on the deployment server through an ssh tunnel rather than install a database on the PC.

I have created a subversion repository on my VPSlink server. I have installed the subclipse plugin on Aptana and checked out my application onto the work PC. I work on the application in Aptana, polish it and when it is ready I commit the changes again through Aptana. Then on my server I deploy the code by getting the new version out of subversion. I don't use a simple rsync to deploy and I haven't got into capistrano (the rails deployment tool) going via svn works for me. I might consider putting up something like trac (or a rails based alternative) to give me a development wiki and web browsing of the repository.

I've been thinking about backups and the current plan is to backup the SVN repositorys and mysql dumps from my VPSLink server to my site5 server and vice versa. The VPSLink stuff is more in need of backing up since I am the administrator of that one, the site5 account includes daily backups. I was tempted by rsync.net a nice, simple, flexible and cheap remote backup option but since I already have two accounts with ssh access and 35G of space between them I don't think I need to spend more money. Rsync.net looks appealing but the main thing it is lacking for professional purposes would be Windows file permissions, otherwise I might consider it for backing up the servers at work: being able to recover all ones files is good, not having to spend a week fixing the spaghetti mess of windows access permissions is better.

One major change is that I have reverted from Lighttpd back to Apache on my VPSLink server. The main reason for this was that Lighttpd seems to have some limitations in terms of supporting things like drupal's urls. Lighttpd would be good for simple setups but getting multiple legacy php and rails applications set up is just as troublesome as with Apache so I've gone back to the devil I know.

I've had Apache fail to start with memory errors a few times. This could well be the 500M limit of the VPSLink coming into play. VPSLink is cheap because there is no swap, 500M is my absolute limit. If I start getting memory problems I will have to consider the options:

• I can upgrade the VPSLink to 1G memory but for similar money I could get a cheap dedicated server
• I could get a different VPS account, one that had burst memory (it's the bursts that kill VPSLink) but I do like the performance of VPSLink.
• I could fiddle about tuning the number of apache processes and suchlike but life is too short for that one

This blog is still on the site5 account. The server is being upgraded soon, maybe this will resolve the loading issues it has whenever I try doing some development on it (e.g run 'top' and shriek in horror).

I was finding Rails development on my Site5 account slightly problematic. There were these issues:

• because of the way the shared hosting was set up you generally needed to trawl the site5 forums to find the special site5 specific hacks to do what you wanted. For example, many seem to have tried and failed to install trac so ultimately one has to compromise over what one can do.
• sometimes it was very slow: I'd find it to be sluggish and checking the load average on the server it would be in double figures: over 300 processes fighting for time with certain people hogging the cpu.

I now have a number of web projects on the go (five including this blog) and I fancied going back to dedicated hosting for the total control it would give me. However there was a problem here: dedicated hosting is expensive and I didn't fancy shelling out that much. After much agonosing I decided to return to using a Virtual Private Server (VPS). I chose to go with VPSLink as their prices were reasonable and it seems suited to what I want. They seem to specialise in VPS's and their site has a blog/wiki/forum which gives them a face compared to oneandone, godaddy or any other big name that only provides vps's to cover the market. I now share a server box with fifteen over guys, each with 512Megs of memory to call our own. Each of us has a 'virtual' server with root access and hence total control over what we do.

On my virtual server I chose to install a preconfigured Ubuntu 7 linux/Ruby on Rails/Lighttpd setup. It is very nice, logging into it with ssh it is hard to tell that the server is shared and is running on a different continent. My rails applications run nice and snappy (once they have done their caching).

I haven't used lighttpd before although I was aware of it as a new clean apache wannabe. While apache is getting bloaty and the configuration files have to me always been obtuse, requireing endless try-this-and-see-what-happens attrition, lighttpd's configuration file was immediately crystal clear: here's the url, there's the directory that serves it. Nuff said. The config file in my installation had a commented out Rails setup which worked on my first tweek.

The only problem I have had thus far with lighttpd is that

/etc/init.d/lighttpd stop

doesn't stop all the lighttpd processes and I have to kill the last one explicitly. I haven't looked into a cause and could even script my way around it if I needed to reboot the server that often.

One possible problem with VPSLink is that their systems are set up such that there is effectively no swap space: if the processes on your VPS use all the allocated memory then tough, they crash. Hence I chose a plan with hopefully sufficient memory (512M) and a light web server. I'm also hoping I don't get too many fcgi processes spawn but I'm not going to lose sleep over that. Should any of my sites get that successful that the server is continually crashing I just upgrade to a dedicated server. (I think I just invited everyone to a DDOS party).

At the time of writing this blog is still on site5. IF I ever get around to porting it to mehpisto then I may move it to the new server. The performance of Drupal on site5 is still acceptable.