Using Phoenixforge

This course uses Phoenixforge to collect homeworks, projects, and paper responses and to distribute the support code you will need to do the projects.

Phoenixforge is based on the Subversion version control system (SVN). There are SVN tutorials online, including here, and here and here. You can search for svn tutorial and svn introduction to find others. The canonical reference is the SVN book here, which includes HTML and PDF versions; you might want to review Chapter 1.

Instructions

As a student in the class, you should have your own Phoenixforge SVN repository visible at: https://phoenixforge.cs.uchicago.edu/projects/[insert your CNetID here]-cs232-aut-14. Make sure this URL is accessible. If it's not, contact a member of the course staff.
To get started, you will need to create a parent directory and then check out your repository. Create the parent directory with the following commands:
```
mkdir cs232
chmod 700 cs232
cd cs232
```
The chmod 700 command ensures that only you have permission to access to your work. (You are responsible for taking steps to prevent others from copying your work.) Then, check out the code:
```
svn checkout https://phoenixforge.cs.uchicago.edu/svn/[insert your CNetID here]-cs232-aut-14
```
You may be prompted to accept the TLS certificate for the Phoenixforge server. If you're paranoid (as you should be in this course!), check that the certificate fingerprint is equal to F6:7C:48:D0:FD:8B:28:45:59:C4:28:F4:18:87:B0:F9:14:A4:BF:C9. If it is, then enter 'p' to permanently accept it. If it's not, let the course staff know! (You will learn what this all means in this class soon enough!) You will then be prompted for your CNet password.
As each assignment is handed out, the course staff will create a directory in your SVN repository (e.g., hw1 for Homework 1) containing the files you will need to get started. These might include homework submission templates or support code. To fetch the latest assignment directories and files, use the svn update command.
When working on an assignment, modify the files in its directory. To add a new file named X for the first time, type svn add X
When you have a set of modifications and added files that you would like to save and upload to Phoenixforge, type svn commit. You will be prompted to write a short "commit message" describing this set of changes (e.g., "Implement function foo()"). You can run svn commit as many times as you like.
We will assume that the last revision you commit before the due date (assuming you're not using any late days) is the one you are turning in. When you're finished with the assignment, make sure that all your work has been committed by typing svn status. This command lists files that have uncommitted modifications (marked with an M), as well as files that have not been added or committed (marked with a ?). Run svn add and svn commit as needed to ensure that all your work has been committed.
As an added check that the files you think have been handed in really have been handed in, examine the contents of your repository on the Web at: https://phoenixforge.cs.uchicago.edu/projects/[insert your CNetID here]-cs154-2014/repository. To help you, each assignment directory in your repository contains a file named 00-checkme.html that contains a link to a Web page that shows the contents of that directory in your repository. Use this to confirm what the graders will see when they collect your files and to make sure that you have not submitted an empty (0 byte) file by accident.