A small tool for better conference Q&A sessions. Presenters can create question sessions and share the link with their audience. Audience members ask questions and upvote questions they like.
- Install Redis.
- Run
npm install. - Create a Twitter application.
- Copy
config.example.jsontoconfig.jsonand replace the values with your own. - Start your server with
npm start.
- PORT: Port the server listens on. Should be 80 in production.
- COOKIE_SECRET: Cookie secret used by express cookie parser.
- COOKIE_KEY: Key in the cookie where session information is stored.
- PERSISTENCE_STRATEGY: If set to "redis" all question and question session data will be stored in Redis and expired after 48 hours. If set to "memory" this data will be kept in local memory and be lost whenever the server is restarted. The memory persistence strategy is intended for test environments and development environments where Redis cannot be installed or persistence is not important.
- TWITTER_CONSUMER_KEY: Key provided by the Twitter application used for authentication/identity.
- TWITTER_CONSUMER_SECRET: Secret provided by the Twitter application used for authentication/identity.
- TWITTER_CALLBACK_URL: URL that Twitter redirects back to after successful authentication. This needs to point to the absolute URL for the
/auth/twitter/callback/path.
These config options may be specified in the config.json file mentioned in the setup above, through environment variables, or through arguments passed node at startup.
Tests can be run with the Testem test runner in TDD mode using npm run tdd or in TAP-output CI mode using npm test.
Copyright © 2014 - Caleb Troughton. Licensed under the MIT license
