-
Notifications
You must be signed in to change notification settings - Fork 52
Home
James Baicoianu edited this page Apr 18, 2016
·
9 revisions
To check out your own copy of JanusWeb, perform the following steps:
git clone -b next https://github.com/jbaicoianu/elation.git
cd elation
./elation web init
git clone https://github.com/jbaicoianu/elation-engine.git components/engine
git clone https://github.com/jbaicoianu/cyclone-physics-js.git components/physics
git clone https://github.com/jbaicoianu/elation-share.git components/share
git clone https://github.com/jbaicoianu/janusweb.git components/janusweb
./elation component enable engine physics share janusweb
Once you have performed these steps, change to the components/janusweb
directory and edit scripts/config.js
. For example, if you intend to host your own copy of JanusWeb at http://www.myserver.com/janusweb/
the following settings would be used:
elation.config.set('dependencies.protocol', 'http:'); // "http:" or "https:"
elation.config.set('dependencies.host', 'www.myserver.com'); // Hostname this release will live on
elation.config.set('dependencies.rootdir', '/janusweb/'); // Directory this release will live in
elation.config.set('dependencies.main', 'janusweb.js'); // The main script file for this release
elation.config.set('janusweb.network.host', 'wss://janusweb.lnq.to:5567'); // Default presence server
elation.config.set('janusweb.network.corsproxy', 'http://janusweb.lnq.to:8089/'); // CORS proxy URL
elation.config.set('janusweb.tracking.enabled', false);
elation.config.set('janusweb.tracking.clientid', '');
Once these config settings are saved, run npm run build
to generate a release in the build/
directory. Copy these files to their final location (eg, http://www.myserver.com/janusweb/) and you should be ready to go.