StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODeploying sinatra app (with config.ru) on heroku cedar stack
text
Body
copied!<p>I'm trying to refactor my sinatra code to separate my main file into separate files, using some tips from <a href="https://stackoverflow.com/a/5030173/111884">this response</a>, and I'm having troubles deploying to heroku.</p> <p>Previously I didn't have a <code>config.ru</code> file, and just used my <code>Procfile</code>, which was:</p> <pre><code>web: bundle exec ruby web.rb -p $PORT </code></pre> <p>as per <a href="http://devcenter.heroku.com/articles/ruby" rel="nofollow noreferrer">this article</a>.</p> <p>From the refactor, I've now changed my <code>Procfile</code> to</p> <pre><code>web: bundle exec thin -R config.ru start -p $PORT </code></pre> <p>With my <code>config.ru</code> file being</p> <pre><code>root = ::File.dirname(__FILE__) require ::File.join( root, 'web' ) run MyApp.new </code></pre> <p>And my <code>web.rb</code> file being contained around a class definition</p> <pre><code>class MyApp < Sinatra::Application # ... end </code></pre> <p>This works on my local development computer, but when I deploy to heroku, I get</p> <pre><code>2011-12-01T11:21:54+00:00 app[web.1]: bundler: command not found: thin 2011-12-01T11:21:54+00:00 app[web.1]: Install missing gem executables with `bundle install` 2011-12-01T11:21:56+00:00 heroku[web.1]: State changed from starting to crashed 2011-12-01T11:22:01+00:00 heroku[router]: Error H10 (App crashed) -> GET [my app].herokuapp.com/ dyno= queue= wait= service= status=503 bytes= 2011-12-01T11:22:02+00:00 heroku[router]: Error H10 (App crashed) -> GET [my app].herokuapp.com/favicon.ico dyno= queue= wait= service= status=503 bytes= </code></pre> <p>Is thin not installed on heroku? Or is there some other way of running my app on heroku with the changes?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload