Does it make sense to add Kamal to Gemfile?

[spryffee]

Considering I'm going to distribute Rails application so one could create own Kamal configuration and deploy, can there be any reason to have Kamal installed with development group of Gemfile as we was doing it with Capistrano?

[morgoth]

The reason might be to have control over kamal version.

[eric1234]

I've added it to my Gemfile when I wanted to use a fork of Kamal that had pending fixes.

[igor-alexandrov]

Since Kamal is an actual dependency of the application, but an infrastructure management tool, I don't like the idea of adding it to the application Gemfile. I usually have a separate Gemfile for it.

# ./kamal/Gemfile

# frozen_string_literal: true

source 'https://rubygems.org'

gem 'kamal', '~> 1.4.0'

BUNDLE_GEMFILE=kamal/Gemfile bundle install

BUNDLE_GEMFILE=kamal/Gemfile bundle binstub kamal --path ../bin

This will allow you to have ./bin/kamal, manage Kamal's version with Rubygems and at the same time have your application's Gemfile clean.