Add thin to Gemfile (but not gemspec)?

[afeld]

That way the cedar branch can be merged to master for deploying magickly to Heroku or somewhere directly, without requiring thin when used as a gem. On the other hand, thin isn't the only option of server to use, so maybe we don't want to force that requirement?

@jcn

[jcn]

It probably makes sense for magickly to be slightly opinionated when it comes to getting up and running quickly as a service (it already mentions thin in the README after all). Since Heroku is probably the most common use case right now, and this is going to require the procfile and some web server.

For people who want to use some other system (unicorn, puma, etc), the answer is probably for them to make their own app which could really just consist of a Gemfile, a procfile and a config.ru which just runs the server and calls down to magickly. They then get the deployment control while just using magickly as a gem.

[afeld]

Ok, I think that makes sense.

• [x] Use bundler instead of jeweler for the .gemspec, so that gems can be added to the Gemfile independently.
• [x] Add thin and newrelic_rpm to Gemfile (see cedar branch).

[afeld]

On master.