This repository contains multiple projects from the Udacity's Fullstack Nanodegree organized into a Vagrant VM.
To install we simply clone this repository and let Vagrant do the VM install and provisioning.
git clone https://github.com/tomca32/fullstack-nanodegree-vm.git
cd fullstack-nanodegree-vm/vagrant
vagrant up
#... wait for a while...To run the application you need to ssh into a running vagrant instance and start the app:
vagrant ssh
cd /vagrant/catalog
python run.pyThis will start the application at the port 5000. Simply open your browser and direct it to localhost:5000
You can reset and seed the database by running:
vagrant ssh
cd /vagrant/catalog
python seed.pyWithout being logged in, you can browse the catalog but you cannot make any changes. Add, Edit and Delete buttons are not shown and trying to visit the URL for those actions wil result in 401. You can login with any Google account using the button in the top right of the application.
Items can contain an image. No image itself is contained in the application but the image url can be passed during item creation. There is no URL validation present, so if there is no image in the URL, a broken image will be displayed.
There are endpoint for JSON and XML formats. Prefix all endpoints with the application URL (localhost:5000 by default):
| Endpoint | Format | Result |
|---|---|---|
| /json | JSON | All categories with all items |
| /category/:category_name/json | JSON | specific category and its items |
| /category/:category_name/item/:item_name/json | JSON | specific item |
| /item/:item_id/json | JSON | specific item (alternate path if item id is known) |
| /xml | XML | All categories with all items |
| /category/:category_name/xml | XML | specific category and its items |
| /category/:category_name/item/:item_name/xml | XML | specific item |
| /item/:item_id/xml | XML | specific item (alternate path if item id is known) |
To run the tests we need to ssh into a running vagrant instance, seed the database and run test script
vagrant ssh
cd /vagrant
./seed.sh
python tournament_test.pyContains all the basic functionality required by the original test suite and contains additional functionality:
- tournament can handle odd number of players. In this case one of tuples in the list from swissPairings() is going to return a tuple containing one player. This there are no API changes.
There are only 2 tables in the database: players and matches:
- players has two columns, id (primary key) and name
- matches has three columns, id (primary key), players (array of players participating in the match)* and winner which is an id of the winner and is a foreign key referencing the id in the players table
*I wanted to make the elements of this array foreign keys referencing the players table but it seems that it cannot be done: http://dba.stackexchange.com/questions/60132/foreign-key-constraint-on-array-member
There are also 3 views:
- wins_by_player returns three columns: player id, player name and number of wins sorted by number of wins descendingly
- matches_by_player returns three columns: player id, player name and number of played matches sorted by number of matches descendingly
- player_standings returns four columns: player id, player name, number of wins and number of matches played