Well, after playing around a hell of a lot more with this thing, I shall enlighten you all on some of the more technical aspects of what I’ve done here…

Firstly, the whole shebang is actually a ‘virtual appliance’ I downloaded from VMware – specifically, Jumpbox with Wordpress v2.3.3. For those unfamiliar with what a virtual appliance is, basically, its a self contained operating system running in a virtual environment on a host PC.

I’m running the appliance on my ‘normal’ PC (AMD Athlon 64bit, 2Gb RAM running Vista Ultimate 64bit) which also runs another appliance which is a virtualised server created when one of my physical servers (GALACTICA) died a few months ago (if anyone is interested, I’ll blog about how I actually virtualised that server – its a handy thing to know how to do if you ever have a hardware failure like I did)

Now, back to this Blogging server arrangement – After downloading the appliance, I extracted it and just had to open the appliance configuration file in VMware Workstation, and viola! There were a few easy setup steps to go through initially, basically asking about network setup, name of the server (which I called PEGASUS) etc. but thats hardly worth mentioning.

After that, it was just a matter of pointing a browser to the local IP address, and that was it!

Of course the next step was making it all pretty, and actually creating the first blog post ;) That caused an interesting dilemma, when I found out that I couldn’t save files to the themes or plugins directories on the server, because the unregistered version of JumpBox in the appliance doesn’t allow it.

Well, I wasnt going to let that stop me – so I cheated ;) I created a new virtual machine in VMware Workstation that was just a standard Ubuntu installation, and then added a second virtual hard drive – which I pointed to the files for the jumpbox/wordpress data drive. That then gave me full write access to the drive and the ability to copy across the theme and plugin files I wanted. Its a bit of a pain in the bum as I have to shut down the blog server, boot up the ubuntu one, copy files, shut down ubuntu, and then finally re-start the blog server – but it gets the job done :)

Once I’d got it to a point where it was working locally, it was time to get it visible to the outside world. That was slightly more fiddly than I had originally expected.

I port-forwarded all HTTP traffic to the servers IP address, and, one would think, that would be it…..well, not quite.

In the ‘options’ settings for WordPress, I had set the address to be my saltwaterit.com domain name – however, that domain name re-directs to saltwaterit.dyndns.org (I use the DynDNS service because I dont have a static/fixed IP address) and because of this redirection, WOrdPress doesn’t get things quite right and sticks your browser in an infinite loop. So a small alteration to the options to say the DynDNS address, and everything now works. Basically, when you first browse to the site from the saltwaterit.com address, it forwards you once to the DynDNS address, which then takes it from there.



Possibly related:


blog comments powered by Disqus