latest 20 messages by e1nh4nd3r

+ [2014-01-25T18:39:00Z] e1nh4nd3r I guess if you're juggling multiple keys on the keychain that might be problematic if you're using something like fail2ban that blocks you if you hit it with too many login attempts with the wrong ssh key...
+ [2014-01-25T18:37:59Z] e1nh4nd3r I don't know, I think that most folks that would be deploying via rsync would want to use keys to secure the user that they are using to deploy with.
+ [2014-01-25T18:36:35Z] e1nh4nd3r Created https://github.com/imathis/octopress/issues/1484 to at least get a thread going.
+ [2014-01-25T18:36:02Z] e1nh4nd3r And we can define ssh_keys that way.
+ [2014-01-25T18:35:53Z] e1nh4nd3r At my job, for one particular recovery method we need rsync for, we do --rsync-command="/usr/bin/sudo /usr/bin/ssh (OPTIONS)"
+ [2014-01-25T18:35:11Z] e1nh4nd3r I think if you define --rsync-command, it does.
+ [2014-01-25T18:25:36Z] e1nh4nd3r I'd imagine it's a something to do with rsync_options in the rakefile, but I'm not quite sure about how to achieve that.
+ [2014-01-25T18:24:51Z] e1nh4nd3r Anyone have a way to set a different ssh key with 'rake deploy' rsync method other than .ssh/id_rsa or whatever's in the ssh keychain?
+ [2014-01-21T02:45:39Z] e1nh4nd3r Nope, that's not it...
+ [2014-01-21T02:42:08Z] e1nh4nd3r Hmm. I wonder if the dir needs to be owned by www-data...
+ [2014-01-21T02:38:39Z] e1nh4nd3r Do I need to specify a "location" block in my sites-available/<sitename> configuration file for EVERY sub-directory I'm trying to hit?
+ [2014-01-21T02:30:38Z] e1nh4nd3r Ahhh... this is interesting. "curl: (7) Failed connect to (REDACTED):8080; Connection refused"
+ [2014-01-21T02:29:46Z] e1nh4nd3r Hm, okay... so it's not Varnish. Varnish is throwing a miss, nginx isn't serving the directory.
+ [2014-01-21T02:13:34Z] e1nh4nd3r Odd. ./public/blog/archives on my site seems to not serve
+ [2014-01-21T02:04:23Z] e1nh4nd3r Just a misunderstanding on my part of what the software actually does.