GitLab

Created by: crohr

The Procfile may be used for deployment purposes (e.g. on heroku, pkgr.io, etc.), therefore any parameter should default to a production-ready one. They can then be overwritten in dev by using a proper .env file at the root of the project. Needed by PR #6716.

Created by: dosire

👍

@randx Can you review?

By Administrator on 2014-04-07T15:00:11 (imported from GitLab project)

Created by: dosire

Thanks @randx !

By Administrator on 2014-04-07T16:26:55 (imported from GitLab project)

Created by: dzaporozhets

after this I no longer can use foreman start for dev purposes. So we added 4df1a10e and 24934c9b to restore old behaviour

By Administrator on 2014-04-08T11:58:38 (imported from GitLab project)

Created by: crohr

Works for me, but the correct way to deal with development environment variables is having a .env file at the root of your project, which will be picked up by foreman (http://ddollar.github.io/foreman/#ENVIRONMENT):

$ cat .env
PORT=3000
RAILS_ENV=development
UNICORN_CONFIG=path/to/dev-unicorn-config

By Administrator on 2014-04-08T12:06:55 (imported from GitLab project)

Created by: dzaporozhets

@crohr why you didn't do it in this PR?

By Administrator on 2014-04-08T12:17:08 (imported from GitLab project)

Created by: crohr

@randx because .env files must not be committed, as they may be specific for each developer, and might be inadvertently picked up in production.

By Administrator on 2014-04-08T12:18:45 (imported from GitLab project)

Created by: dzaporozhets

Not all developers know about .env and they will be confused why command bundle exec foreman start not working any more. So next time set default settings so something doesn't break quietly

By Administrator on 2014-04-08T12:25:45 (imported from GitLab project)

Created by: crohr

Will do!

By Administrator on 2014-04-08T12:29:13 (imported from GitLab project)

Created by: dzaporozhets

@crohr thank you :)

By Administrator on 2014-04-08T12:35:42 (imported from GitLab project)