This is the right forum.
This is trivial to do in RoR.
The benefit that you get is that you can have a production ready product in a fraction of the time that it takes you to write a deployment descriptor in almost any other platform.
The program that you want is almost right out of the Agile book - as the main example.
Given that programming is 90% research and 10% coding, you're in trouble if you don't have time to do your own research. On the other hand, soliciting input from more experienced developers is a form of research. The problem is that the answer will be biased.
I disagree with my colleague's comments about "pesky </tag>'s". Redundancy is necessary in any wire protocol, such as SGML (of which HTML is a small subset). Since SGML is generic in nature, with no knowledge of the intended contents or business of the transmitted document, ending a <tag> with a </tag> is a clean notation that allows the expression of any simple or complex data structure and keeps the interpretation of data separate from the data itself.
With that said, Ruby is bult around small-system concepts and Rails has a lot of My-SQLisms. There has been some difficulty getting the Ruby community to understand the benefits of things like prepared statements. Building a transactional system is a bit (not a lot) more difficult than I had expected, so scalable real-time systems that pass the atomicity test require a bit of coding.
PHP has the same sorts of flaws, and is painful enough to understand that I have never actually learned it. It grew organically, so the syntax is irregular. It has most of the same small-systemisms (can I invent that word? please?) that Ruby does.
Does this help?