Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
/cc @codyrobbins
- Loading branch information
Showing
1 changed file
with
4 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6f1216c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @kirs sorry committing this here, but you locked the issue...
That
File.read()
will try to the get the.ruby version
in the machine where you are running capistrano right? Wouldn't it be better to read that file in the remote machine, after the code being pulled?6f1216c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. I see no difference in reading local/remote files, but as a fact remote
.ruby_version
may not be available it it's the first deploy.6f1216c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I appreciate the addition of a commented example in the readme (thanks!), I still think that this should definitely be the default behavior of the gem if
.ruby-version
is present. It’s the default case and it reduces unnecessary verbosity of the deployment configuration. It’s not good practice to specify the same important application configuration value in two different places. Since this gem is meant to integrate Rbenv and Capistrano, and since.ruby-version
is supported by Rbenv, I still don’t see a reason this gem wouldn’t include specific support for it?