Software & Services


Github: Every student is required to have a Github account. Because Github is free to use for public repositories (which we'll use in this course) there is no need to have a paid Github plan if you don't already have one.

DigitalOcean: In this course we'll use DigitalOcean as our production server provider. Their lowest tier server (aka Droplet) costs $5/month and will be sufficient for our needs. You will need to maintain this server for the duration of the semester.

If this cost is prohibitive, you can sign up for the Github Education Student Developer Pack (SDP) whch will give you $50 in DigitalOcean credits. The SDP has to be approved, so sign up early to avoid missing any deadlines at the start of the semester.

While you can create your DigitalOcean account now, you should not create any Droplets until instructions are provided in Week 2.

If you already have a server provider you will still need to use DigitalOcean, for the reasons listed below under Choosing to use other tools, languages or services.

Operating Systems

Instruction in this course accommodates Mac OS and Windows.

Unix-y users are allowed to take the course, but must be prepared to do independent legwork for the system related instructions given at the beginning of the course. Every semester we typically have a handful of Unix users who we encourage to work together to help one another out.

Administrative Privileges

Because we work with a lot of different software packages in this course, it is expected that you will be able to work on a machine where you have Administrative Privileges. Given this requirement, you will be unable to complete this course using lab or other public computers.


Code Editors You can use whatever code editor you prefer, the following are just suggestions if you don't already have a favorite:

Command Line

These are the command line programs we support in this course:

Local Servers

These are the local servers we'll support in this course:

Other tools or services

In this course we often get questions about using different tools or services than what is suggested in the curriculum.

For example:

The policy on this is always the same: we recommend you stick with the tools we suggest, but if you go off-course, you do so at your own risk.

It would be to your advantage to stick with our suggestions as that's what the lectures will pull from, that's what the notes are on, and that's what the teaching team is trained in. Furthermore, our suggestions have been tested to make sure they accommodate all the goals we have in this course. We'd like to avoid situations where students start off with a piece of software that works for tasks in Week 1 and 2, only to find out that something you need to accomplish in Week 8 can't be done.

Instructions for different platforms can vary greatly, and it is impossible to support all options, especially in a large course. By sticking with set recommendations, we can provide more cohesive instruction and most efficiently help everyone.