[jitsi-dev] Redirection when connecting from a mobile phone


#1

Hi Jitsi team!

I am observing that when users try to login from their mobiles they are
redirected to the Jitsi Mobile App. Is there a way to avoid this
redirection?

I would like them to connect via Chrome on their Android phone, and not
at all on their iPhone (I know iPhone does not yet support WebRTC which
is fine, android supports it, I need to test Windows phones also).

Checking the Jitsi Meet files I found the following variable in
/usr/share/jitsi-meet/interface_config.js:

···

------------------------------------------------------------------------
MOBILE_APP_PROMO: true
------------------------------------------------------------------------

Switching MOBILE_APP_PROMO to "false" should be enough?

Thanks in advance.

Kind regards,
Daniel


#2

Hi Daniel,
As I experience, setting MOBILE_APP_PROMO: false, wont let you use
jitsi-meet on mobile browsers. It just remove the mobile app promotion. And
displays a message saying that "Jitsi-meet does not support mobile"

···

On Thu, Jun 1, 2017 at 12:16 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

Hi Jitsi team!

I am observing that when users try to login from their mobiles they are
redirected to the Jitsi Mobile App. Is there a way to avoid this
redirection?

I would like them to connect via Chrome on their Android phone, and not
at all on their iPhone (I know iPhone does not yet support WebRTC which
is fine, android supports it, I need to test Windows phones also).

Checking the Jitsi Meet files I found the following variable in
/usr/share/jitsi-meet/interface_config.js:

------------------------------------------------------------------------
MOBILE_APP_PROMO: true
------------------------------------------------------------------------

Switching MOBILE_APP_PROMO to "false" should be enough?

Thanks in advance.

Kind regards,
Daniel

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

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>


#3

Hi Daniel,

Hi, Buddhika.

As I experience, setting MOBILE_APP_PROMO: false, wont let you use
jitsi-meet on mobile browsers. It just remove the mobile app promotion.
And displays a message saying that "Jitsi-meet does not support mobile"

Thanks for your reply.

But you're getting the "Jitsi-meet does not support mobile" message when
you try to access from Android with Chrome by putting this variable in
"false"?

I thought Jitsi Meet would work without hindrance on any platform that
uses Chrome.

Kind regards,
Daniel

···

On 31/05/17 16:38, Buddhika Jayawardhana wrote:


#4

You can create your own mobile apps for Android and IOS (As per the
documentation
<https://github.com/jitsi/jitsi-meet/blob/master/doc/mobile.md>). . I think
viewing on the browser has been disabled considering the user experience.

···

On Thu, Jun 1, 2017 at 2:08 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 31/05/17 16:38, Buddhika Jayawardhana wrote:

> Hi Daniel,

Hi, Buddhika.

> As I experience, setting MOBILE_APP_PROMO: false, wont let you use
> jitsi-meet on mobile browsers. It just remove the mobile app promotion.
> And displays a message saying that "Jitsi-meet does not support mobile"

Thanks for your reply.

But you're getting the "Jitsi-meet does not support mobile" message when
you try to access from Android with Chrome by putting this variable in
"false"?

I thought Jitsi Meet would work without hindrance on any platform that
uses Chrome.

Kind regards,
Daniel

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

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>


#5

Hi, Buddhika.

···

On 31/05/17 22:59, Buddhika Jayawardhana wrote:

You can create your own mobile apps for Android and IOS (As per the
documentation
<https://github.com/jitsi/jitsi-meet/blob/master/doc/mobile.md>). . I
think viewing on the browser has been disabled considering the user
experience.

Thanks for your answer.

But is this something recent? Because I have a screenshot from last year
(December 2016) and it was working.

https://ibin.co/3OQjpddvkuOc.png

Kind regards,
Daniel


#6

Yes, this was changed after that. The main reason is having a proper UX, adjusted to mobile needs, which the website doesn’t provide. You can bypass this by requesting the desktop site.

Cheers,

···

On Jun 1, 2017, at 05:05, Daniel Bareiro <daniel-listas@gmx.net> wrote:

Hi, Buddhika.

On 31/05/17 22:59, Buddhika Jayawardhana wrote:

You can create your own mobile apps for Android and IOS (As per the
documentation
<https://github.com/jitsi/jitsi-meet/blob/master/doc/mobile.md>). . I
think viewing on the browser has been disabled considering the user
experience.

Thanks for your answer.

But is this something recent? Because I have a screenshot from last year
(December 2016) and it was working.

https://ibin.co/3OQjpddvkuOc.png

--
Saúl


#7

I have not used an old version of jitsi. Is there anyone who could get this
working ?

···

On Thu, Jun 1, 2017 at 8:35 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

Hi, Buddhika.

On 31/05/17 22:59, Buddhika Jayawardhana wrote:

> You can create your own mobile apps for Android and IOS (As per the
> documentation
> <https://github.com/jitsi/jitsi-meet/blob/master/doc/mobile.md>). . I
> think viewing on the browser has been disabled considering the user
> experience.

Thanks for your answer.

But is this something recent? Because I have a screenshot from last year
(December 2016) and it was working.

https://ibin.co/3OQjpddvkuOc.png

Kind regards,
Daniel

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

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>


#8

Hi, Saúl.

But is this something recent? Because I have a screenshot from last year
(December 2016) and it was working.

https://ibin.co/3OQjpddvkuOc.png

Yes, this was changed after that. The main reason is having a proper UX,
adjusted to mobile needs, which the website doesn’t provide.

Thank you for confirming this. Do you know approximately when this
change was introduced?

You can bypass this by requesting the desktop site.

To get this do you mean to use something like User-Agent Switcher?

Thanks for your reply.

Kind regards,
Daniel

···

On 01/06/17 04:33, Saúl Ibarra Corretgé wrote:


#9

Hi, Saúl.

But is this something recent? Because I have a screenshot from last year
(December 2016) and it was working.

https://ibin.co/3OQjpddvkuOc.png

Yes, this was changed after that. The main reason is having a proper UX,
adjusted to mobile needs, which the website doesn’t provide.

Thank you for confirming this. Do you know approximately when this
change was introduced?

Not really :-S But you should be able to find it by looking at the commits in the unsupported-browser feature.

You can bypass this by requesting the desktop site.

To get this do you mean to use something like User-Agent Switcher?

No, Chrome on Android has a checkbox which reads “Request desktop site” that’s enough to go back to the web version.

Cheers,

···

On Jun 1, 2017, at 13:45, Daniel Bareiro <daniel-listas@gmx.net> wrote:
On 01/06/17 04:33, Saúl Ibarra Corretgé wrote:

--
Saúl


#10

Hi, Saúl.

But is this something recent? Because I have a screenshot from last year
(December 2016) and it was working.

https://ibin.co/3OQjpddvkuOc.png

Yes, this was changed after that. The main reason is having a proper UX,
adjusted to mobile needs, which the website doesn’t provide.

Thank you for confirming this. Do you know approximately when this
change was introduced?

Not really :-S But you should be able to find it by looking at the commits
in the unsupported-browser feature.

The question was also aimed at achieving a natural integration of Jitsi
Meet with a Learning Management System (Chamilo) and the idea was that
users have a direct access to Jitsi Meet from that platform. I think
this change can make this integration difficult.

Any suggestions?

I've been reviewing the commits so far this year and I found these:

https://github.com/jitsi/jitsi-meet/commit/743d12e32607f2ba9f1a228e110b9877a9924df9

https://github.com/jitsi/jitsi-meet/commit/05b7df26e6f386f3a0511a3c6bbbf183778a1915

https://github.com/jitsi/jitsi-meet/commit/88eabf23f4641197db39504c63030406ad24d723

Could you please confirm if the change is introduced by any of these
commits?

You can bypass this by requesting the desktop site.

To get this do you mean to use something like User-Agent Switcher?

No, Chrome on Android has a checkbox which reads “Request desktop site”
that’s enough to go back to the web version.

Ah, thanks for the clarification!

Thanks for your time.

Kind regards,
Daniel

···

On 01/06/17 10:09, Saúl Ibarra Corretgé wrote:


#11

Hi, Saúl.

But is this something recent? Because I have a screenshot from last year
(December 2016) and it was working.

https://ibin.co/3OQjpddvkuOc.png

Yes, this was changed after that. The main reason is having a proper UX,
adjusted to mobile needs, which the website doesn’t provide.

Thank you for confirming this. Do you know approximately when this
change was introduced?

Not really :-S But you should be able to find it by looking at the commits
in the unsupported-browser feature.

The question was also aimed at achieving a natural integration of Jitsi
Meet with a Learning Management System (Chamilo) and the idea was that
users have a direct access to Jitsi Meet from that platform. I think
this change can make this integration difficult.

I’m not familiar with that system, but I guess I understand what you mean.

Any suggestions?

I've been reviewing the commits so far this year and I found these:

https://github.com/jitsi/jitsi-meet/commit/743d12e32607f2ba9f1a228e110b9877a9924df9

https://github.com/jitsi/jitsi-meet/commit/05b7df26e6f386f3a0511a3c6bbbf183778a1915

https://github.com/jitsi/jitsi-meet/commit/88eabf23f4641197db39504c63030406ad24d723

Could you please confirm if the change is introduced by any of these
commits?

Kinda. That feature got worked over a number of times, but if I’m not mistaken, modifying this test should enable it for Android: https://github.com/jitsi/jitsi-meet/blob/master/react/features/app/functions.web.js#L42

Just remove the Android part.

Cheers,

···

On Jun 1, 2017, at 23:31, Daniel Bareiro <daniel-listas@gmx.net> wrote:
On 01/06/17 10:09, Saúl Ibarra Corretgé wrote:

--
Saúl


#12

Hi, Saúl.

Thank you for confirming this. Do you know approximately when this
change was introduced?

Not really :-S But you should be able to find it by looking at the commits
in the unsupported-browser feature.

The question was also aimed at achieving a natural integration of Jitsi
Meet with a Learning Management System (Chamilo) and the idea was that
users have a direct access to Jitsi Meet from that platform. I think
this change can make this integration difficult.

I’m not familiar with that system, but I guess I understand what you mean.

Any suggestions?

I've been reviewing the commits so far this year and I found these:

https://github.com/jitsi/jitsi-meet/commit/743d12e32607f2ba9f1a228e110b9877a9924df9

https://github.com/jitsi/jitsi-meet/commit/05b7df26e6f386f3a0511a3c6bbbf183778a1915

https://github.com/jitsi/jitsi-meet/commit/88eabf23f4641197db39504c63030406ad24d723

Could you please confirm if the change is introduced by any of these
commits?

Kinda. That feature got worked over a number of times, but if I’m not mistaken,
modifying this test should enable it for Android:
https://github.com/jitsi/jitsi-meet/blob/master/react/features/app/functions.web.js#L42

Just remove the Android part.

Thank you for this. Then I understand that I would have to remove the
lines 42 through 52 (including the comma of line 52, right?). Should
this allow to directly access Jitsi Meet without having to ask for the
desktop version of the site?

I don't see this "react" directory on my installation from the
repository. To test this would I have to download the code, make the
change and compile it or is there any way to test this change over a
preexisting installation?

Thanks for your time.

Kind regards,
Daniel

···

On 02/06/17 05:25, Saúl Ibarra Corretgé wrote:


#13

Hi, Saúl.

Thank you for confirming this. Do you know approximately when this
change was introduced?

Not really :-S But you should be able to find it by looking at the commits
in the unsupported-browser feature.

The question was also aimed at achieving a natural integration of Jitsi
Meet with a Learning Management System (Chamilo) and the idea was that
users have a direct access to Jitsi Meet from that platform. I think
this change can make this integration difficult.

I’m not familiar with that system, but I guess I understand what you mean.

Any suggestions?

I've been reviewing the commits so far this year and I found these:

https://github.com/jitsi/jitsi-meet/commit/743d12e32607f2ba9f1a228e110b9877a9924df9

https://github.com/jitsi/jitsi-meet/commit/05b7df26e6f386f3a0511a3c6bbbf183778a1915

https://github.com/jitsi/jitsi-meet/commit/88eabf23f4641197db39504c63030406ad24d723

Could you please confirm if the change is introduced by any of these
commits?

Kinda. That feature got worked over a number of times, but if I’m not mistaken,
modifying this test should enable it for Android:
https://github.com/jitsi/jitsi-meet/blob/master/react/features/app/functions.web.js#L42

Just remove the Android part.

Thank you for this. Then I understand that I would have to remove the
lines 42 through 52 (including the comma of line 52, right?). Should
this allow to directly access Jitsi Meet without having to ask for the
desktop version of the site?

Correct. Though it would be easier if you change “android” for “NOTandroid” so the platform name doesn’t match.

I don't see this "react" directory on my installation from the
repository. To test this would I have to download the code, make the
change and compile it or is there any way to test this change over a
preexisting installation?

I’m afraid not. All the code gets bundled together, so you’d have to build jitsi-meet from source.

Cheers,

···

On Jun 2, 2017, at 13:58, Daniel Bareiro <daniel-listas@gmx.net> wrote:
On 02/06/17 05:25, Saúl Ibarra Corretgé wrote:

--
Saúl


#14

Hi, Saúl.

I've been reviewing the commits so far this year and I found these:

https://github.com/jitsi/jitsi-meet/commit/743d12e32607f2ba9f1a228e110b9877a9924df9

https://github.com/jitsi/jitsi-meet/commit/05b7df26e6f386f3a0511a3c6bbbf183778a1915

https://github.com/jitsi/jitsi-meet/commit/88eabf23f4641197db39504c63030406ad24d723

Could you please confirm if the change is introduced by any of these
commits?

Kinda. That feature got worked over a number of times, but if I’m not mistaken,
modifying this test should enable it for Android:
https://github.com/jitsi/jitsi-meet/blob/master/react/features/app/functions.web.js#L42

Just remove the Android part.

Thank you for this. Then I understand that I would have to remove the
lines 42 through 52 (including the comma of line 52, right?). Should
this allow to directly access Jitsi Meet without having to ask for the
desktop version of the site?

Correct. Though it would be easier if you change “android” for “NOTandroid”
so the platform name doesn’t match.

Thanks for the suggestion.

I don't see this "react" directory on my installation from the
repository. To test this would I have to download the code, make the
change and compile it or is there any way to test this change over a
preexisting installation?

I’m afraid not. All the code gets bundled together, so you’d have to
build jitsi-meet from source.

Thanks for confirm. I will take it into account in case I have to
introduce this change.

Following this path, by getting the jitsi-meet code from the Github
repository and compiling, the result would be equivalent to installing
the jitsi-meet, jitsi-meet-web-config, jitsi-meet-web, and
jitsi-meet-prosody packages?

Could the other packages (jicofo and jitsi-videobridge) be installed and
interact smoothly with the compiled version?

Thanks for your reply.

Kind regards,
Daniel

···

On 02/06/17 10:07, Saúl Ibarra Corretgé wrote:


#15

Hi, Saúl.

I've been reviewing the commits so far this year and I found these:

https://github.com/jitsi/jitsi-meet/commit/743d12e32607f2ba9f1a228e110b9877a9924df9

https://github.com/jitsi/jitsi-meet/commit/05b7df26e6f386f3a0511a3c6bbbf183778a1915

https://github.com/jitsi/jitsi-meet/commit/88eabf23f4641197db39504c63030406ad24d723

Could you please confirm if the change is introduced by any of these
commits?

Kinda. That feature got worked over a number of times, but if I’m not mistaken,
modifying this test should enable it for Android:
https://github.com/jitsi/jitsi-meet/blob/master/react/features/app/functions.web.js#L42

Just remove the Android part.

Thank you for this. Then I understand that I would have to remove the
lines 42 through 52 (including the comma of line 52, right?). Should
this allow to directly access Jitsi Meet without having to ask for the
desktop version of the site?

Correct. Though it would be easier if you change “android” for “NOTandroid”
so the platform name doesn’t match.

Thanks for the suggestion.

I don't see this "react" directory on my installation from the
repository. To test this would I have to download the code, make the
change and compile it or is there any way to test this change over a
preexisting installation?

I’m afraid not. All the code gets bundled together, so you’d have to
build jitsi-meet from source.

Thanks for confirm. I will take it into account in case I have to
introduce this change.

Following this path, by getting the jitsi-meet code from the Github
repository and compiling, the result would be equivalent to installing
the jitsi-meet, jitsi-meet-web-config, jitsi-meet-web, and
jitsi-meet-prosody packages?

No, that would be just jitsi-meet-web (and the -config I think). The rest don’t need changes.

Could the other packages (jicofo and jitsi-videobridge) be installed and
interact smoothly with the compiled version?

Sure.

Cheers,

···

On Jun 12, 2017, at 12:50, Daniel <daniel-listas@gmx.net> wrote:
On 02/06/17 10:07, Saúl Ibarra Corretgé wrote:

--
Saúl


#16

Hi Daniel,

This is how I have done it.

   1. Install the jitsi-meet using package manager
   2. clone jitsi-meet from git
   3. checkout to the relevant release of installed jitsi-meet
   4. change the code and make
   5. change the jitsi-meet root in Nginx virtual host config

···

On Mon, Jun 12, 2017 at 11:20 PM, Daniel <daniel-listas@gmx.net> wrote:

Hi, Saúl.

On 02/06/17 10:07, Saúl Ibarra Corretgé wrote:

>>>> I've been reviewing the commits so far this year and I found these:
>>>>
>>>> https://github.com/jitsi/jitsi-meet/commit/
743d12e32607f2ba9f1a228e110b9877a9924df9
>>>>
>>>> https://github.com/jitsi/jitsi-meet/commit/
05b7df26e6f386f3a0511a3c6bbbf183778a1915
>>>>
>>>> https://github.com/jitsi/jitsi-meet/commit/
88eabf23f4641197db39504c63030406ad24d723
>>>>
>>>> Could you please confirm if the change is introduced by any of these
>>>> commits?

>>> Kinda. That feature got worked over a number of times, but if I’m not
mistaken,
>>> modifying this test should enable it for Android:
>>> https://github.com/jitsi/jitsi-meet/blob/master/react/
features/app/functions.web.js#L42
>>>
>>> Just remove the Android part.

>> Thank you for this. Then I understand that I would have to remove the
>> lines 42 through 52 (including the comma of line 52, right?). Should
>> this allow to directly access Jitsi Meet without having to ask for the
>> desktop version of the site?

> Correct. Though it would be easier if you change “android” for
“NOTandroid”
> so the platform name doesn’t match.

Thanks for the suggestion.

>> I don't see this "react" directory on my installation from the
>> repository. To test this would I have to download the code, make the
>> change and compile it or is there any way to test this change over a
>> preexisting installation?

> I’m afraid not. All the code gets bundled together, so you’d have to
> build jitsi-meet from source.

Thanks for confirm. I will take it into account in case I have to
introduce this change.

Following this path, by getting the jitsi-meet code from the Github
repository and compiling, the result would be equivalent to installing
the jitsi-meet, jitsi-meet-web-config, jitsi-meet-web, and
jitsi-meet-prosody packages?

Could the other packages (jicofo and jitsi-videobridge) be installed and
interact smoothly with the compiled version?

Thanks for your reply.

Kind regards,
Daniel

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

--
*Buddhika Jayawardhana*
Undergraduate | Department of Computer Science & Engineering
University of Moratuwa
*buddhika.anushka@gmail.com <buddhika.12@cse.mrt.ac.lk>* | LinkedIn
<http://lk.linkedin.com/in/buddhikajay/>


#17

Hi, Saúl.

I don't see this "react" directory on my installation from the
repository. To test this would I have to download the code, make the
change and compile it or is there any way to test this change over a
preexisting installation?

I’m afraid not. All the code gets bundled together, so you’d have to
build jitsi-meet from source.

Thanks for confirm. I will take it into account in case I have to
introduce this change.

Following this path, by getting the jitsi-meet code from the Github
repository and compiling, the result would be equivalent to installing
the jitsi-meet, jitsi-meet-web-config, jitsi-meet-web, and
jitsi-meet-prosody packages?

No, that would be just jitsi-meet-web (and the -config I think). The rest don’t need changes.

Could the other packages (jicofo and jitsi-videobridge) be installed and
interact smoothly with the compiled version?

Sure.

Perfect. So in the case of compiling the source code for jitsi-meet, if
I understood correctly, I should install jitsi-meet and
jitsi-meet-prosody (in addition to jicofo and jitsi-videobridge). It is
right?

Thanks for your reply.

Kind regards,
Daniel

···

On 12/06/17 17:47, Saúl Ibarra Corretgé wrote:


#18

Just jitsi-meet should be ok, the rest you should already have them.

Cheers,

···

On Jun 12, 2017, at 18:00, Daniel <daniel-listas@gmx.net> wrote:

Hi, Saúl.

On 12/06/17 17:47, Saúl Ibarra Corretgé wrote:

I don't see this "react" directory on my installation from the
repository. To test this would I have to download the code, make the
change and compile it or is there any way to test this change over a
preexisting installation?

I’m afraid not. All the code gets bundled together, so you’d have to
build jitsi-meet from source.

Thanks for confirm. I will take it into account in case I have to
introduce this change.

Following this path, by getting the jitsi-meet code from the Github
repository and compiling, the result would be equivalent to installing
the jitsi-meet, jitsi-meet-web-config, jitsi-meet-web, and
jitsi-meet-prosody packages?

No, that would be just jitsi-meet-web (and the -config I think). The rest don’t need changes.

Could the other packages (jicofo and jitsi-videobridge) be installed and
interact smoothly with the compiled version?

Sure.

Perfect. So in the case of compiling the source code for jitsi-meet, if
I understood correctly, I should install jitsi-meet and
jitsi-meet-prosody (in addition to jicofo and jitsi-videobridge). It is
right?

--
Saúl


#19

Hi, Saúl.

···

On 13/06/17 11:42, Saúl Ibarra Corretgé wrote:

I don't see this "react" directory on my installation from the
repository. To test this would I have to download the code, make the
change and compile it or is there any way to test this change over a
preexisting installation?

I’m afraid not. All the code gets bundled together, so you’d have to
build jitsi-meet from source.

Thanks for confirm. I will take it into account in case I have to
introduce this change.

Following this path, by getting the jitsi-meet code from the Github
repository and compiling, the result would be equivalent to installing
the jitsi-meet, jitsi-meet-web-config, jitsi-meet-web, and
jitsi-meet-prosody packages?

No, that would be just jitsi-meet-web (and the -config I think). The rest don’t need changes.

Could the other packages (jicofo and jitsi-videobridge) be installed and
interact smoothly with the compiled version?

Sure.

Perfect. So in the case of compiling the source code for jitsi-meet, if
I understood correctly, I should install jitsi-meet and
jitsi-meet-prosody (in addition to jicofo and jitsi-videobridge). It is
right?

Just jitsi-meet should be ok, the rest you should already have them.

Ah, then I think this would coincide with the procedure suggested by
Buddhika, right?

From what I see, the other packages would be installed as dependencies:

------------------------------------------------------------------------
root@conference:~# aptitude show jitsi-meet
[...]
Depends: jitsi-videobridge (= 961-1), jicofo (= 1.0-357-1),
jitsi-meet-web (= 1.0.2025-1), jitsi-meet-web-config (= 1.0.2025-1),
jitsi-meet-prosody (= 1.0.2025-1)
------------------------------------------------------------------------

I think in this case we would have redundant code installed, because we
have the jitsi-meet version of the package and the version we compiled
with the code of https://github.com/jitsi/jitsi-meet, right?

I think that's why Buddhika said that he changed on Nginx the web
directory for the one used by the compiled application.

Kind regards,
Daniel


#20

Hi, Saúl.

I don't see this "react" directory on my installation from the
repository. To test this would I have to download the code, make the
change and compile it or is there any way to test this change over a
preexisting installation?

I’m afraid not. All the code gets bundled together, so you’d have to
build jitsi-meet from source.

Thanks for confirm. I will take it into account in case I have to
introduce this change.

Following this path, by getting the jitsi-meet code from the Github
repository and compiling, the result would be equivalent to installing
the jitsi-meet, jitsi-meet-web-config, jitsi-meet-web, and
jitsi-meet-prosody packages?

No, that would be just jitsi-meet-web (and the -config I think). The rest don’t need changes.

Could the other packages (jicofo and jitsi-videobridge) be installed and
interact smoothly with the compiled version?

Sure.

Perfect. So in the case of compiling the source code for jitsi-meet, if
I understood correctly, I should install jitsi-meet and
jitsi-meet-prosody (in addition to jicofo and jitsi-videobridge). It is
right?

Just jitsi-meet should be ok, the rest you should already have them.

Ah, then I think this would coincide with the procedure suggested by
Buddhika, right?

I haven’t seen his replies, sorry.

From what I see, the other packages would be installed as dependencies:

------------------------------------------------------------------------
root@conference:~# aptitude show jitsi-meet
[...]
Depends: jitsi-videobridge (= 961-1), jicofo (= 1.0-357-1),
jitsi-meet-web (= 1.0.2025-1), jitsi-meet-web-config (= 1.0.2025-1),
jitsi-meet-prosody (= 1.0.2025-1)
------------------------------------------------------------------------

I think in this case we would have redundant code installed, because we
have the jitsi-meet version of the package and the version we compiled
with the code of https://github.com/jitsi/jitsi-meet, right?

If you build a Debian package, it will replace the installed one, if you just build the code you have 2 choices:

- copy your changes over the existing files
- install it elsewhere and have nguni look there

I think that's why Buddhika said that he changed on Nginx the web
directory for the one used by the compiled application.

This would work for the second option, yes.

Cheers,

···

On Jun 14, 2017, at 13:40, Daniel <daniel-listas@gmx.net> wrote:
On 13/06/17 11:42, Saúl Ibarra Corretgé wrote:

--
Saúl