Sorry to be negative. This is not a good idea for me.
I will feel more comfortable, it will be easier for me to support it later, and I can reuse it in other Ruby / Rails applications.
I seriously doubt it. It will probably be more difficult to maintain / reuse in the future due to additional code that you will need to write in order to βintegrateβ Drupal and Ruby. The larger the code, the greater the chance of errors. I assume that you are going to link them together using REST / webservices / similar technology - if so, you write so much extra code! Gluing the front elements (which should be in Drupal) with functional elements (maybe in Ruby) just sounds so complicated to me.
I assume that it will only be the one who will support the code. What if its someone else? Can you find someone who has two skill sets (Ruby + Drupal) in your area / budget?
What about returning the Drupal community? If your code becomes useful and its a big mess of Drupal + Ruby, you really can't post it on Drupal.org so that others can create, improve and test it.
I offer two options
- Use only Drupal.
- You seem to be in love with Ruby, or at least too used to it. In this case: find a Ruby-based CMS! (Sorry, I do not know!)
For me, this is a classic dilemma: if you create a custom Drupal module that will mean a shorter term pain, because you get out of your comfort zone .... or you have to integrate Ruby + Drupal, which will be easier in a short, but very painful in debt.
I would choose a short-term pain :-)
Sid kshatriya
source share