Teaching Guide

Elvenware Logo



This is the final for Prog 219 taken June 2015. Many details are perhaps not filled in yet, but this should be enough to get you started.

The core goal is to create a web application that runs on AWS with upstart and links to a MongoDb database running on MongoLab.


The final should be built with HTML, CSS, and JavaScript. It should contain the following elements:


This should be a single page app with the following subpages:


On all pages you should be able to see the name of the currently selected topic. For instance, here we can see the name of the selected scientist:

Subjects Name

On you main page, you might want to show a summary of all the data about a particular topic. Here you can see the bottom portion of the summary information for one scientist:

Summary info

All I want to see at this point is a login page. But ideally, in some later course, we would learn how to allow the user to see the home page, the about page and the login page, but to use the pages that provide the ability to edit data, one would have to be signed in. We are most of the way to getting that done, but we are just out of time.

It would be cool, I suppose, to have two levels of logging in:


The following database features should be included

Jasmine Unit Tests

These will be for extra credit only.

Turn it in

Put the program itsefl in your repository in Week11-Final.

Provide a valid link to the place on AWS where you program is running with upstart. By default it will be: :30027. Just to be clear: it is important that you include specific information on how to find your program running on AWS. A valid link with the correct text in the anchor tag would be good.

Extra Credit

There are several ways to get extra credit.

You can already view a document related to a topic. I want to you to be able to view documents related to each of the subjects associated with a topic. The point is that the user should be able to see an overview document on the home page and then drill into a series of subtopics on the Subjects page.

Suppose your subject was scientists. The user should be able to:


Some hints

REST Calls from Client to Database and Back

Please see this information:

Bootswatch in bower.json

One of your duties as a developer is to make sure that your code can be compiled and run by other developers. Don't leave mistakes in your code, or in package.json, or bower.json, that cause build errors. You should test the code that you check in, and make sure it builds.

In particular, in your bower file, don't write this:

"bootswatch": "~3.3.4+1"

It causes an error when I type bower install. Instead, write this, where the tilde has been removed:

"bootswatch": "3.3.4+1"

Define Scientists

In subdocuments I redefined models/scientists.js. Some of that was probably not necessary and will only be confusing. For now, at least, let export only one Schema, but keep the updates to the comment schema:

var mongoose = require('mongoose');

var comment = mongoose.Schema({
    commentText: String,
    date: { type: Date, default: Date.now }

var scientistsSchema = mongoose.Schema({
    "firstName": String,
    "lastName": String,
    "subject": String,
    "subjects": [String],
    comments: [comment]

module.exports = mongoose.model('scientist', scientistsSchema);


There are a number of ways to solve this. One is:

cd ~/bin
ln -s ~/Git/prog219-lastName/Week11-Final final;

When everything is set up, test your work:

sudo start final

Then go to the appropriate URL and test your work. For problems, check /var/log/final.conf.

Jasmine and $httpBackend

I have added at least a little more text to my explanation of $httpBackend:

Press F5 a few times to make sure you have the most recent copy if you are going back to that page after viewing it recently.


This video shows one way to handle the login functionality in your application. This is not the only possible solution. You can do it differently, but if you are not sure what is wanted, this gives you an idea of what to shoot for.

A working example of how to handle the SignIn program is in the following directory: