DebateVid.io is a centralized repository for parliamentary, policy, and Lincoln-Douglas debate videos.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci
app
bin
config
db
lib/tasks
log
public
spec
.babelrc
.codeclimate.yml
.eslintrc.json
.gitignore
.node-version
.rspec
.rubocop.yml
.ruby-version
Gemfile
Gemfile.lock
LICENSE.txt
Procfile
Procfile.dev
README.md
Rakefile
browserslist
config.ru
package.json
yarn.lock

README.md

Build Status Test Coverage Code Climate security

DebateVid.io

DebateVid.io is a centralized repository for parliamentary, policy, and Lincoln-Douglas debate videos.

Development

DebateVid.io is built on Ruby on Rails and uses yarn for frontend assets.

Setup

  1. Clone the repository (git clone git@github.com:schneidmaster/debatevid.io.git)
  2. Install gems: bundle install
  3. Install packages: yarn install
  4. Start the Rails and webpack servers: foreman start -f Procfile.dev

Configuration

DebateVid.io uses dotenv to manage configuration. Specifically, client IDs and secret keys for Facebook, Twitter, and Google as well as the API key for YouTube are kept in a local file excluded from the Git repository. To set up your application for development, you need to first create test applications on the Facebook, Twitter, and Google developer portals. Then, generate the appropriate keys and create a file named .env in the application root directory with the following contents:

FACEBOOK_KEY=################
FACEBOOK_SECRET=################
TWITTER_KEY=################
TWITTER_SECRET=################
GOOGLE_KEY=################
GOOGLE_SECRET=################
YOUTUBE_DEV_KEY=################

In the production environment, the Rails secret key base and database password are also kept in the application environment:

SECRET_KEY_BASE=################
DB_PASSWORD=################

Staging/Production Configuration

On Heroku, DebateVid.io requires both the node buildpack (for webpack/asset compilation) and the ruby buildpack. Add them with:

heroku buildpacks:clear
heroku buildpacks:set heroku/nodejs
heroku buildpacks:add heroku/ruby --index 2

Contributing

  1. Fork it (https://github.com/schneidmaster/debatevid.io/fork)
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

License

MIT