But it will be a cold day in hell when I suggest using node for the backend.
If your project is big enough to require the skills of an experienced back-end guy, then you're so far past the learning stage that you might as well be in your rocking chair screaming at the neighbor kids.
Rails works great for every web task except the very big and the very small. Very small being anything you'd want to put on a Raspberry Pi.
The learning curve is reasonable, and can be made easier if you get the basics of both Ruby and MVC down by using a simpler Ruby framework like Sinatra to build out a few toy apps before jumping into Rails. Once you feel like you need more out of a framework than Sinatra can give, it's time to switch to Rails.
Ruby and the web go together like Captain and Coke.