<img src=“https://coveralls.io/repos/devdame/DBC-final-project/badge.png” alt=“Coverage Status” />

trUism is a tool to help prospective college students find a school that’s a good culture fit. We listen to social media output on different college campuses and report to you what students are actually talking about.

Check it out! truism.herokuapp.com

Sample Screenshots¶ ↑

System Requirements¶ ↑

• Ruby 2.0.0 p-451

• Rails 4.0.3

• Postgres 9.3.2

• Internet access

External APIs and Libraries¶ ↑

Geofeedia

Location-based social media aggregation and monitoring.

• API: app.geofeedia.com/account/apisetup

• Docs: app.geofeedia.com/Content/APIQuickStartGuide.pdf

AlchemyAPI

Natural Language Processing and sentiment analysis.

• Demo: www.alchemyapi.com/products/demo

• Docs: www.alchemyapi.com/api

D3.js

JavaScript data visualization library utilizing web standards such as SVG, HTML5, and CSS3.

• Gallery: github.com/mbostock/d3/wiki/Gallery

• Docs: github.com/mbostock/d3/wiki

Getting Started¶ ↑

1. Clone to local machine: git clone https://github.com/devdame/DBC-final-project.git campuslyfe

2. Install dependencies: bundle

3. Initialize database: rake db:reset

4. Run server: rails s

5. Visit localhost:3000

Workflow¶ ↑

As a collaborator on this project, I hold myself to high standard of code, commit often, and never push to the master branch.

1. Starting out, or if using a new development workstation:

   git clone https://github.com/devdame/DBC-final-project.git campuslyfe

2. Create new branch for the feature you’re working on:

   git checkout -b Daniel_awesomebranch

3. To bring the local code base up-to-date, first checkout master branch:

   git checkout master

4. Pull in the latest code from the master brach:

   git pull origin master

5. Then switch back to your feature branch before merging code from master:

   git checkout Daniel_awesomebranch

6. Now merge the updated master branch code into your current feature branch:

   git merge master

7. Now you may work on the code for your feature branch. COMMIT OFTEN.

8. When you are ready to submit code to the project repo, go ahead and commit one more time. First include files that were changed:

   git add .

9. Then commit the changes you’ve made:

   git commit -m "Add awesome feature to do awesome thing"

10. Repeat step 3 through 6 to ensure your code base is up-to-date with any changes to master that might have occured in the time you were working on your feature branch. Solve conflicts if present.

11. Push your code to your remote feature branch:

    git push origin Daniel_awesomebranch

12. Submit a pull request on Github for code review.

Database Schema¶ ↑

Running the Test Suite¶ ↑

rspec

Brought to You By¶ ↑

Jay

github.com/jayrogers889csa

Jess

github.com/thejessleigh

Andrew

github.com/Birdrock

Lauren

github.com/devdame

Daniel

github.com/dandydanny