Procfile.dev doesn't work

scottohara commented 8 years ago

When running heroku local -f Procfile.dev, the db process that starts couch doesn't return control, so the web process never starts (until CTRL-C, which kills the db process).

Tried both:

db: bundle exec rake db:start

and

db: couchdb

scottohara commented 7 years ago

Turns out that heroku local uses port 5000 for web processes unless a port is explicitly specified.

Fixed by adding -p 9393 to the web command.

There are still some funny issues though. Firstly, the Thin startup message, i.e.

== Shotgun/Thin on http://127.0.0.1:9393/
Thin web server (v1.7.0 codename Dunder Mifflin)
Maximum connections set to 1024
Listening on 127.0.0.1:9393, CTRL+C to stop

...doesn't appear until the first web request is handled (seems like the output is buffered until a request forces it to be flushed to stdout?)

Secondly, hitting CTRL-C kill the processes, but doesn't return to the prompt. Requires a second CTRL-C to get back to the prompt.

scottohara commented 7 years ago

If/when we get this resolved, we should be able to remove the foreman gem from Gemfile and update README instructions to refer to `heroku local instead

scottohara commented 6 years ago

No longer seems to be an issue

scottohara / tvmanager

Procfile.dev doesn't work #71