DevOps Zone is brought to you in partnership with:

Full-time developer on a small team. Writing great specs and code, delivered on time. Chase is a DZone MVB and is not an employee of DZone and has posted 53 posts at DZone. You can read more from them at their website. View Full User Profile

Writing a cURL to Python Install Script for a Django Development Environment

09.10.2013
| 1905 views |
  • submit to reddit

Paste and Pray

It’s pretty common to Google a technical issue and come up with a blog or a StackOverflow article that promises to fix the issue by copying and pasting a simple one-liner into a terminal. At first it’s just a quick chmod, or a simple apt-get. It’s completely unsafe unless you know exactly what the command is doing, but it’s pretty damn effective. Then you graduate to doing few lines at a time without really thinking about it too much, like a bad drug habit. Repetition slowly convinces you that it’s not insane.

In the last couple of years, I’ve seen a few extreme versions of this same idea, but taken to the next level. Homebrew can be installed by running:

ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go)"

Heroku Toolbelt for Linux is just a

wget -qO- https://toolbelt.heroku.com/install-ubuntu.sh | sh

away. I call these Paste and Pray installers.

Sounds like fun, right? I thought so, so I came up with a version that installs a pretty vanilla Django development environment, from scratch. It doesn’t assume anything except cURL and Python, both of which come pre-installed on OSX and Ubuntu. It does a fully automated install of Homebrew (including its dependency XCode on OSX), as well as pip, virtualenv, your code from GitHub, Django and any other Python requirements you have. It also sets some environment variables and updates your hosts file.

Oh, did I mention that some of these steps require root access? That’s right! It’s more like Super Paste and Pray™.

Note: this code is not intended to be directly re-usable. Instead, I thought I would share what I learned while writing it.

The Code

You can view the code and documentation. The code itself can be run with

curl -fsS https://raw.github.com/chase-seibert/paste-and-pray/go/run.py |sudo -E python

You should be able to modify it pretty easily for any Django app.

Sh Stuff

Although I didn’t want any dependencies required for the installer itself, I did want to take this chance to play around with sh, a nice Python API for interfacing with the shell. Because I could not rely on pip to be installed, I just downloaded this dependency right in Python:

urllib.urlretrieve("https://raw.github.com/amoffat/sh/master/sh.py", "sh.py")
sh = imp.load_source("sh", "sh.py")

Working with sh turned out to be a little trickier than I imagined. First off, many of my commands required root access. The easiest method was to start the script with sudo and wrap any steps that did not require root in a sudo -E -u username prefix. This is exactly what sh.bake is for.

I found it useful to redirect _out to sys.stdout for trouble-shooting purposes. Similarly, if you need to take user input, you will need to redirect stdin with something like:

def raw_input_tty(name, prompt):
    ''' the main use case for this script has the user piping in the results from
    a curl; which over-rides stdin. But we also want to interactively prompt the user
    for some input, so dynamcially switch back to tty. '''
    sys.stdin = open('/dev/tty')
    return raw_input(prompt)

Sudo Madness

Initially, I had tried calling setuid to downgrade to a non-root user. But, I was not able to go back to root, meaning that you would need to do all the root steps in one chunk, then do all the non-root stuff. This was a show-stopper since the Homebrew install step must be run as a regular user, but subsequent pip and virtualenv tool installs required root.

Another wrinkle was getting the original username from inside sudo. This was simple, though I did need to hunt around before I discovered that both OSX and Linux set a SUDO_USER environment variable for just this purpose.

OSX Stuff

Installing Homebrew manually is straightforward, but does require the XCode command line tools to be installed first. Normally, this is a headache because you have to create an Apple ID and hunt and peck trough their developer website for a binary installer.

It turns out there there are direct download links, they just are not publicized. Here is some Python code to download and install the correct version.

def install_xcode(osx_version):
    # see: https://devimages.apple.com.edgekey.net/downloads/xcode/simulators/index-3905972D-B609-49CE-8D06-51ADC78E07BC.dvtdownloadableindex
    downloads = {
        10.7: "http://devimages.apple.com/downloads/xcode/command_line_tools_for_xcode_os_x_lion_april_2013.dmg",
        10.8: "http://devimages.apple.com/downloads/xcode/command_line_tools_for_xcode_os_x_mountain_lion_april_2013.dmg",
    }
    if osx_version not in downloads:
        raise NotImplementedError("Could not locate XCode download for OSX %s" % osx_version)
    download_file = downloads.get(osx_version)
    # save this OUTSIDE the normal tmp dir; in case we need to restart install
    dmg_file = "/tmp/xcode.dmg"
    if not os.path.exists(dmg_file):
        urllib.urlretrieve(download_file, dmg_file)
    volume_dir = "/tmp/xcode"
    if not os.path.exists(volume_dir):
        sh.hdiutil("attach", "-mountpoint", volume_dir, dmg_file)
    mpkg_file = [f for f in os.listdir(volume_dir) if f.endswith(".mpkg")][0]
    try:
        sh.installer("-pkg", os.path.join(volume_dir, mpkg_file), "-target", "/")
    except sh.ErrorReturnCode as e:
        print e.stderr
    finally:
        sh.hdiutil("detach", volume_dir)

As I said, the Homebrew install is easy. I did have to include a small fixup gist to get it to work on one of my test machines.

Python Stuff

Working with Python made a lot of the script easier. Specifically, working with sh made tasks like getting the list of items currently installed by brew pretty simple:

installed = self.sh.brew("list", "-1").split("\n")
not_installed = list(set(self.dependencies) - set(installed))

It also allows chaining, just like in a bash shell:

sh.grep(sh.cat("/etc/hosts"), HOST_NAME)

One area that was a little tricky was activating virtualenv from inside Python. However, there is actually a supported method for this.

activate_this = '/path/to/env/bin/activate_this.py'
execfile(activate_this, dict(__file__=activate_this))

GitHub Stuff

For the shortest URL possible, you can set the default branch in GitHub to be something short, like “go”. Looking at the homebrew installer, I noticed that it’s possible to leave the file name off, too. GitHub’s raw file service apparently picks the first file by alphabetical order if you do this. However, I didn’t want to mess with trying to get my code to show up alphabetically before .gitignore, so I skipped this optimization.

Final Thoughts

Random other thoughts on writing installers:

  • Create a temp directory if you need to do anything like download files.
  • Make the installer idempotent; you want to be able to retry cleanly.
  • Checking whether a step has already been run is a good idea.
  • Don’t try to hide the debug output, at least for a development audience.


Published at DZone with permission of Chase Seibert, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)