Heroku wrongly detecting my Node app as a Ruby app

Question

I have a Node project that is using Bundler and Guard to handle my pre-compilations steps. This means that I have a Gemfile in the root of my project along with the package.json file.

My problem is that Heroku believes that my project is a Ruby app, just because the Gemfile exists. And complains that I have not committed the Gemfile.lock, which I don't want to commit.

-----> Heroku receiving push
-----> Ruby app detected
 !
 !     Gemfile.lock is required. Please run "bundle install" locally
 !     and commit your Gemfile.lock.
 !
 !     Heroku push rejected, failed to compile Ruby app

Is there a way to tell Heroku that the app is a Node app and not a Ruby app?

I suppose, I should have done that directly. I thought I would get a faster answer here, though :) — andersjanmyr
– andersjanmyr, Commented Apr 4, 2012 at 12:41

Giovanni Cappellotto · Accepted Answer · 2013-03-13 16:00:02Z

34

The solution to this, with a lot of help from Heroku Support is: use a build pack!

Override the Heroku default buildpacks by specifying a custom buildpack in the BUILDPACK_URL config var

$ heroku config:add BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-nodejs

You can also specify a buildpack during app creation

$ heroku create -s cedar --buildpack https://github.com/heroku/heroku-buildpack-nodejs

Simple when you know it. Some more documentation can be found at Heroku Dev Center

edited Mar 13, 2013 at 16:00

Giovanni Cappellotto

4,9051 gold badge32 silver badges33 bronze badges

answered Apr 5, 2012 at 9:24

andersjanmyr

11.6k5 gold badges31 silver badges29 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

rakslice Over a year ago

At the Heroku Dev Center link that andersjanmyr noted, they have the buildpacks in a certain order in a table, and they say: "By default, these buildpacks will be searched in this order until a match is detected and used to compile your app."

Lounge9 · Accepted Answer · 2015-11-28 03:22:44Z

4

It seems there's a new way to do this as BUILDPACK_URL is now deprecated, explained here, but essentially the command is:

$ heroku buildpacks:set heroku/nodejs

You may also specify a buildpack during app creation:

$ heroku create myapp --buildpack heroku/nodejs

answered Nov 28, 2015 at 3:22

Lounge9

1,42213 silver badges22 bronze badges

Collectives™ on Stack Overflow

Heroku wrongly detecting my Node app as a Ruby app

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related