opentok-meet

Opentok app with screen sharing using the WebRTC screen sharing and Archiving features. You can check it out running at meet.tokbox.com.

Running locally

1. If you haven't already, sign up for OpenTok.
2. Clone this repo
3. cp config.json.sample config.json
4. Add your OpenTok apikey and secret to config.json
5. Create your screensharing extensions by following the instructions at https://github.com/opentok/screensharing-extensions and put your Chrome Extension ID in config.json.
6. Run redis
7. npm install
8. If you want to use SSL you will need to generate a key and make sure the server.key and server.crt files are in the main directory. You can find instructions for generating a self-signed certificate here. SSL is recommended so that screen-sharing works and so that you don't have to keep clicking the allow button to allow access to your camera. If you still don't want to use SSL then just update app.js to use http.createServer instead of https.createServer.
9. npm start
10. Go to https://localhost:3000

Running on Heroku

1. If you haven't already, sign up for OpenTok.
2. Create a Heroku instance
3. Clone this repo
4. In the repo run heroku git:remote -a <instance name> to add the remote to github.
5. Add redistogo heroku addons:add redistogo
6. Add your OpenTok API Key and Secret and your Chrome Screensharing Extension ID to the environment heroku config:set HEROKU=true OT_API_KEY=<YOUR_API_KEY> OT_API_SECRET=<YOUR_SECRET> CHROME_EXTENSION_ID=<YOUR_EXTENSION_ID>
7. git push heroku master
8. Visit your heroku URL

##Running Tests

• You can run the unit tests using karma with npm test
• You can run E2E tests using protractor with npm run protractor
  • Make sure that you have started your server npm start
  • Updated protractor.conf.js to point to your local server and your local copy of the screensharing extension for Chrome.
  • Also make sure that your screensharing extension is allowing access to your local server by updating the matches property in the manifest.json file.