Not a particularly searchable term.
Edit:
The primary weakness of my approach is that for convenience's sake, I rely heavily on apt-get. So hypothetically I'm tied to the debian family. (we use Ubuntu LTS of a couple different versions)
Strictly speaking this disadvantage is unnecessary, you could do all from-source builds using fabric if you wanted. Didn't seem like a constructive use of my time though.
Sample task in my fabfile:
https://gist.github.com/3086836
I'll let you guess from the function name what it does.
The magic word of devops is "idempotence".
While that page has a long list of things they do, the important bits relevant to your comment are
1. a tighter focus on idempotence than Fabric 2. an easy-ish way to integrate package management so you could potentially use the same script to kick off either yum or apt depending on the box
Why the hell would I store anything about deploying one of my projects in /etc/?
Why would I make the same mistake twice? My only real dissatisfaction with Flask is that it cannot handle dispatching its work in parallel. Not a big deal though.
I like knowing exactly how things get done.
For a number of reasons, Debian (or faithful derivatives) comes closest to this of any platform I've encountered.
That said: fabric appears to be little more than a multi-system aware task runner. Somewhat like dsh (distributed ssh / dancer's shell): http://www.netfort.gr.jp/~dancer/software/dsh.html
... or like Capistrano, as the Debian package description suggests (modulo installing Rails).
There's a bad pimp joke around "idempotence" waiting to be made.
Your task here would seem to install Oracle's Java 7 HostSpot JVM.
How do you get around the licensing question(s) (or is that what the "-y" is for)?
> fabric appears to be little more than a multi-system aware task runner.
And C is little more than a portable assembler ;)
Seems to be down right now though.
Also, you need this too: https://github.com/sebastien/cuisine/
