Fab for All

29 March 2012

So, you know how you think you're going to get home from the conference and hop on your computer and do all sorts of awesome things like you said you would? And you know how that's complete and utter BS? I came home and collapsed for about a week. Or two.

At PyCon2012, I gave a talk about setting up your first site in the cloud. It was well received, and there were many requests for me to put up my fab files, in spite them being utter crap. Well, I've gone and done that.

The fab files are very rough. I tried to tidy them up a bit, but in the end, ended up hitting commit and hoping for the best. My hope for this repo is:

  • Others will help me improve them
  • I'll get versions for other services
  • I'll get some that work for other frameworks
  • I'll get versions for other setups, like one that uses Gunicon or Varnish
  • I might even get some fancy stuff, like ssh keys and ssl in there!

I'd really like, at the end of the day, to have a set of scripts that are not only functional, but easy to learn from, and easy to use. And I'd really welcome community support on this!

(Sorry about the cross-posts on Planet Django and Planet Python! I usually try to pick one!)


Related tags: django python


1 Markus Gattol says...

Hi Katie,

I've been using fabric tons, it's great no doubt. Not sure if you know ZeroMQ, it's wicked. http://saltstack.org is built around ZeroMQ and caters to the same goal than fabric and fiends. Take a look, it's worth it... ;)

Posted at 1:53 p.m. on March 30, 2012

2 Katie Cunningham says...

@Markus: I had not! I'll have to look at that!

Posted at 2:14 p.m. on March 30, 2012

3 timo says...

in your talk you said you sometimes check in half-ready files because dinner's ready or your children are rampaging around the house or something - there's a git command that might be just right for you!

git stash

will make a "snapshot" (just two commits, really) of both your index and your working copy and then reset your working copy to the commit you are currently on and reset your index. then you can

git stash apply

and you'll be back to before you git stashed and the "snapshot" will still be reachable from your stash. alternatively,

git stash pop

will do the same, but also delete - not unrecoverably - the snapshot.

git stash allows you to have a stack of multiple of those snapshots and you can even apply/pop after moving to a different branch or have made some commits in between (you may need to merge in some cases)

hope to help! - Timo

Posted at 9:40 p.m. on April 2, 2012

4 Katie Cunningham says...


Oh, git stash and I are good friends. I still want the code somewhere else but my local, as I have had a child crater my box so bad, I had to wipe and reinstall.

I only do this for private projects, though, where no one else is dealing with my code.

Posted at 7:26 a.m. on April 3, 2012

5 eng. Ilian Iliev says...

Hi Katie, and thanks for the post and the talk. It was really interesting and helpful. What I can not understand is why you are copying the files "manually" instead of just executing "git pull" on the server? It seems more convenient to me but I would like to hear your thoughts.

Thanks in advance )

Posted at 6:55 a.m. on June 19, 2012

Comments are closed.

Comments have been closed for this post.