# HG changeset patch # User Steve Losh # Date 1309440381 14400 # Node ID 07a50b67d5cd5641e0bc80aa85a5059d8443b421 # Parent a15f1a3cf6916e32ed7eb171c206215b53f38ccc A couple of updates to the Django entry. diff -r a15f1a3cf691 -r 07a50b67d5cd content/blog/2011/06/django-advice.html --- a/content/blog/2011/06/django-advice.html Thu Jun 30 09:16:20 2011 -0400 +++ b/content/blog/2011/06/django-advice.html Thu Jun 30 09:26:21 2011 -0400 @@ -72,6 +72,10 @@ to learn and use an automated provisioning system. Support for Puppet and Chef is built in. I chose Puppet, but if you prefer Chef that's cool too. +You can also use other tools like Fabric or some simple scripts, but I'd strongly +recommend giving Puppet or Chef a fair shot. It's a lot to learn, but they're both +widely tested and very powerful. + Because you're developing against a VM and deploying to a VM, you can reuse 90% of the provisioning code across the two. @@ -722,7 +726,8 @@ Luckily [BCVI][] exists. It's a utility that opens a "back channel" to your local machine when you SSH and lets you run `vi FILE` to open that file in -Vim/MacVim/GVim/etc on your *local* machine. +Vim/MacVim/GVim/etc on your *local* machine. When you save the file it uploads it +back to the server automatically for you. It can be a bit tricky to set up, but it's worth it. Trust me.