Why is grunt needed? Is it because he's using Rails::API?
Most setups I've seen just let Rails serve the templates.
Most setups I've seen just let Rails serve the templates.
Also grunt has a watch process that see code changes, it will then compile them and have the server get the browser to reload content to get the new version.
When this gets deployed to your production server, you will probably use the same server process that handles the Rails requests. grunt is for development only.