Running a Development Environment

Go up to the main SLP documents page (md)

There are a number of ways to run a development environment that will allow you to do the work in this course. They are all listed below; choose the one that you feel will work best for you. There is no one particular solution that is better than the others -- they all have pros and cons.

With both VirtualBox and Docker, you have two operating systems -- the 'host' machine (what booted your computer) and the 'guest' machine (what is running in VirtualBox or Docker).

VirtualBox image

We have a VirtualBox image all created that has the necessary software installed. This is very similar to the image used in CS 2150 in the past. Due to updated versions of the software, however, you should not use your old CS 2150 image. The image will require a XXX Gb download; once uncompressed, it will take up about XXX Gb on your machine.



Docker image

We have a docker image ready for you to use. To download it, do XXX. You download a docker image, and when run, it's called a container (you can run many containers from the same image). Note that once a container is destroyed, ALL files on that container are removed; if you start up another container from an image, then you get the default files.



Install your own

You can install everything on your own machine. While we can help if you run into problems, we may not be able to debug everything if you run into an oddball problem.

Run on the course server

You are certainly welcome to run your code on the course server, which is all set up for the software needed in this course. You can configure a copy of the project in your own user directory, and test it there. You can NOT edit live code as part of your development.