Camping for IT

Camping is a great micro-framework from the legendary _why the lucky stiff. It's small size and simplicity give me even more enjoyment than when I work with Rails. But it hasn't gotten the recognition as a tool for companies as it deserves. In many ways Camping should have easier access into the hearts and minds of the system administrators and internal company coders then Rails has. A lot of what is written internally for a company is little tools for small changes here and there. Passwords need to be changed and the business software needs to export new usernames or change account informations automatically. Historically this has usually been done with perl cgi-bin scripts or even small PHP scripts. We could start using Ruby cgi-bin scrips from ground up but that wouldn't be very ruby'ish of us would it.

But you do run into a few problems when you start using Camping like that. Camping's conventions assume that you are writing something from the ground up. It assumes that you want to use sqlite but if you use mysql then it assumes that everything is in a single database. But things tend to be different when we write our little helper tools. We might want to build a logviewer to look at some logs in a mysql table and then we have to compare that to a user table in a totally different server. Luckily, this being ruby, that is easily fixable in an elegant way.

Post continues, click to read more...