[jitsi-users] deb packages vs. compiling from source


#1

Hi Team,

I have a question regarding which version to use in production (for each
component), and how to update in case of bug. Installing from deb packages
vs. compiling from source.

TL:

What version of each app to be used for production. I understand the quick
install method does it though deb packages and configures all components
together all in one server and it works great.

Thanks to great community !! as each repository is getting updated almost
everyday. How do one decide which code to use? and if it will work with
each components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo,
jigasi etc.

So If I have to split services on different server for better scaling,
should I still be using deb packages to install?

Main question: In case of bug in current install, and that bug is fixed in
recent code, does it get updated on deb packages as well or do we have to
compile each component from source ?

Thanks

BR,
Jade


#2

Hi,

Hi Team,

I have a question regarding which version to use in production (for each
component), and how to update in case of bug. Installing from deb packages
vs. compiling from source.

TL:

What version of each app to be used for production. I understand the quick
install method does it though deb packages and configures all components
together all in one server and it works great.

Thanks to great community !! as each repository is getting updated almost
everyday. How do one decide which code to use? and if it will work with each
components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo, jigasi etc.

So when installing from deb package you can look at the jitsi-meet version:
# dpkg -l | grep jitsi-meet
ii jitsi-meet 1.0.1638-1
       all WebRTC JavaScript video conferences

This is version 1638 is for the meta package that has dependencies of
particular versions that are currently installed. So if you go to any
of the repos of the components there is a tag jitsi-meet_1638 which
makes the relation between particular source snapshot and the version
installed.

So If I have to split services on different server for better scaling,
should I still be using deb packages to install?

Yep, you can use debian packages. You can install different components
on different machines without requiring all other dependencies, but
you need some configuration so for example jicofo and jvb to connect
to the prosody server machine. There are some scripts in the meta
package source repo(https://github.com/jitsi/jitsi-meet-debian-meta)
for checking corresponding versions:
https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/get-versions.sh.
The scripts depend on having updated debian repo on the machine
running them.

Main question: In case of bug in current install, and that bug is fixed in
recent code, does it get updated on deb packages as well or do we have to
compile each component from source ?

Fixing bugs goes into unstable. We have some internal performance
tests(run on every build) and when they pass packages goes into
testing repo automatically. Once we decide a version is production
ready we push it to stable.
So you can decide which repo to use.

Regards
damencho

···

On Tue, Jan 24, 2017 at 11:09 AM, Jade SZ <jitterbuffer@gmail.com> wrote:

Thanks

BR,
Jade

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


#3

Hi damencho,

Thanks for the great info. It indeed helped.

Can you confirm if jitsi-meet_1622 is the latest stable as it comes with
Debian stable repo. As I see on github tags are in 2k's

Also which version of jitsi-meet is being used for https://meet.jit.si/ ?

Regards,
JSZ

···

On Tue, Jan 24, 2017 at 10:40 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

On Tue, Jan 24, 2017 at 11:09 AM, Jade SZ <jitterbuffer@gmail.com> wrote:
> Hi Team,
>
> I have a question regarding which version to use in production (for each
> component), and how to update in case of bug. Installing from deb
packages
> vs. compiling from source.
>
> TL:
>
> What version of each app to be used for production. I understand the
quick
> install method does it though deb packages and configures all components
> together all in one server and it works great.
>
> Thanks to great community !! as each repository is getting updated almost
> everyday. How do one decide which code to use? and if it will work with
each
> components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo, jigasi
etc.

So when installing from deb package you can look at the jitsi-meet version:
# dpkg -l | grep jitsi-meet
ii jitsi-meet 1.0.1638-1
       all WebRTC JavaScript video conferences

This is version 1638 is for the meta package that has dependencies of
particular versions that are currently installed. So if you go to any
of the repos of the components there is a tag jitsi-meet_1638 which
makes the relation between particular source snapshot and the version
installed.

>
> So If I have to split services on different server for better scaling,
> should I still be using deb packages to install?

Yep, you can use debian packages. You can install different components
on different machines without requiring all other dependencies, but
you need some configuration so for example jicofo and jvb to connect
to the prosody server machine. There are some scripts in the meta
package source repo(https://github.com/jitsi/jitsi-meet-debian-meta)
for checking corresponding versions:
https://github.com/jitsi/jitsi-meet-debian-meta/blob/
master/get-versions.sh.
The scripts depend on having updated debian repo on the machine
running them.

>
> Main question: In case of bug in current install, and that bug is fixed
in
> recent code, does it get updated on deb packages as well or do we have to
> compile each component from source ?

Fixing bugs goes into unstable. We have some internal performance
tests(run on every build) and when they pass packages goes into
testing repo automatically. Once we decide a version is production
ready we push it to stable.
So you can decide which repo to use.

Regards
damencho

>
>
> Thanks
>
>
>
> BR,
> Jade
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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


#4

Yep, that is the latest stable. We haven't released in a while and we are
looking forward for the new release.
About the versions, open two tabs on meet.jit.si and in the js console
filter with the word version this way you can check, prosody, jicofo and
jvb versions. Open the source of the page and check the version number in
the script inclusion of app.bundle this is the jitsi-meet-web package
version.

Regards
damencho

···

On Apr 26, 2017 8:06 AM, "Jade SZ" <jitterbuffer@gmail.com> wrote:

Hi damencho,

Thanks for the great info. It indeed helped.

Can you confirm if jitsi-meet_1622 is the latest stable as it comes with
Debian stable repo. As I see on github tags are in 2k's

Also which version of jitsi-meet is being used for https://meet.jit.si/ ?

Regards,
JSZ

On Tue, Jan 24, 2017 at 10:40 PM, Damian Minkov <damencho@jitsi.org> > wrote:

Hi,

On Tue, Jan 24, 2017 at 11:09 AM, Jade SZ <jitterbuffer@gmail.com> wrote:
> Hi Team,
>
> I have a question regarding which version to use in production (for each
> component), and how to update in case of bug. Installing from deb
packages
> vs. compiling from source.
>
> TL:
>
> What version of each app to be used for production. I understand the
quick
> install method does it though deb packages and configures all components
> together all in one server and it works great.
>
> Thanks to great community !! as each repository is getting updated
almost
> everyday. How do one decide which code to use? and if it will work with
each
> components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo, jigasi
etc.

So when installing from deb package you can look at the jitsi-meet
version:
# dpkg -l | grep jitsi-meet
ii jitsi-meet 1.0.1638-1
       all WebRTC JavaScript video conferences

This is version 1638 is for the meta package that has dependencies of
particular versions that are currently installed. So if you go to any
of the repos of the components there is a tag jitsi-meet_1638 which
makes the relation between particular source snapshot and the version
installed.

>
> So If I have to split services on different server for better scaling,
> should I still be using deb packages to install?

Yep, you can use debian packages. You can install different components
on different machines without requiring all other dependencies, but
you need some configuration so for example jicofo and jvb to connect
to the prosody server machine. There are some scripts in the meta
package source repo(https://github.com/jitsi/jitsi-meet-debian-meta)
for checking corresponding versions:
https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/
get-versions.sh.
The scripts depend on having updated debian repo on the machine
running them.

>
> Main question: In case of bug in current install, and that bug is fixed
in
> recent code, does it get updated on deb packages as well or do we have
to
> compile each component from source ?

Fixing bugs goes into unstable. We have some internal performance
tests(run on every build) and when they pass packages goes into
testing repo automatically. Once we decide a version is production
ready we push it to stable.
So you can decide which repo to use.

Regards
damencho

>
>
> Thanks
>
>
>
> BR,
> Jade
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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

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


#5

Hi,

Here is a screenshot.

Regards
damencho

···

On Wed, Apr 26, 2017 at 9:51 AM, Kaiduan Xie <kaiduanx@gmail.com> wrote:

Damencho,

open two tabs on meet.jit.si and in the js console filter with the word
version this way you can check, prosody, jicofo and jvb versions

How to filter with the word version to check prosody, jicofo, jvb version? I
have not figured out :slight_smile:

/Kaiduan

On Wed, Apr 26, 2017 at 9:29 AM, Damian Minkov <damencho@damencho.com> > wrote:

Yep, that is the latest stable. We haven't released in a while and we are
looking forward for the new release.
About the versions, open two tabs on meet.jit.si and in the js console
filter with the word version this way you can check, prosody, jicofo and jvb
versions. Open the source of the page and check the version number in the
script inclusion of app.bundle this is the jitsi-meet-web package version.

Regards
damencho

On Apr 26, 2017 8:06 AM, "Jade SZ" <jitterbuffer@gmail.com> wrote:

Hi damencho,

Thanks for the great info. It indeed helped.

Can you confirm if jitsi-meet_1622 is the latest stable as it comes with
Debian stable repo. As I see on github tags are in 2k's

Also which version of jitsi-meet is being used for https://meet.jit.si/ ?

Regards,
JSZ

On Tue, Jan 24, 2017 at 10:40 PM, Damian Minkov <damencho@jitsi.org> >>> wrote:

Hi,

On Tue, Jan 24, 2017 at 11:09 AM, Jade SZ <jitterbuffer@gmail.com> >>>> wrote:
> Hi Team,
>
> I have a question regarding which version to use in production (for
> each
> component), and how to update in case of bug. Installing from deb
> packages
> vs. compiling from source.
>
> TL:
>
> What version of each app to be used for production. I understand the
> quick
> install method does it though deb packages and configures all
> components
> together all in one server and it works great.
>
> Thanks to great community !! as each repository is getting updated
> almost
> everyday. How do one decide which code to use? and if it will work
> with each
> components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo,
> jigasi etc.

So when installing from deb package you can look at the jitsi-meet
version:
# dpkg -l | grep jitsi-meet
ii jitsi-meet 1.0.1638-1
       all WebRTC JavaScript video conferences

This is version 1638 is for the meta package that has dependencies of
particular versions that are currently installed. So if you go to any
of the repos of the components there is a tag jitsi-meet_1638 which
makes the relation between particular source snapshot and the version
installed.

>
> So If I have to split services on different server for better scaling,
> should I still be using deb packages to install?

Yep, you can use debian packages. You can install different components
on different machines without requiring all other dependencies, but
you need some configuration so for example jicofo and jvb to connect
to the prosody server machine. There are some scripts in the meta
package source repo(https://github.com/jitsi/jitsi-meet-debian-meta)
for checking corresponding versions:

https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/get-versions.sh.
The scripts depend on having updated debian repo on the machine
running them.

>
> Main question: In case of bug in current install, and that bug is
> fixed in
> recent code, does it get updated on deb packages as well or do we have
> to
> compile each component from source ?

Fixing bugs goes into unstable. We have some internal performance
tests(run on every build) and when they pass packages goes into
testing repo automatically. Once we decide a version is production
ready we push it to stable.
So you can decide which repo to use.

Regards
damencho

>
>
> Thanks
>
>
>
> BR,
> Jade
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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

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

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

--
Founder of Goodstartsoft
https://www.goodstartsoft.com

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


#6

Damencho,

open two tabs on meet.jit.si and in the js console filter with the word
version this way you can check, prosody, jicofo and jvb versions

How to filter with the word version to check prosody, jicofo, jvb version?
I have not figured out :slight_smile:

/Kaiduan

···

On Wed, Apr 26, 2017 at 9:29 AM, Damian Minkov <damencho@damencho.com> wrote:

Yep, that is the latest stable. We haven't released in a while and we are
looking forward for the new release.
About the versions, open two tabs on meet.jit.si and in the js console
filter with the word version this way you can check, prosody, jicofo and
jvb versions. Open the source of the page and check the version number in
the script inclusion of app.bundle this is the jitsi-meet-web package
version.

Regards
damencho

On Apr 26, 2017 8:06 AM, "Jade SZ" <jitterbuffer@gmail.com> wrote:

Hi damencho,

Thanks for the great info. It indeed helped.

Can you confirm if jitsi-meet_1622 is the latest stable as it comes with
Debian stable repo. As I see on github tags are in 2k's

Also which version of jitsi-meet is being used for https://meet.jit.si/ ?

Regards,
JSZ

On Tue, Jan 24, 2017 at 10:40 PM, Damian Minkov <damencho@jitsi.org> >> wrote:

Hi,

On Tue, Jan 24, 2017 at 11:09 AM, Jade SZ <jitterbuffer@gmail.com> >>> wrote:
> Hi Team,
>
> I have a question regarding which version to use in production (for
each
> component), and how to update in case of bug. Installing from deb
packages
> vs. compiling from source.
>
> TL:
>
> What version of each app to be used for production. I understand the
quick
> install method does it though deb packages and configures all
components
> together all in one server and it works great.
>
> Thanks to great community !! as each repository is getting updated
almost
> everyday. How do one decide which code to use? and if it will work
with each
> components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo,
jigasi etc.

So when installing from deb package you can look at the jitsi-meet
version:
# dpkg -l | grep jitsi-meet
ii jitsi-meet 1.0.1638-1
       all WebRTC JavaScript video conferences

This is version 1638 is for the meta package that has dependencies of
particular versions that are currently installed. So if you go to any
of the repos of the components there is a tag jitsi-meet_1638 which
makes the relation between particular source snapshot and the version
installed.

>
> So If I have to split services on different server for better scaling,
> should I still be using deb packages to install?

Yep, you can use debian packages. You can install different components
on different machines without requiring all other dependencies, but
you need some configuration so for example jicofo and jvb to connect
to the prosody server machine. There are some scripts in the meta
package source repo(https://github.com/jitsi/jitsi-meet-debian-meta)
for checking corresponding versions:
https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/
get-versions.sh.
The scripts depend on having updated debian repo on the machine
running them.

>
> Main question: In case of bug in current install, and that bug is
fixed in
> recent code, does it get updated on deb packages as well or do we have
to
> compile each component from source ?

Fixing bugs goes into unstable. We have some internal performance
tests(run on every build) and when they pass packages goes into
testing repo automatically. Once we decide a version is production
ready we push it to stable.
So you can decide which repo to use.

Regards
damencho

>
>
> Thanks
>
>
>
> BR,
> Jade
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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

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

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

--
Founder of Goodstartsoft
https://www.goodstartsoft.com


#7

Hi Team/damencho,

Is jigasi dependent on jitsi-meet version or I can use the one in master
which seems to have latest fixes.

I don't see in jitsi meet debian meta any specific versioning of jigasi per
jitsi-meet. Please confirm. Thanks

Regards,
JSZ

···

On Wed, Apr 26, 2017 at 8:01 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

Here is a screenshot.

Regards
damencho

On Wed, Apr 26, 2017 at 9:51 AM, Kaiduan Xie <kaiduanx@gmail.com> wrote:
> Damencho,
>
> open two tabs on meet.jit.si and in the js console filter with the word
> version this way you can check, prosody, jicofo and jvb versions
>
> How to filter with the word version to check prosody, jicofo, jvb
version? I
> have not figured out :slight_smile:
>
> /Kaiduan
>
> On Wed, Apr 26, 2017 at 9:29 AM, Damian Minkov <damencho@damencho.com> > > wrote:
>>
>> Yep, that is the latest stable. We haven't released in a while and we
are
>> looking forward for the new release.
>> About the versions, open two tabs on meet.jit.si and in the js console
>> filter with the word version this way you can check, prosody, jicofo
and jvb
>> versions. Open the source of the page and check the version number in
the
>> script inclusion of app.bundle this is the jitsi-meet-web package
version.
>>
>> Regards
>> damencho
>>
>> On Apr 26, 2017 8:06 AM, "Jade SZ" <jitterbuffer@gmail.com> wrote:
>>>
>>> Hi damencho,
>>>
>>> Thanks for the great info. It indeed helped.
>>>
>>> Can you confirm if jitsi-meet_1622 is the latest stable as it comes
with
>>> Debian stable repo. As I see on github tags are in 2k's
>>>
>>> Also which version of jitsi-meet is being used for
https://meet.jit.si/ ?
>>>
>>>
>>> Regards,
>>> JSZ
>>>
>>> On Tue, Jan 24, 2017 at 10:40 PM, Damian Minkov <damencho@jitsi.org> > >>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> On Tue, Jan 24, 2017 at 11:09 AM, Jade SZ <jitterbuffer@gmail.com> > >>>> wrote:
>>>> > Hi Team,
>>>> >
>>>> > I have a question regarding which version to use in production (for
>>>> > each
>>>> > component), and how to update in case of bug. Installing from deb
>>>> > packages
>>>> > vs. compiling from source.
>>>> >
>>>> > TL:
>>>> >
>>>> > What version of each app to be used for production. I understand the
>>>> > quick
>>>> > install method does it though deb packages and configures all
>>>> > components
>>>> > together all in one server and it works great.
>>>> >
>>>> > Thanks to great community !! as each repository is getting updated
>>>> > almost
>>>> > everyday. How do one decide which code to use? and if it will work
>>>> > with each
>>>> > components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo,
>>>> > jigasi etc.
>>>>
>>>> So when installing from deb package you can look at the jitsi-meet
>>>> version:
>>>> # dpkg -l | grep jitsi-meet
>>>> ii jitsi-meet 1.0.1638-1
>>>> all WebRTC JavaScript video conferences
>>>>
>>>> This is version 1638 is for the meta package that has dependencies of
>>>> particular versions that are currently installed. So if you go to any
>>>> of the repos of the components there is a tag jitsi-meet_1638 which
>>>> makes the relation between particular source snapshot and the version
>>>> installed.
>>>>
>>>> >
>>>> > So If I have to split services on different server for better
scaling,
>>>> > should I still be using deb packages to install?
>>>>
>>>> Yep, you can use debian packages. You can install different components
>>>> on different machines without requiring all other dependencies, but
>>>> you need some configuration so for example jicofo and jvb to connect
>>>> to the prosody server machine. There are some scripts in the meta
>>>> package source repo(https://github.com/jitsi/jitsi-meet-debian-meta)
>>>> for checking corresponding versions:
>>>>
>>>> https://github.com/jitsi/jitsi-meet-debian-meta/blob/
master/get-versions.sh.
>>>> The scripts depend on having updated debian repo on the machine
>>>> running them.
>>>>
>>>> >
>>>> > Main question: In case of bug in current install, and that bug is
>>>> > fixed in
>>>> > recent code, does it get updated on deb packages as well or do we
have
>>>> > to
>>>> > compile each component from source ?
>>>>
>>>> Fixing bugs goes into unstable. We have some internal performance
>>>> tests(run on every build) and when they pass packages goes into
>>>> testing repo automatically. Once we decide a version is production
>>>> ready we push it to stable.
>>>> So you can decide which repo to use.
>>>>
>>>> Regards
>>>> damencho
>>>>
>>>>
>>>> >
>>>> >
>>>> > Thanks
>>>> >
>>>> >
>>>> >
>>>> > BR,
>>>> > Jade
>>>> >
>>>> > _______________________________________________
>>>> > users mailing list
>>>> > users@jitsi.org
>>>> > Unsubscribe instructions and other list options:
>>>> > http://lists.jitsi.org/mailman/listinfo/users
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/users
>>>
>>>
>>>
>>> _______________________________________________
>>> users mailing list
>>> users@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>
>
> --
> Founder of Goodstartsoft
> https://www.goodstartsoft.com
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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


#8

Yep, there is no matching version in meta package. I suggest always using
latest for now.

···

On May 18, 2017 06:28, "JSZ" <jitterbuffer@gmail.com> wrote:

Hi Team/damencho,

Is jigasi dependent on jitsi-meet version or I can use the one in master
which seems to have latest fixes.

I don't see in jitsi meet debian meta any specific versioning of jigasi
per jitsi-meet. Please confirm. Thanks

Regards,
JSZ

On Wed, Apr 26, 2017 at 8:01 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

Here is a screenshot.

Regards
damencho

On Wed, Apr 26, 2017 at 9:51 AM, Kaiduan Xie <kaiduanx@gmail.com> wrote:
> Damencho,
>
> open two tabs on meet.jit.si and in the js console filter with the word
> version this way you can check, prosody, jicofo and jvb versions
>
> How to filter with the word version to check prosody, jicofo, jvb
version? I
> have not figured out :slight_smile:
>
> /Kaiduan
>
> On Wed, Apr 26, 2017 at 9:29 AM, Damian Minkov <damencho@damencho.com> >> > wrote:
>>
>> Yep, that is the latest stable. We haven't released in a while and we
are
>> looking forward for the new release.
>> About the versions, open two tabs on meet.jit.si and in the js console
>> filter with the word version this way you can check, prosody, jicofo
and jvb
>> versions. Open the source of the page and check the version number in
the
>> script inclusion of app.bundle this is the jitsi-meet-web package
version.
>>
>> Regards
>> damencho
>>
>> On Apr 26, 2017 8:06 AM, "Jade SZ" <jitterbuffer@gmail.com> wrote:
>>>
>>> Hi damencho,
>>>
>>> Thanks for the great info. It indeed helped.
>>>
>>> Can you confirm if jitsi-meet_1622 is the latest stable as it comes
with
>>> Debian stable repo. As I see on github tags are in 2k's
>>>
>>> Also which version of jitsi-meet is being used for
https://meet.jit.si/ ?
>>>
>>>
>>> Regards,
>>> JSZ
>>>
>>> On Tue, Jan 24, 2017 at 10:40 PM, Damian Minkov <damencho@jitsi.org> >> >>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> On Tue, Jan 24, 2017 at 11:09 AM, Jade SZ <jitterbuffer@gmail.com> >> >>>> wrote:
>>>> > Hi Team,
>>>> >
>>>> > I have a question regarding which version to use in production (for
>>>> > each
>>>> > component), and how to update in case of bug. Installing from deb
>>>> > packages
>>>> > vs. compiling from source.
>>>> >
>>>> > TL:
>>>> >
>>>> > What version of each app to be used for production. I understand
the
>>>> > quick
>>>> > install method does it though deb packages and configures all
>>>> > components
>>>> > together all in one server and it works great.
>>>> >
>>>> > Thanks to great community !! as each repository is getting updated
>>>> > almost
>>>> > everyday. How do one decide which code to use? and if it will work
>>>> > with each
>>>> > components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo,
>>>> > jigasi etc.
>>>>
>>>> So when installing from deb package you can look at the jitsi-meet
>>>> version:
>>>> # dpkg -l | grep jitsi-meet
>>>> ii jitsi-meet 1.0.1638-1
>>>> all WebRTC JavaScript video conferences
>>>>
>>>> This is version 1638 is for the meta package that has dependencies of
>>>> particular versions that are currently installed. So if you go to any
>>>> of the repos of the components there is a tag jitsi-meet_1638 which
>>>> makes the relation between particular source snapshot and the version
>>>> installed.
>>>>
>>>> >
>>>> > So If I have to split services on different server for better
scaling,
>>>> > should I still be using deb packages to install?
>>>>
>>>> Yep, you can use debian packages. You can install different
components
>>>> on different machines without requiring all other dependencies, but
>>>> you need some configuration so for example jicofo and jvb to connect
>>>> to the prosody server machine. There are some scripts in the meta
>>>> package source repo(https://github.com/jitsi/jitsi-meet-debian-meta)
>>>> for checking corresponding versions:
>>>>
>>>> https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/
get-versions.sh.
>>>> The scripts depend on having updated debian repo on the machine
>>>> running them.
>>>>
>>>> >
>>>> > Main question: In case of bug in current install, and that bug is
>>>> > fixed in
>>>> > recent code, does it get updated on deb packages as well or do we
have
>>>> > to
>>>> > compile each component from source ?
>>>>
>>>> Fixing bugs goes into unstable. We have some internal performance
>>>> tests(run on every build) and when they pass packages goes into
>>>> testing repo automatically. Once we decide a version is production
>>>> ready we push it to stable.
>>>> So you can decide which repo to use.
>>>>
>>>> Regards
>>>> damencho
>>>>
>>>>
>>>> >
>>>> >
>>>> > Thanks
>>>> >
>>>> >
>>>> >
>>>> > BR,
>>>> > Jade
>>>> >
>>>> > _______________________________________________
>>>> > users mailing list
>>>> > users@jitsi.org
>>>> > Unsubscribe instructions and other list options:
>>>> > http://lists.jitsi.org/mailman/listinfo/users
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/users
>>>
>>>
>>>
>>> _______________________________________________
>>> users mailing list
>>> users@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>
>
> --
> Founder of Goodstartsoft
> https://www.goodstartsoft.com
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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

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


#9

Hi,

Can we use latest version of jigasi with debian stable jitsi-meet. Or do we
have to use a specific version only. Thanks

Regards,
JSZ

···

On Thu, May 18, 2017 at 4:26 PM, JSZ <jitterbuffer@gmail.com> wrote:

Hi Team/damencho,

Is jigasi dependent on jitsi-meet version or I can use the one in master
which seems to have latest fixes.

I don't see in jitsi meet debian meta any specific versioning of jigasi
per jitsi-meet. Please confirm. Thanks

Regards,
JSZ

On Wed, Apr 26, 2017 at 8:01 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

Here is a screenshot.

Regards
damencho

On Wed, Apr 26, 2017 at 9:51 AM, Kaiduan Xie <kaiduanx@gmail.com> wrote:
> Damencho,
>
> open two tabs on meet.jit.si and in the js console filter with the word
> version this way you can check, prosody, jicofo and jvb versions
>
> How to filter with the word version to check prosody, jicofo, jvb
version? I
> have not figured out :slight_smile:
>
> /Kaiduan
>
> On Wed, Apr 26, 2017 at 9:29 AM, Damian Minkov <damencho@damencho.com> >> > wrote:
>>
>> Yep, that is the latest stable. We haven't released in a while and we
are
>> looking forward for the new release.
>> About the versions, open two tabs on meet.jit.si and in the js console
>> filter with the word version this way you can check, prosody, jicofo
and jvb
>> versions. Open the source of the page and check the version number in
the
>> script inclusion of app.bundle this is the jitsi-meet-web package
version.
>>
>> Regards
>> damencho
>>
>> On Apr 26, 2017 8:06 AM, "Jade SZ" <jitterbuffer@gmail.com> wrote:
>>>
>>> Hi damencho,
>>>
>>> Thanks for the great info. It indeed helped.
>>>
>>> Can you confirm if jitsi-meet_1622 is the latest stable as it comes
with
>>> Debian stable repo. As I see on github tags are in 2k's
>>>
>>> Also which version of jitsi-meet is being used for
https://meet.jit.si/ ?
>>>
>>>
>>> Regards,
>>> JSZ
>>>
>>> On Tue, Jan 24, 2017 at 10:40 PM, Damian Minkov <damencho@jitsi.org> >> >>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> On Tue, Jan 24, 2017 at 11:09 AM, Jade SZ <jitterbuffer@gmail.com> >> >>>> wrote:
>>>> > Hi Team,
>>>> >
>>>> > I have a question regarding which version to use in production (for
>>>> > each
>>>> > component), and how to update in case of bug. Installing from deb
>>>> > packages
>>>> > vs. compiling from source.
>>>> >
>>>> > TL:
>>>> >
>>>> > What version of each app to be used for production. I understand
the
>>>> > quick
>>>> > install method does it though deb packages and configures all
>>>> > components
>>>> > together all in one server and it works great.
>>>> >
>>>> > Thanks to great community !! as each repository is getting updated
>>>> > almost
>>>> > everyday. How do one decide which code to use? and if it will work
>>>> > with each
>>>> > components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo,
>>>> > jigasi etc.
>>>>
>>>> So when installing from deb package you can look at the jitsi-meet
>>>> version:
>>>> # dpkg -l | grep jitsi-meet
>>>> ii jitsi-meet 1.0.1638-1
>>>> all WebRTC JavaScript video conferences
>>>>
>>>> This is version 1638 is for the meta package that has dependencies of
>>>> particular versions that are currently installed. So if you go to any
>>>> of the repos of the components there is a tag jitsi-meet_1638 which
>>>> makes the relation between particular source snapshot and the version
>>>> installed.
>>>>
>>>> >
>>>> > So If I have to split services on different server for better
scaling,
>>>> > should I still be using deb packages to install?
>>>>
>>>> Yep, you can use debian packages. You can install different
components
>>>> on different machines without requiring all other dependencies, but
>>>> you need some configuration so for example jicofo and jvb to connect
>>>> to the prosody server machine. There are some scripts in the meta
>>>> package source repo(https://github.com/jitsi/jitsi-meet-debian-meta)
>>>> for checking corresponding versions:
>>>>
>>>> https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/
get-versions.sh.
>>>> The scripts depend on having updated debian repo on the machine
>>>> running them.
>>>>
>>>> >
>>>> > Main question: In case of bug in current install, and that bug is
>>>> > fixed in
>>>> > recent code, does it get updated on deb packages as well or do we
have
>>>> > to
>>>> > compile each component from source ?
>>>>
>>>> Fixing bugs goes into unstable. We have some internal performance
>>>> tests(run on every build) and when they pass packages goes into
>>>> testing repo automatically. Once we decide a version is production
>>>> ready we push it to stable.
>>>> So you can decide which repo to use.
>>>>
>>>> Regards
>>>> damencho
>>>>
>>>>
>>>> >
>>>> >
>>>> > Thanks
>>>> >
>>>> >
>>>> >
>>>> > BR,
>>>> > Jade
>>>> >
>>>> > _______________________________________________
>>>> > users mailing list
>>>> > users@jitsi.org
>>>> > Unsubscribe instructions and other list options:
>>>> > http://lists.jitsi.org/mailman/listinfo/users
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/users
>>>
>>>
>>>
>>> _______________________________________________
>>> users mailing list
>>> users@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>
>
> --
> Founder of Goodstartsoft
> https://www.goodstartsoft.com
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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


#10

Use latest jigasi, should be ok with stable.

···

On May 19, 2017 6:25 AM, "JSZ" <jitterbuffer@gmail.com> wrote:

Hi,

Can we use latest version of jigasi with debian stable jitsi-meet. Or do
we have to use a specific version only. Thanks

Regards,
JSZ

On Thu, May 18, 2017 at 4:26 PM, JSZ <jitterbuffer@gmail.com> wrote:

Hi Team/damencho,

Is jigasi dependent on jitsi-meet version or I can use the one in master
which seems to have latest fixes.

I don't see in jitsi meet debian meta any specific versioning of jigasi
per jitsi-meet. Please confirm. Thanks

Regards,
JSZ

On Wed, Apr 26, 2017 at 8:01 PM, Damian Minkov <damencho@jitsi.org> >> wrote:

Hi,

Here is a screenshot.

Regards
damencho

On Wed, Apr 26, 2017 at 9:51 AM, Kaiduan Xie <kaiduanx@gmail.com> wrote:
> Damencho,
>
> open two tabs on meet.jit.si and in the js console filter with the
word
> version this way you can check, prosody, jicofo and jvb versions
>
> How to filter with the word version to check prosody, jicofo, jvb
version? I
> have not figured out :slight_smile:
>
> /Kaiduan
>
> On Wed, Apr 26, 2017 at 9:29 AM, Damian Minkov <damencho@damencho.com> >>> > wrote:
>>
>> Yep, that is the latest stable. We haven't released in a while and we
are
>> looking forward for the new release.
>> About the versions, open two tabs on meet.jit.si and in the js
console
>> filter with the word version this way you can check, prosody, jicofo
and jvb
>> versions. Open the source of the page and check the version number in
the
>> script inclusion of app.bundle this is the jitsi-meet-web package
version.
>>
>> Regards
>> damencho
>>
>> On Apr 26, 2017 8:06 AM, "Jade SZ" <jitterbuffer@gmail.com> wrote:
>>>
>>> Hi damencho,
>>>
>>> Thanks for the great info. It indeed helped.
>>>
>>> Can you confirm if jitsi-meet_1622 is the latest stable as it comes
with
>>> Debian stable repo. As I see on github tags are in 2k's
>>>
>>> Also which version of jitsi-meet is being used for
https://meet.jit.si/ ?
>>>
>>>
>>> Regards,
>>> JSZ
>>>
>>> On Tue, Jan 24, 2017 at 10:40 PM, Damian Minkov <damencho@jitsi.org> >>> >>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> On Tue, Jan 24, 2017 at 11:09 AM, Jade SZ <jitterbuffer@gmail.com> >>> >>>> wrote:
>>>> > Hi Team,
>>>> >
>>>> > I have a question regarding which version to use in production
(for
>>>> > each
>>>> > component), and how to update in case of bug. Installing from deb
>>>> > packages
>>>> > vs. compiling from source.
>>>> >
>>>> > TL:
>>>> >
>>>> > What version of each app to be used for production. I understand
the
>>>> > quick
>>>> > install method does it though deb packages and configures all
>>>> > components
>>>> > together all in one server and it works great.
>>>> >
>>>> > Thanks to great community !! as each repository is getting updated
>>>> > almost
>>>> > everyday. How do one decide which code to use? and if it will work
>>>> > with each
>>>> > components like jitsi-meet, lib-jitsi-meet, videobridge, jicofo,
>>>> > jigasi etc.
>>>>
>>>> So when installing from deb package you can look at the jitsi-meet
>>>> version:
>>>> # dpkg -l | grep jitsi-meet
>>>> ii jitsi-meet 1.0.1638-1
>>>> all WebRTC JavaScript video conferences
>>>>
>>>> This is version 1638 is for the meta package that has dependencies
of
>>>> particular versions that are currently installed. So if you go to
any
>>>> of the repos of the components there is a tag jitsi-meet_1638 which
>>>> makes the relation between particular source snapshot and the
version
>>>> installed.
>>>>
>>>> >
>>>> > So If I have to split services on different server for better
scaling,
>>>> > should I still be using deb packages to install?
>>>>
>>>> Yep, you can use debian packages. You can install different
components
>>>> on different machines without requiring all other dependencies, but
>>>> you need some configuration so for example jicofo and jvb to connect
>>>> to the prosody server machine. There are some scripts in the meta
>>>> package source repo(https://github.com/jitsi/jitsi-meet-debian-meta
)
>>>> for checking corresponding versions:
>>>>
>>>> https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/
get-versions.sh.
>>>> The scripts depend on having updated debian repo on the machine
>>>> running them.
>>>>
>>>> >
>>>> > Main question: In case of bug in current install, and that bug is
>>>> > fixed in
>>>> > recent code, does it get updated on deb packages as well or do we
have
>>>> > to
>>>> > compile each component from source ?
>>>>
>>>> Fixing bugs goes into unstable. We have some internal performance
>>>> tests(run on every build) and when they pass packages goes into
>>>> testing repo automatically. Once we decide a version is production
>>>> ready we push it to stable.
>>>> So you can decide which repo to use.
>>>>
>>>> Regards
>>>> damencho
>>>>
>>>>
>>>> >
>>>> >
>>>> > Thanks
>>>> >
>>>> >
>>>> >
>>>> > BR,
>>>> > Jade
>>>> >
>>>> > _______________________________________________
>>>> > users mailing list
>>>> > users@jitsi.org
>>>> > Unsubscribe instructions and other list options:
>>>> > http://lists.jitsi.org/mailman/listinfo/users
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/users
>>>
>>>
>>>
>>> _______________________________________________
>>> users mailing list
>>> users@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>
>
> --
> Founder of Goodstartsoft
> https://www.goodstartsoft.com
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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

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