Rails Asset Pipeline: Ditching therubyracer

March 17, 2014

I’m fixing things. And I’m sick of compiling therubyracer on production machines just to be up-to-date.

So, I tried switching to node.js for asset compiling in production. I’m already going to have Node.js on the server anyways so it was a no brainer.

Too bad it was also a no-go.

The node.js make install script installs node to /usr/local/bin/node which isn’t in the PATH of the user running Passenger by default. And adding PATHS to a running system isn’t worth my time for a single binary.

The answer? Link it:

ln -s /usr/local/bin/node /usr/bin/node

And then you’re good! Rails/Passenger should pick up node and quit asking you for a JS binary.

Also, I’m trying Digital Ocean for a hosting solution. So far, it’s cheaper then Rackspace… and Amazon… and Linode… And it’s got just enough for me to get by!


James Hagerman

Written by James Hagerman

© 2026