datenspuren/jitsi-deployment
datenspuren/jitsi-deployment
6
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc: clarify HTTP vs HTTPS in README

Browse Source
This commit is contained in:
Michael Vorburger ⛑️ 2020-03-13 20:04:29 +01:00 committed by GitHub
parent 8bfe7fbb92
commit d7bb2e66fb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -34,8 +34,10 @@ follow these steps:
* Create a ``.env`` file by copying and adjusting ``env.example``. * Create a ``.env`` file by copying and adjusting ``env.example``.
* `cp env.example .env` * `cp env.example .env`
* Run ``docker-compose up -d``. * Run ``docker-compose up -d``.
* Access the web UI at ``https://localhost:8443`` (or ``http://localhost:8000`` for HTTP, or * Access the web UI at ``https://localhost:8443`` (or a different port, in case you edited the compose file).
a different port, in case you edited the compose file).
Note that HTTP (not HTTPS) is also available (on port 8000, by default), but that's e.g. for a reverse proxy setup;
direct access via HTTP instead HTTPS leads to WebRTC errors such as _Failed to access your microphone/camera: Cannot use microphone/camera for an unknown reason. Cannot read property 'getUserMedia' of undefined_ or _navigator.mediaDevices is undefined_.
If you want to use jigasi too, first configure your env file with SIP credentials If you want to use jigasi too, first configure your env file with SIP credentials
and then run Docker Compose as follows: ``docker-compose -f docker-compose.yml -f jigasi.yml up`` and then run Docker Compose as follows: ``docker-compose -f docker-compose.yml -f jigasi.yml up``