In the previous blog we explained about all the features available in RLingCMS. In this blog we are here by providing the information about the technologies used in building RLingCMS.

1. Framework.

RLingCMS is built using Ruby On Rails technology. We have been comfortable programmers for 5 long years on ruby on rails and that’s what made us pick this technology. To build RLingCMS we use the latest rails version i.e. Rails 3.0.5 and the latest ruby version 1.9.2. Even thought RLingCMS cannot work on earlier rails versions i.e. Rails 2.3.X versions, it works fine on earlier ruby versions i.e. 1.8.7.  which are configured to run rails 3 activities.

2. Front End Scripts

We have used HTML to yield all the front end content. We could have used HAML, but since most of the designers do not have much knowledge of HAML, we restored to using HTML.

Regarding javascripts, thought our intial coding started using Prototype and scriptaculous, later dates, we moved our javascripts to JQuery

To write up descriptions and page bodies, we have used a rich text editor where users can type HTML content into the editor. We have used CKEditor to edit rich text.

3. Testing Criteria

While building RLingCMS, we haven’t just ran and built the app, we have also used the best techniques to ensure the application we have built is clean and neat. In order to do that we have written unit tests and integration tests. For unit tests we have choosen RSpec and for integration we have used Cucumber with Capybara. We initially started with Webrat but later on seeing the flexibility of Capybara, we shifted to capybara. RlingCMS uses Factorygirl and database cleaner to intitialize the cucumber tests

4. Databases

Even though there is very flexibility to use any Database with RLingCMS i.e. all we have to do is configure the database adapter in the database.yml file, all our implementations have been made on MYSQL database. However we see no harm in using sqlite or postgresql or any other relational database system for that matter

5. Servers

RLing CMS on its development mode uses the in built webrick server system, however all our production systems are on Apache and Phusion Passenger (mod_rails). We have not tested it on Mongrel or on NGinx. Phusion Passenger is very flexible as all we have to do is to change the .htaccess file and run a touch command.

6. Other Technologies used

1. Paperclip – To upload files and image resizing activities
2. RailRoady – To Create a model and controller diagrams
3. UserStamp – To record which used created what

This is a public release of technologies used in RLingCMS.

-- Satish N Kota, Chief Initiator, RLING CMS.