Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve the SSH key path later. #146

Merged
merged 1 commit into from
Jan 31, 2015
Merged

Conversation

Ferada
Copy link
Contributor

@Ferada Ferada commented Jan 10, 2015

This enables the user to use e.g. "~/.ssh/id_rsa"` in their configuration file, thereby solving issue #130 and #105.

@brandondrew does this work for you? I don't think generally allowing environment variables in the configuration file is necessary, as "~" is enough here, so I just went with that.

This enables the user to use e.g. "~/.ssh/id_rsa" in their configuration
file.
@brandondrew
Copy link
Contributor

Sounds good to me.

@petems
Copy link
Owner

petems commented Jan 31, 2015

@Ferada Awesome, works for me too! 👍

petems added a commit that referenced this pull request Jan 31, 2015
Resolve the SSH key path later.
@petems petems merged commit 8f8543a into petems:master Jan 31, 2015
petems added a commit that referenced this pull request Jan 31, 2015
Accidentally introduced failure in #146
petems added a commit that referenced this pull request Jan 31, 2015
There seems to be some confusion around the add-key command, as it just uploads a key to DigitalOcean, not to a machine (See #136, #146)
petems added a commit that referenced this pull request Jan 31, 2015
There seems to be some confusion around the add-key command, as it just uploads a key to DigitalOcean, not to a machine (See #136, #146)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants