bdc67201e2
The React-based rewrite looks whether there's a room name (in the window's location) in order to choose between WelcomePage and Conference. But app.js expects Conference to be rendered before it builds a room name if WelcomePage is disabled and there's no room name. A quick and dirty workaround is to render Conference within WelcomePage so that the rendered result closely resembles index.html before the React-based rewrite. |
||
|---|---|---|
| android | ||
| connection_optimization | ||
| css | ||
| debian | ||
| doc | ||
| fonts | ||
| images | ||
| ios | ||
| lang | ||
| modules | ||
| nwjs-integration | ||
| prosody-plugins | ||
| react | ||
| service | ||
| sounds | ||
| .buckconfig | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .jshintignore | ||
| .jshintrc | ||
| .watchmanconfig | ||
| 404.html | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| analytics.js | ||
| app.js | ||
| authError.html | ||
| base.html | ||
| close.html | ||
| close.js | ||
| close2.html | ||
| conference.js | ||
| config.js | ||
| connection.js | ||
| favicon.ico | ||
| index.android.js | ||
| index.html | ||
| index.ios.js | ||
| interface_config.js | ||
| logging_config.js | ||
| package.json | ||
| plugin.head.html | ||
| title.html | ||
| unsupported_browser.html | ||
| utils.js | ||
| webpack.config.js | ||
README.md
Jitsi Meet - Secure, Simple and Scalable Video Conferences
Jitsi Meet is an open-source (Apache) WebRTC JavaScript application that uses Jitsi Videobridge to provide high quality, scalable video conferences. You can see Jitsi Meet in action here at the session #482 of the VoIP Users Conference.
You can also try it out yourself at https://meet.jit.si .
Jitsi Meet allows for very efficient collaboration. It allows users to stream their desktop or only some windows. It also supports shared document editing with Etherpad.
Installation
Installing Jitsi Meet is quite a simple experience. For Debian-based systems, we recommend following the quick-install document, which uses the package system.
For other systems, or if you wish to install all components manually, see the detailed manual installation instructions.
Building the sources
Jitsi Meet uses Browserify. If you want to make changes in the code you need to install Browserify. Browserify requires nodejs.
On Debian/Ubuntu systems, the required packages can be installed with:
sudo apt-get install npm nodejs-legacy
cd jitsi-meet
npm install
To build the Jitsi Meet application, just type
make
Working with the library sources(lib-jitsi-meet).
By default the library is build from its git repository sources. The default dependency path in package.json is :
"lib-jitsi-meet": "jitsi/lib-jitsi-meet",
To work with local copy you must change the path to:
"lib-jitsi-meet": "file:///Users/name/local-lib-jitsi-meet-copy",
To make the project you must force it to take the sources as 'npm update' will not do it.
npm install lib-jitsi-meet --force && make
Or if you are making only changes to the library:
npm install lib-jitsi-meet --force && make deploy-lib-jitsi-meet
Alternative way is to use npm link.
It allows to link lib-jitsi-meet dependency to local source in few steps:
cd lib-jitsi-meet
# create global symlink for lib-jitsi-meet package
npm link
cd ../jitsi-meet
# create symlink from the local node_modules folder to the global lib-jitsi-meet symlink
npm link lib-jitsi-meet
So now after changes in local lib-jitsi-meet repository you can rebuild it with npm run install and your jitsi-meet repository will use that modified library.
Note: when using node version 4.x, the make file of jitsi-meet do npm update which will delete the link, no longer the case with version 6.x.
If you do not want to use local repository anymore you should run
cd jitsi-meet
npm unlink lib-jitsi-meet
npm install
Discuss
Please use the Jitsi dev mailing list to discuss feature requests before opening an issue on Github.
Acknowledgements
Jitsi Meet started out as a sample conferencing application using Jitsi Videobridge. It was originally developed by then ESTOS' developer Philipp Hancke who then contributed it to the community where development continues with joint forces!