Foreman: Use different Procfile in development and production

Viewed 22744

I have a homemade Sinatra application for which I intend to use Heroku to host it.

I use foreman and shotgun in development, with the following Procfile:

web: shotgun config.ru -s thin -o 0.0.0.0 -p $PORT -E $RACK_ENV

It works great with both development and production. But the thing is, I don't want to use shotgun in production since it's too slow.

Can we use separate Procfile configurations for both dev and prod?

4 Answers

@sharagoz 's comment on the selected answer, in my opinion, is the best option to allow you to still use foreman start without adding additional arguments AND keep your Procfile separate for Heroku.

To avoid the -f Procfile.dev parameter you can create a .foreman file with procfile: Procfile.dev in it – Sharagoz

In my applications root directory I created a .foreman file and as the comment states

.foreman

procfile: Procfile.dev

Procfile

web: bundle exec puma -C config/puma.rb

Procfile.dev

web: bundle exec puma -C config/puma.rb
webpacker: ./bin/webpack-dev-server

For those still looking for this, according to the docs foreman is not needed anymore. You can simply use:

heroku local -f Procfile.dev

Related