May 15, 2014
There was one thing I didn’t mention in my previous post about running Octopress on a Vagrant machine — in the machine’s current state (with Windows as a host machine), we cannot deploy the site with a
rake deploy command. The reason for this is we don’t have an ssh key available to the Vagrant box.
While we could create new keys on the Vagrant machine, this kind of seems to defeat part of the purpose of using Vagrant (setting up a development environment with little manual interaction). Additionally, we could simply share our host machine’s ~/.ssh folder with our vagrant machine but this also seems kind of messy.
Thankfully, there is a pretty simple way to get everything working to where we can use the host machine’s ssh key and that is through an ssh-agent. In the Vagrantfile we setup as part of the previous post, we are already giving our machine access to the ssh-agent with the following command
config.ssh.forward_agent = true. The only problem with this forward_agent property is that you may not have an ssh-agent running (especially if you are on Windows). There are a couple things we can do to get around that…
eval `ssh-agent`followed by
ssh-add(assuming your keys are idrsa/idrsa.pub) — You’d connect to your Vagrant machine after running this command and would be able to deploy, however, there are a couple of problems with this method. First off, this is a manual process you’d have to remember every time you wish to deploy. Another issue is that you have an ssh-agent process that you need to remember to get rid of down the road.
ssh-addto the .profile would allow us to automate the process of starting the agent when loading the terminal. That being said, using the
evalscript would be bad — it would create a new ssh-agent each time a new shell is loaded. Thankfully, GitHub has shared a solution to this problem.
I generally stick with option 2, as I am not much of a PowerShell user. It’s definitely nice to have the PowerShell option available as a backup, however. One thing I would really like to explore a bit more is making this working with cmder. I could not get the agent to run when using cmder (without having it launch PowerShell) but I did not spend much time on that yet.
If you want to test to make sure that your ssh-agent is running and getting shared to your vagrant machine…
vagrant upfollowed by
ssh -T firstname.lastname@example.org
If everything is working you should see:
Hi _______! You've successfully authenticated, but GitHub does not provide shell access.