I'm relatively new to a lot of the stack I'm using and have run into a problem deploying to Heroku.
I'm hoping this is a simple thing as I'm not very familiar with Heroku even though I've trawled StackOverflow, Heroku's site, Google and everywhere else I can think of but no joy.
Here's the issue:
- I create a local Padrino app
- I go through the normal process to deploy straight to Heroku using git
- It detects it as a Ruby/Rack app and everything is happy
- I add the gem neo4jrb/neo4j
- I deploy again
- This time it thinks it's a Ruby/Rails app and won't run
From what I can find Heroku uses the config.ru file to detect a Rack app and the use of Rails in the Gemfile.lock to detect a Rails app.
The neo4j gem has a dependency on 'railties' which in turn has a dependency on 'actionpack' which in turn has a dependency on 'rails-dom-testing' and 'rails-html-sanitizer'. So both of these rails sounding gems are in the Gemfile.lock.
My assumption is that the attempt to detect Rails happens first, it sees some rails related items in the Gemfile.lock and then treats it as a Rails app from then on.
Is there a way to tell Heroku to treat it as a Rack app regardless of what the detection thinks?