How do you set up the Digital Ocean or AWS server?

mb

Requirements:

Section

• Feature

Title

• The group name.
• The group members.

Introduction
What is the problem?
What are the use cases?

Design

• RESTful API

Tools

• front-end
• back-end
• embedding-media services

Hosting

• How do you set up the Digital Ocean or AWS server?

Other

• Proof-read your report. Get another group to read it. Read it aloud.

Create diagrams with captions.
Create sections and subsections effectively.

description of the site, its purpose, its intended users
the group name
the group members

for each member:
name
photo
bio
major responsibilities
no. of commits
no. of issues
no. of unit tests

stats:
total no. of commits
total no. of issues
total no. of unit tests
a link to the Apiary API
a link to the GitHub Issue Tracker
a link to the GitHub Repo
a link to the GitHub Wiki

data:
links to the data sources
description of how each was scraped

tools:
tools used
describe their use
special focus on optional tools that were not required

Once we are complete with phase 1 we need to PR dev into master and have digital ocean serve master

for each model, a page that contains a
table of all of the instances of that model
with at least five columns of attributes of that model
with the ability to sort the table using any of the columns
in ascending or descending order and
with links to those instances
right now with only three rows
but eventually with many rows and pagination

Github metrics up to date?
Any details about building startup fairy we need to change?

We're not displaying enough attributes in the tables.

Relevant piazza https://piazza.com/class/iryccp26g9wou?cid=245

ReactJS vs Angular 2

Edit: Kirstine Domingo said it's not necessary for phase 1 but recommended for sortable tables requirement

May require
updating makefile
updating test files

Create a set of static HTML pages for three crises, three organizations, and three people that displays all of the data collected.
The pages must be served by using Flask to embed the static content into the HTML.

Currently makefile is empty.

$ find . -type f -name '*.md' | xargs wc -w

carousel
make it beautiful
with a way to navigate among the pages

for each model, a page that contains a
table of all of the instances of that model
with at least five columns of attributes of that model
with the ability to sort the table using any of the columns
in ascending or descending order and
with links to those instances
right now with only three rows
but eventually with many rows and pagination

RESTful API

Add more content? Change the links? Do the nav buttons match the links on the splash page
Close if there is no changes need to be made

Not all of our models have at least 5 properties we can display in a table

We need to also have the doc files created by one of these commands

Then we can fill our database with data from them

front-end
back-end
embedding-media services

https://docs.google.com/document/d/1pe2OrfFYmpHcV4SvOCGWcSfo1RfXIdMKAxv_MQb3Q2c/edit?usp=sharing

See #48

Title

• The group name.
• The group members.

Introduction

• What is the problem?
• What are the use cases?

I disabled the hamburger menu temporarily.

Each model (or "category") has a table associated it. On the category page, we ant to be able to select a category and display the appropriate content.

Create a UML class diagram of the models using yUML
The diagram needs to show data members, methods, associations and multiplicity between the models.

Videos
Maps
Social Networks
Embed images

for each member:
name
photo
bio

Write unit tests in tests.py that test corner cases and failure cases until you have an average of 3 tests for each function/method, confirm the expected failures, and add, commit, and push to the PUBLIC code repo.

Repository has been imported into Travis-ci, but .travis.yml is empty. Fill out .travis.yml.

Please also disable email notifications.
Link to travis: https://travis-ci.org/cs373gc-fall-2016/TBD

for each model, a page that contains a
table of all of the instances of that model
with at least five columns of attributes of that model
with the ability to sort the table using any of the columns
in ascending or descending order and
with links to those instances
right now with only three rows
but eventually with many rows and pagination

Blocked by project proposal, unsure if it is also necessary in phase 1 anyways

Tests cannot be run in this phase but they do need to be designed

for each model, a page that contains a
table of all of the instances of that model
with at least five columns of attributes of that model
with the ability to sort the table using any of the columns
in ascending or descending order and
with links to those instances
right now with only three rows
but eventually with many rows and pagination

columns by category
add clickable links to show details
display each item in a cell if it is a list properly (doesn't show commas where needed)