set :scm_username, “foo”. If you access your source repository with a
different user name than you are logged into your local machine with,
Capistrano needs to know.
Actually the way I access my repository through my app is through ssh
keys. The only user name I have with github is the one I use to log
into github to view my repositories.
So I'm not sure if scm_username is needed and what username does it
want.
set :scm_username, foo. If you access your source repository with a
different user name than you are logged into your local machine with,
Capistrano needs to know.
Actually the way I access my repository through my app is through ssh
keys. The only user name I have with github is the one I use to log
into github to view my repositories.
So I'm not sure if scm_username is needed and what username does it
want.
If I'm not mistaken, they are not talking about your GitHub username
(or wherever you're hosing your repository). They are talking about the
Git username that you set with git config.
This information will show up in git log indicating the author of the
changes at the time they were committed. It has nothing to do with
authentication for accessing the Git repository. That, as you mentioned,
is handled separately from :scm_username thorough something like ssh as
you mentioned.