In at the deep end – getting a VPS

Well, after some research, I’ve decided to go and take the plunge and get a basic VPS.

My aim is to get Railo/Resin/Apache/PHP/MySQL running on Centos 5.3.

I’ve gone for Wizz VPS, as they’re UK based, and a child company of my current PHP hosting – Layershift, with whom I’ve had good experiences – they are also staggeringly cheap.

They’re also completely unmanaged, so I’m on my own…

Getting mySQL and PHP installed was easy, just using the VPS containers package management system (so a bit of point and click). Installing yum and then using that was equally easy. ‘yum update’ = genius.

I’ve been fairly taken back by just *how* efficiently RAM seems to be handled under Linux/Centos. I’m used to a windows box, where just running the OS and CF8 can take up the best part of a GB. I’ve currently got MySQL and PHP, and the OS running under 40MB (not under any load of course) which is amazing.

The tricky part is going to be getting Railo in and running. Whilst there seems to be a fair amount of chat on the Railo Google group about creating some definitive install guides, I’m finding the lack of a definitive install guide somewhat frustrating. I’ve managed to do some things, like install Java for compiling connectors etc, but the syntax (and really, the true understanding of what I’m trying to achieve) does escape me a bit at the moment. My Linux Kung-Fu needs work.

Hopefully we should start seeing some proper documentation for Railo production environments soon! (and I mean documentation for the latest Railo version, and the latest and greatest Linux distros).

Finally – some Railo VPS goodness

I think I’m slightly over the top happy that I’ve got Railo working now..

All thanks to Jordan Michaels’s beta installer (get on the Google Railo Beta list to get access – which worked perfectly.

Had a couple of hiccups, but they were completely my own fault – I was getting a 503 error whenever I tried to serve a .cfm page; checked the logs, and low and behold TomCat couldn’t start: something was using port 8080. (A Address already in use:8080 error)

A quick “netstat -anp | grep 8080” command, and lo and behold, I’d set Apache to listen on 8080 in the http.conf.

Took that out, and restart apache/railo, and all is happy.

Now I’ve just got to read up on Railo security, and pop a bit more RAM In the VPS (it sits at about 140MB with railo/mysql/tomcat and the OS), oh and test *everything*.

As Hannibal would say – “I love it when a plan comes together” 🙂

One area where Open Source Railo should make a difference…

With the release of Railo 3.1 as an open source project, I can think of one area in particular where this is going to make a huge difference – hosting.

UK hosts seem to split into two camps (IMO), LAMP specialists, and then CF providers, often running Win2003/IIS/CF/MySQL/SQL server.

With UK hosting, there is a huge disparity between hosting for standard LAMP, and CF hosting: Not just price, but diskspace and bandwidth. You can pick up a linux PHP based VPS with 30GB webspace and about 300GB of bandwidth for a fraction of the price the equivalent would be with CF hosting: the reason is fairly obvious – CF licenses (and windows server licences) cost a lot – shared hosts in particular seem to cram a lot onto several larger servers to stretch the license as widely as possible (I’m not saying LAMP hosts don’t), so diskspace (in particular) is at a premium.

Previously I’ve considered getting a VPS, and simply buying a CF standard license, as generally speaking, that suits my freelance needs; but that extra £1000 odd is simply crippling, and makes the whole idea unuseable.

I run a lot of smaller sites, none of which could afford the CF outlay and rely heavily on shared hosting – the irony is, as they’re built in CF, they were initially quicker and thus cheaper to build.

I hope we’ll start to see Railo offered as another service alongside PHP: there’s now no reason *not* too, except the obvious maintence required for an additional service, and the potential hit to the server’s RAM in actually running it. Alternatively, this could all go the way of OBD or the smith project, but I hope not.

Whilst there are many sides to this argument, especially the effect on CFML as a language, this announcement is something I’m really rather pleased about overall – it gives many more sites the option of using CFML, especially those smaller ones which would otherwise have to go on PHP for budget reasons. Additionally, for higher education, running Railo should now be a no brainer – after all, it’s free, why not at least try it?

I’m now seriously considering consolidating all my hosting into a single linux VPS with PHP, Railo and MySQL. Being able to run Drupal and all my bespoke CF projects under the same roof is very appealing. Now all it takes is do some research into Railo properly, and check there aren’t any massive “gotchas”. Speaking of which, is there a good CF8 vs Railo 3.1 comparison out there anywhere yet?