From WordPress to Radiant CMS

So, yesterday I spent a little time migrating a site from WordPress to Radiant CMS, and so far I couldn’t be happier.

I didn’t do this because I was unhappy with WordPress, but because I wanted to trim my server down by running nginx instead of Apache. This WordPress install was the last thing that I felt like was easier running on Apache, and for some reason I had reservations about running PHP/FastCGI on nginx just to run a simple WordPress site.

Right now, the site isn’t a blog, rather just a site that I did for a customer and wanted them to be able to update/add content easily. So, really, any CMS would do.

I chose Radiant CMS for no other reason than it’s in my favorite language, Ruby. After a quick read through the docs, I gave it a go.

Installation was typically easy for any of these types of things; just create a database, run a couple scripts to migrate/seed it, and off you go.

What I surprisingly like so far, is being able to add/edit snippets, layouts, css, and js directly in the CMS. Obviously, it’s not the most elegant text editing environment, but, I was copy and pasting some old css, and bits and pieces from the WordPress files, and it went really seamlessly.

I like the idea of being able to change the layout of the sidebar wherever I’m at, and not have to do a cap deploy, or fire up FileZilla to upload the file.

Finally, I felt like Radiant CMS was just a better fit for this particular site. It isn’t a blog, so a general purpose CMS is much more appropriate in my mind.

It is up and running today with no problems so far, but I still have a little work to do on my server.

  1. Figure out exactly how to monitor the site with Monit (kinda odd using rvm)
  2. Move all of my other sites off of Apache/Passenger and on to nginx/Unicorn (or Thin, or Passenger…)
  3. Dump Apache, and hopefully watch my free memory jump!

Stay tuned as I hope to post more about this in the future.

**UPDATE**

Just got Monit keeping an eye on this. Pretty easy actually.

  1. Create a simple Rackup file (see RailsGuides)
  2. Point the actual Ruby binary, probably somewhere in
    /usr/local/rvm/rubies

    to the actual server binary (in this case, Thin), and point that at your new config.ru

Now, once nginx is fired up, I’ll have it serve all static files, and get rid of

use Rails::Rack::Static

in the config.ru

Till then…

In any institution in which a majority of citizens or members can pass laws or rules that apply, not just to themselves, but to all members of the group, judgment is required to distinguish potential laws which are reasonable and fair from those which are tyrannical because they are unnecessary, unfair, and justifiably intolerable to the minority that opposed them. And formal mechanisms need to be in place, wherever feasible, to prevent tyrannical laws from being passed by those whose judgment in such matters might fail.