This is the currently the only front end for creating scenes and playing scenes. For this to work you'll also need a running copy of a MediaHub, and an AssetStore.
Setup your MediaHub and AssetStore first if you haven't done so already.
Copy the file env-example.sh to env.sh. Set the ASSET_STORE and MEDIA_HUB exports to the url's of where those are running (if you're developing locally then just leave the defaults, as those services should default to those ports when running).
DEBUG - Allows console logs to be stripped out and other development build processes
Node v4.4.7 and npm v2.15.8. Install the needed npm packages:
npm install
Start the local development server:
./env.sh gulp
The shell script merely provides the appropriate environment variables for whatever is specified after it.
The default gulp task handles a number of things for us:
- bundling the javascript
- copying the js/html/css to a
dist/directory - starting up a local webserver to serve it with
- watching filesystem for changes, then bundling and copying again
Now you may access the editor at http://localhost:3000 and the viewer at http://localhost:3000/viewer.html
This whole repo is currently setup to be deployed as an Azure Website. The deploy.sh file is used by KuduSync.
However, you can easily deploy it elsewhere. Just run the build-dist gulp command:
env.sh gulp build-dist
The copy the contents of dist/ to whereever you'd like to host the files.
Integration tests for the HubClient testing out socket listeners
--require mock-local-storage allows us avoid the global and window variables such as localStorage from blowing up tests
./dev-env.sh mocha --require mock-local-storage test/integration/test-hub-client.js