[jitsi-dev] Trying to build Jitsi-Meet


#1

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and `make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!


#2

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

···

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and `make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

I first tried with no server, that is, just opening index.html in
chrome. Then I tried with `python -m SimpleHTTPServer` and went to
localhost:8000 but still no luck.

···

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and `make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Here is the GET issued at the python server:

127.0.0.1 - - [26/Mar/2018 23:22:15] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET /css/all.css HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/lib-jitsi-meet.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/app.bundle.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:16] "GET /favicon.ico HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
/libs/do_external_connect.min.map HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/lib-jitsi-meet.min.map
HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/app.bundle.min.map
HTTP/1.1" 200 -

···

On 3/26/18, eyal land <eyal3002@gmail.com> wrote:

I first tried with no server, that is, just opening index.html in
chrome. Then I tried with `python -m SimpleHTTPServer` and went to
localhost:8000 but still no luck.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and `make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#5

Hi,

This will not work that way. You need a webserver that supports ssi
(nginx, apache2 ... ) and https. Webrtc work when used with https
connection only, not sure whether `python -m SimpleHTTPServer`
supports https endpoints.
If you want to run it with some other webserver it should have https,
and if it doesn't support ssi you need to modify index.html and
replace ssi directives with standard script src tags, for example,
https://github.com/jitsi/jitsi-meet/blob/master/index.html#L132 should
be <script src="config.js"/>.

Regards
damencho

···

On Mon, Mar 26, 2018 at 3:28 PM, eyal land <eyal3002@gmail.com> wrote:

Here is the GET issued at the python server:

127.0.0.1 - - [26/Mar/2018 23:22:15] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET /css/all.css HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/lib-jitsi-meet.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/app.bundle.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:16] "GET /favicon.ico HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
/libs/do_external_connect.min.map HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/lib-jitsi-meet.min.map
HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/app.bundle.min.map
HTTP/1.1" 200 -

On 3/26/18, eyal land <eyal3002@gmail.com> wrote:

I first tried with no server, that is, just opening index.html in
chrome. Then I tried with `python -m SimpleHTTPServer` and went to
localhost:8000 but still no luck.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and `make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#6

Thanks, I've settled for now on using webpack-dev-server, does the job.

···

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This will not work that way. You need a webserver that supports ssi
(nginx, apache2 ... ) and https. Webrtc work when used with https
connection only, not sure whether `python -m SimpleHTTPServer`
supports https endpoints.
If you want to run it with some other webserver it should have https,
and if it doesn't support ssi you need to modify index.html and
replace ssi directives with standard script src tags, for example,
https://github.com/jitsi/jitsi-meet/blob/master/index.html#L132 should
be <script src="config.js"/>.

Regards
damencho

On Mon, Mar 26, 2018 at 3:28 PM, eyal land <eyal3002@gmail.com> wrote:

Here is the GET issued at the python server:

127.0.0.1 - - [26/Mar/2018 23:22:15] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET /css/all.css HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/lib-jitsi-meet.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/app.bundle.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:16] "GET /favicon.ico HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
/libs/do_external_connect.min.map HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/lib-jitsi-meet.min.map
HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/app.bundle.min.map
HTTP/1.1" 200 -

On 3/26/18, eyal land <eyal3002@gmail.com> wrote:

I first tried with no server, that is, just opening index.html in
chrome. Then I tried with `python -m SimpleHTTPServer` and went to
localhost:8000 but still no luck.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and `make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#7

The "Running with webpack-dev-server for development" section on
README states that:

By default the backend deployment used is beta.meet.jit.si, ...

and later that the app is running on localhost:8080.

My question is, what is meant by the "backend deployment"? More
generally, what are the moving parts here, in what way does jitsi-meet
use jotsi-videobridge? How does the big picture looks? What's the
architecture behind the jitsi-meet webapp?

Sorry for all the questions, but I really want to understand the whole
design of the system, and I couldn't find an Architecture or a Code
Layout documentation page anywhere.

···

On 3/27/18, eyal land <eyal3002@gmail.com> wrote:

Thanks, I've settled for now on using webpack-dev-server, does the job.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This will not work that way. You need a webserver that supports ssi
(nginx, apache2 ... ) and https. Webrtc work when used with https
connection only, not sure whether `python -m SimpleHTTPServer`
supports https endpoints.
If you want to run it with some other webserver it should have https,
and if it doesn't support ssi you need to modify index.html and
replace ssi directives with standard script src tags, for example,
https://github.com/jitsi/jitsi-meet/blob/master/index.html#L132 should
be <script src="config.js"/>.

Regards
damencho

On Mon, Mar 26, 2018 at 3:28 PM, eyal land <eyal3002@gmail.com> wrote:

Here is the GET issued at the python server:

127.0.0.1 - - [26/Mar/2018 23:22:15] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET /css/all.css HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/lib-jitsi-meet.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/app.bundle.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:16] "GET /favicon.ico HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
/libs/do_external_connect.min.map HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/lib-jitsi-meet.min.map
HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/app.bundle.min.map
HTTP/1.1" 200 -

On 3/26/18, eyal land <eyal3002@gmail.com> wrote:

I first tried with no server, that is, just opening index.html in
chrome. Then I tried with `python -m SimpleHTTPServer` and went to
localhost:8000 but still no luck.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and
`make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#8

Hi,

I cannot remember of a detailed document description of all. But here
is some schema:
https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md
You can see jitsi-meet there which is the web app and everything else
it the backend. Jitsi-meet connects to XMPP server from where it
communicates with the other participants and with jicofo, which is the
JItsiCOnferenceFOcus which orchestrates the conference. And
jitsi-videobridge is an SFU which is responsible for receiving the
media (audio/video) from the clients and forwarding it to the
appropriate participants.
This is the architecture in two sentences.

Regards
damencho

···

On Tue, Mar 27, 2018 at 10:47 AM, eyal land <eyal3002@gmail.com> wrote:

The "Running with webpack-dev-server for development" section on
README states that:

By default the backend deployment used is beta.meet.jit.si, ...

and later that the app is running on localhost:8080.

My question is, what is meant by the "backend deployment"? More
generally, what are the moving parts here, in what way does jitsi-meet
use jotsi-videobridge? How does the big picture looks? What's the
architecture behind the jitsi-meet webapp?

Sorry for all the questions, but I really want to understand the whole
design of the system, and I couldn't find an Architecture or a Code
Layout documentation page anywhere.

On 3/27/18, eyal land <eyal3002@gmail.com> wrote:

Thanks, I've settled for now on using webpack-dev-server, does the job.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This will not work that way. You need a webserver that supports ssi
(nginx, apache2 ... ) and https. Webrtc work when used with https
connection only, not sure whether `python -m SimpleHTTPServer`
supports https endpoints.
If you want to run it with some other webserver it should have https,
and if it doesn't support ssi you need to modify index.html and
replace ssi directives with standard script src tags, for example,
https://github.com/jitsi/jitsi-meet/blob/master/index.html#L132 should
be <script src="config.js"/>.

Regards
damencho

On Mon, Mar 26, 2018 at 3:28 PM, eyal land <eyal3002@gmail.com> wrote:

Here is the GET issued at the python server:

127.0.0.1 - - [26/Mar/2018 23:22:15] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET /css/all.css HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/lib-jitsi-meet.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/app.bundle.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:16] "GET /favicon.ico HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
/libs/do_external_connect.min.map HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/lib-jitsi-meet.min.map
HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/app.bundle.min.map
HTTP/1.1" 200 -

On 3/26/18, eyal land <eyal3002@gmail.com> wrote:

I first tried with no server, that is, just opening index.html in
chrome. Then I tried with `python -m SimpleHTTPServer` and went to
localhost:8000 but still no luck.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and
`make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#9

Thanks. So my server is there only to serve the React UI, right? The
real meat is happening on beta.meet.jit.si, which the front-end webapp
communicates directly, without my server anywhere in-between. Is this
description correct? What I'm missing now is the collaboration between
videobridge, jicofo and prosody (and the participants of course)

···

On 3/27/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

I cannot remember of a detailed document description of all. But here
is some schema:
https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md
You can see jitsi-meet there which is the web app and everything else
it the backend. Jitsi-meet connects to XMPP server from where it
communicates with the other participants and with jicofo, which is the
JItsiCOnferenceFOcus which orchestrates the conference. And
jitsi-videobridge is an SFU which is responsible for receiving the
media (audio/video) from the clients and forwarding it to the
appropriate participants.
This is the architecture in two sentences.

Regards
damencho

On Tue, Mar 27, 2018 at 10:47 AM, eyal land <eyal3002@gmail.com> wrote:

The "Running with webpack-dev-server for development" section on
README states that:

By default the backend deployment used is beta.meet.jit.si, ...

and later that the app is running on localhost:8080.

My question is, what is meant by the "backend deployment"? More
generally, what are the moving parts here, in what way does jitsi-meet
use jotsi-videobridge? How does the big picture looks? What's the
architecture behind the jitsi-meet webapp?

Sorry for all the questions, but I really want to understand the whole
design of the system, and I couldn't find an Architecture or a Code
Layout documentation page anywhere.

On 3/27/18, eyal land <eyal3002@gmail.com> wrote:

Thanks, I've settled for now on using webpack-dev-server, does the job.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This will not work that way. You need a webserver that supports ssi
(nginx, apache2 ... ) and https. Webrtc work when used with https
connection only, not sure whether `python -m SimpleHTTPServer`
supports https endpoints.
If you want to run it with some other webserver it should have https,
and if it doesn't support ssi you need to modify index.html and
replace ssi directives with standard script src tags, for example,
https://github.com/jitsi/jitsi-meet/blob/master/index.html#L132 should
be <script src="config.js"/>.

Regards
damencho

On Mon, Mar 26, 2018 at 3:28 PM, eyal land <eyal3002@gmail.com> wrote:

Here is the GET issued at the python server:

127.0.0.1 - - [26/Mar/2018 23:22:15] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET /css/all.css HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/lib-jitsi-meet.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/app.bundle.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:16] "GET /favicon.ico HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
/libs/do_external_connect.min.map HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/lib-jitsi-meet.min.map
HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/app.bundle.min.map
HTTP/1.1" 200 -

On 3/26/18, eyal land <eyal3002@gmail.com> wrote:

I first tried with no server, that is, just opening index.html in
chrome. Then I tried with `python -m SimpleHTTPServer` and went to
localhost:8000 but still no luck.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> >>>>>>> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and
`make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#10

Hi again,

Yep, the backend is doing all the conference logic, the web is just a
web frontend ...
beta.meet.jit.si is just our testing environment where latest packages
are being deployed and it can restart any now and then.
When using the dev-web-server it just serves everything from the
locally modified web app, where everything else is served from that
backend, this is just a developer tool.
What do you want to know about the backend? Its that jicofo is the one
creating the muc, the first to join the conference and it is the one
talking with the bridge opening channels there and sending offers with
those channels to the clients that join. Prosody is the xmpp server
that connects them all, all communication between different parts is
xmpp.

Regards
damencho

···

On Tue, Mar 27, 2018 at 12:02 PM, eyal land <eyal3002@gmail.com> wrote:

Thanks. So my server is there only to serve the React UI, right? The
real meat is happening on beta.meet.jit.si, which the front-end webapp
communicates directly, without my server anywhere in-between. Is this
description correct? What I'm missing now is the collaboration between
videobridge, jicofo and prosody (and the participants of course)

On 3/27/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

I cannot remember of a detailed document description of all. But here
is some schema:
https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md
You can see jitsi-meet there which is the web app and everything else
it the backend. Jitsi-meet connects to XMPP server from where it
communicates with the other participants and with jicofo, which is the
JItsiCOnferenceFOcus which orchestrates the conference. And
jitsi-videobridge is an SFU which is responsible for receiving the
media (audio/video) from the clients and forwarding it to the
appropriate participants.
This is the architecture in two sentences.

Regards
damencho

On Tue, Mar 27, 2018 at 10:47 AM, eyal land <eyal3002@gmail.com> wrote:

The "Running with webpack-dev-server for development" section on
README states that:

By default the backend deployment used is beta.meet.jit.si, ...

and later that the app is running on localhost:8080.

My question is, what is meant by the "backend deployment"? More
generally, what are the moving parts here, in what way does jitsi-meet
use jotsi-videobridge? How does the big picture looks? What's the
architecture behind the jitsi-meet webapp?

Sorry for all the questions, but I really want to understand the whole
design of the system, and I couldn't find an Architecture or a Code
Layout documentation page anywhere.

On 3/27/18, eyal land <eyal3002@gmail.com> wrote:

Thanks, I've settled for now on using webpack-dev-server, does the job.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This will not work that way. You need a webserver that supports ssi
(nginx, apache2 ... ) and https. Webrtc work when used with https
connection only, not sure whether `python -m SimpleHTTPServer`
supports https endpoints.
If you want to run it with some other webserver it should have https,
and if it doesn't support ssi you need to modify index.html and
replace ssi directives with standard script src tags, for example,
https://github.com/jitsi/jitsi-meet/blob/master/index.html#L132 should
be <script src="config.js"/>.

Regards
damencho

On Mon, Mar 26, 2018 at 3:28 PM, eyal land <eyal3002@gmail.com> wrote:

Here is the GET issued at the python server:

127.0.0.1 - - [26/Mar/2018 23:22:15] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET /css/all.css HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/lib-jitsi-meet.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/app.bundle.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:16] "GET /favicon.ico HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
/libs/do_external_connect.min.map HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/lib-jitsi-meet.min.map
HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/app.bundle.min.map
HTTP/1.1" 200 -

On 3/26/18, eyal land <eyal3002@gmail.com> wrote:

I first tried with no server, that is, just opening index.html in
chrome. Then I tried with `python -m SimpleHTTPServer` and went to
localhost:8000 but still no luck.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> >>>>>>>> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources) but
it doesn't work. Opening `index.html` (after `npm install` and
`make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#11

Thanks for the detailed response!

and sorry for bothering...

···

On 3/27/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi again,

Yep, the backend is doing all the conference logic, the web is just a
web frontend ...
beta.meet.jit.si is just our testing environment where latest packages
are being deployed and it can restart any now and then.
When using the dev-web-server it just serves everything from the
locally modified web app, where everything else is served from that
backend, this is just a developer tool.
What do you want to know about the backend? Its that jicofo is the one
creating the muc, the first to join the conference and it is the one
talking with the bridge opening channels there and sending offers with
those channels to the clients that join. Prosody is the xmpp server
that connects them all, all communication between different parts is
xmpp.

Regards
damencho

On Tue, Mar 27, 2018 at 12:02 PM, eyal land <eyal3002@gmail.com> wrote:

Thanks. So my server is there only to serve the React UI, right? The
real meat is happening on beta.meet.jit.si, which the front-end webapp
communicates directly, without my server anywhere in-between. Is this
description correct? What I'm missing now is the collaboration between
videobridge, jicofo and prosody (and the participants of course)

On 3/27/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

I cannot remember of a detailed document description of all. But here
is some schema:
https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md
You can see jitsi-meet there which is the web app and everything else
it the backend. Jitsi-meet connects to XMPP server from where it
communicates with the other participants and with jicofo, which is the
JItsiCOnferenceFOcus which orchestrates the conference. And
jitsi-videobridge is an SFU which is responsible for receiving the
media (audio/video) from the clients and forwarding it to the
appropriate participants.
This is the architecture in two sentences.

Regards
damencho

On Tue, Mar 27, 2018 at 10:47 AM, eyal land <eyal3002@gmail.com> wrote:

The "Running with webpack-dev-server for development" section on
README states that:

By default the backend deployment used is beta.meet.jit.si, ...

and later that the app is running on localhost:8080.

My question is, what is meant by the "backend deployment"? More
generally, what are the moving parts here, in what way does jitsi-meet
use jotsi-videobridge? How does the big picture looks? What's the
architecture behind the jitsi-meet webapp?

Sorry for all the questions, but I really want to understand the whole
design of the system, and I couldn't find an Architecture or a Code
Layout documentation page anywhere.

On 3/27/18, eyal land <eyal3002@gmail.com> wrote:

Thanks, I've settled for now on using webpack-dev-server, does the job.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This will not work that way. You need a webserver that supports ssi
(nginx, apache2 ... ) and https. Webrtc work when used with https
connection only, not sure whether `python -m SimpleHTTPServer`
supports https endpoints.
If you want to run it with some other webserver it should have https,
and if it doesn't support ssi you need to modify index.html and
replace ssi directives with standard script src tags, for example,
https://github.com/jitsi/jitsi-meet/blob/master/index.html#L132 should
be <script src="config.js"/>.

Regards
damencho

On Mon, Mar 26, 2018 at 3:28 PM, eyal land <eyal3002@gmail.com> wrote:

Here is the GET issued at the python server:

127.0.0.1 - - [26/Mar/2018 23:22:15] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET /css/all.css HTTP/1.1" 200
-
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/lib-jitsi-meet.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
/libs/app.bundle.min.js?v=139 HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:16] "GET /favicon.ico HTTP/1.1" 200
-
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
/libs/do_external_connect.min.map HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
/libs/lib-jitsi-meet.min.map
HTTP/1.1" 200 -
127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/app.bundle.min.map
HTTP/1.1" 200 -

On 3/26/18, eyal land <eyal3002@gmail.com> wrote:

I first tried with no server, that is, just opening index.html in
chrome. Then I tried with `python -m SimpleHTTPServer` and went to
localhost:8000 but still no luck.

On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

What is your web server serving those files? It seems it doesn't
support server-side includes.

Regards
damencho

On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> >>>>>>>>> wrote:

Hello,

I am trying to build Jitsi-Meet by following the instructions
[here](https://github.com/jitsi/jitsi-meet#building-the-sources)
but
it doesn't work. Opening `index.html` (after `npm install` and
`make`)
gives me a gray page with the following error:

Uncaught ReferenceError: interfaceConfig is not defined
    at Object.<anonymous> (languageDetector.web.js:23)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:86)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (_global.js:6)
    at t (bootstrap 598f5fbc0f03143fbe3c:19)
    at Object.<anonymous> (actions.js:622)
    at Object.<anonymous> (actions.js:432)

These lines repeat themselves (or at least that's how it looks).

Please guide me through the building process of Jitsi-Meet!

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#12

hello

···

2018-03-27 19:59 GMT+02:00 eyal land <eyal3002@gmail.com>:

Thanks for the detailed response!

and sorry for bothering...

On 3/27/18, Damian Minkov <damencho@jitsi.org> wrote:
> Hi again,
>
> Yep, the backend is doing all the conference logic, the web is just a
> web frontend ...
> beta.meet.jit.si is just our testing environment where latest packages
> are being deployed and it can restart any now and then.
> When using the dev-web-server it just serves everything from the
> locally modified web app, where everything else is served from that
> backend, this is just a developer tool.
> What do you want to know about the backend? Its that jicofo is the one
> creating the muc, the first to join the conference and it is the one
> talking with the bridge opening channels there and sending offers with
> those channels to the clients that join. Prosody is the xmpp server
> that connects them all, all communication between different parts is
> xmpp.
>
> Regards
> damencho
>
>
> On Tue, Mar 27, 2018 at 12:02 PM, eyal land <eyal3002@gmail.com> wrote:
>> Thanks. So my server is there only to serve the React UI, right? The
>> real meat is happening on beta.meet.jit.si, which the front-end webapp
>> communicates directly, without my server anywhere in-between. Is this
>> description correct? What I'm missing now is the collaboration between
>> videobridge, jicofo and prosody (and the participants of course)
>>
>> On 3/27/18, Damian Minkov <damencho@jitsi.org> wrote:
>>> Hi,
>>>
>>> I cannot remember of a detailed document description of all. But here
>>> is some schema:
>>> https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md
>>> You can see jitsi-meet there which is the web app and everything else
>>> it the backend. Jitsi-meet connects to XMPP server from where it
>>> communicates with the other participants and with jicofo, which is the
>>> JItsiCOnferenceFOcus which orchestrates the conference. And
>>> jitsi-videobridge is an SFU which is responsible for receiving the
>>> media (audio/video) from the clients and forwarding it to the
>>> appropriate participants.
>>> This is the architecture in two sentences.
>>>
>>> Regards
>>> damencho
>>>
>>> On Tue, Mar 27, 2018 at 10:47 AM, eyal land <eyal3002@gmail.com> > wrote:
>>>> The "Running with webpack-dev-server for development" section on
>>>> README states that:
>>>>
>>>>> By default the backend deployment used is beta.meet.jit.si, ...
>>>>
>>>> and later that the app is running on localhost:8080.
>>>>
>>>> My question is, what is meant by the "backend deployment"? More
>>>> generally, what are the moving parts here, in what way does jitsi-meet
>>>> use jotsi-videobridge? How does the big picture looks? What's the
>>>> architecture behind the jitsi-meet webapp?
>>>>
>>>> Sorry for all the questions, but I really want to understand the whole
>>>> design of the system, and I couldn't find an Architecture or a Code
>>>> Layout documentation page anywhere.
>>>>
>>>> On 3/27/18, eyal land <eyal3002@gmail.com> wrote:
>>>>> Thanks, I've settled for now on using webpack-dev-server, does the
job.
>>>>>
>>>>> On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> This will not work that way. You need a webserver that supports ssi
>>>>>> (nginx, apache2 ... ) and https. Webrtc work when used with https
>>>>>> connection only, not sure whether `python -m SimpleHTTPServer`
>>>>>> supports https endpoints.
>>>>>> If you want to run it with some other webserver it should have
https,
>>>>>> and if it doesn't support ssi you need to modify index.html and
>>>>>> replace ssi directives with standard script src tags, for example,
>>>>>> https://github.com/jitsi/jitsi-meet/blob/master/index.html#L132
should
>>>>>> be <script src="config.js"/>.
>>>>>>
>>>>>> Regards
>>>>>> damencho
>>>>>>
>>>>>>
>>>>>> On Mon, Mar 26, 2018 at 3:28 PM, eyal land <eyal3002@gmail.com> > wrote:
>>>>>>> Here is the GET issued at the python server:
>>>>>>>
>>>>>>> 127.0.0.1 - - [26/Mar/2018 23:22:15] "GET / HTTP/1.1" 200 -
>>>>>>> 127.0.0.1 - - [26/Mar/2018 23:22:15] "GET /css/all.css HTTP/1.1"
200
>>>>>>> -
>>>>>>> 127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
>>>>>>> /libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 -
>>>>>>> 127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
>>>>>>> /libs/lib-jitsi-meet.min.js?v=139 HTTP/1.1" 200 -
>>>>>>> 127.0.0.1 - - [26/Mar/2018 23:22:15] "GET
>>>>>>> /libs/app.bundle.min.js?v=139 HTTP/1.1" 200 -
>>>>>>> 127.0.0.1 - - [26/Mar/2018 23:22:16] "GET /favicon.ico HTTP/1.1"
200
>>>>>>> -
>>>>>>> 127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
>>>>>>> /libs/do_external_connect.min.map HTTP/1.1" 200 -
>>>>>>> 127.0.0.1 - - [26/Mar/2018 23:22:20] "GET
>>>>>>> /libs/lib-jitsi-meet.min.map
>>>>>>> HTTP/1.1" 200 -
>>>>>>> 127.0.0.1 - - [26/Mar/2018 23:22:20] "GET /libs/app.bundle.min.map
>>>>>>> HTTP/1.1" 200 -
>>>>>>>
>>>>>>>
>>>>>>> On 3/26/18, eyal land <eyal3002@gmail.com> wrote:
>>>>>>>> I first tried with no server, that is, just opening index.html in
>>>>>>>> chrome. Then I tried with `python -m SimpleHTTPServer` and went to
>>>>>>>> localhost:8000 but still no luck.
>>>>>>>>
>>>>>>>> On 3/26/18, Damian Minkov <damencho@jitsi.org> wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> What is your web server serving those files? It seems it doesn't
>>>>>>>>> support server-side includes.
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> damencho
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Mar 26, 2018 at 2:55 PM, eyal land <eyal3002@gmail.com> > >>>>>>>>> wrote:
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> I am trying to build Jitsi-Meet by following the instructions
>>>>>>>>>> [here](https://github.com/jitsi/jitsi-meet#building-the-sources
)
>>>>>>>>>> but
>>>>>>>>>> it doesn't work. Opening `index.html` (after `npm install` and
>>>>>>>>>> `make`)
>>>>>>>>>> gives me a gray page with the following error:
>>>>>>>>>>
>>>>>>>>>> Uncaught ReferenceError: interfaceConfig is not defined
>>>>>>>>>> at Object.<anonymous> (languageDetector.web.js:23)
>>>>>>>>>> at t (bootstrap 598f5fbc0f03143fbe3c:19)
>>>>>>>>>> at Object.<anonymous> (actions.js:86)
>>>>>>>>>> at t (bootstrap 598f5fbc0f03143fbe3c:19)
>>>>>>>>>> at Object.<anonymous> (_global.js:6)
>>>>>>>>>> at t (bootstrap 598f5fbc0f03143fbe3c:19)
>>>>>>>>>> at Object.<anonymous> (actions.js:622)
>>>>>>>>>> at Object.<anonymous> (actions.js:432)
>>>>>>>>>>
>>>>>>>>>> These lines repeat themselves (or at least that's how it looks).
>>>>>>>>>>
>>>>>>>>>> Please guide me through the building process of Jitsi-Meet!
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> dev mailing list
>>>>>>>>>> dev@jitsi.org
>>>>>>>>>> Unsubscribe instructions and other list options:
>>>>>>>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> dev mailing list
>>>>>>>>> dev@jitsi.org
>>>>>>>>> Unsubscribe instructions and other list options:
>>>>>>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> dev mailing list
>>>>>>> dev@jitsi.org
>>>>>>> Unsubscribe instructions and other list options:
>>>>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>>>>
>>>>>> _______________________________________________
>>>>>> dev mailing list
>>>>>> dev@jitsi.org
>>>>>> Unsubscribe instructions and other list options:
>>>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>>>
>>>>
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
Khalfoun Besma .