I'm currently doing the new Digital Maker badge with my Cubs and last night I found myself at my friend's Brownie pack doing some of the activities I did (or will be doing) with my Cubs. With only an hour I had to reduce what I was planning but most importantly the girls had fun (rule 0 of Guiding)!
Thanks to a post at http://www.drhevans.com/blog/posts/195-using-ssh-agent-for-sudo-authentication/ I got a starting point, however a few things didn't quite work out (I had to install checkinstall as a prerequisite and edit the client machine user's ssh config) so here's the adjusted instructions (updated Feb 2015).
So I own a VPS (if you can ever really own a VPS) which does a number of things for me. It's backed up by the hosting company, something which requires root access. Now I always worry when giving someone root access, no matter how much I trust them, so the back ups are performed through a simple script which only allows certain commands to be ran, as well as logging all attempts.
The otherday I watched episode 303 of Security Now and Steve has a very interesting take on passwords. Essentially assuming we don't have a dictonary word then it's all about using as many different types of characters as possible. Yes length still matters but entropy (randomness) doesn't.
So I was investigating how to run a rails app on my VPS. I needed to use several sources to get little bit's working, so here's the combined instructions. Note that I assume you're starting with a working apache installation.
On The Server (Once)
I've been playing around with git for a short while now and now I think I've finally got it, or rather the point of it. Ignore those places that discuss it as you commit to your local repository and then commit that the the main repository etc. No it's about letting everyone have a complete copy - in fact you don't even need a central repository to get the benefit of version control - it sits there in a folder on your own PC.
Anyway so here's some sourcves which may help:
