Jitsi-meet: Nextcloud + jitsi

[lelibreauquotidien]

Good morning,

Is your feature request related to a problem you are facing?
Yesterday I wanted to create a video conference on meet.jit.si and record it.
I was surprised when I saw that recording was only possible on dropbox.

Describe the solution you'd like
I located the bash script that sends the file to dropbox.
I will be potentially interested to implement this on jitsi meet with other people.

Are you interested in this feature?
Waiting for your answer.

[damencho]

There are many people interested in this. This will involve also UI changes(jitsi-meet) so this can be enabled, and people to authenticate using their nextcloud instance, and jibri change to upload it.
So if you are willing to work on that, go for it, the community will be very happy about it. What we can offer is help, review and adopt it on meet.jit.si.

[lelibreauquotidien]

Good,I'll keep you informed

[sunjam]

Conversations could be saved to WebDAV, which is the exact open standard used by Nextcloud. See request #5412

[pixi]

Good,I'll keep you informed
Did you make any progress here?
And, one way or the other, would this be an inspioration for you? https://switnet.net/en/2020/05/jitsi-meet-jibri-nextcloud/

[lelibreauquotidien]

I have failed to install my jitsi development environment.

[azon2111]

Any updates on this? TY

[sunjam]

Umm, all the info is on GitHub.

On Mon, May 18, 2020, 12:44 PM azon2111 [e-mail] wrote:

Any updates on this? TY

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jitsi/jitsi-meet/issues/5800#issuecomment-630397561,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANUKZTLR5TND7CAEQLDREDRSGFZTANCNFSM4MEDX3SA
.

[azon2111]

Umm, all the info is on GitHub.
…
On Mon, May 18, 2020, 12:44 PM azon2111 @.*> wrote: Any updates on this? TY — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5800 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANUKZTLR5TND7CAEQLDREDRSGFZTANCNFSM4MEDX3SA .

I am posting this on GitHub - I see the one script that deploys jitsi-jibri-nextcloud altogher but not seeing anything here about WebDAV or NC specifically that would be drop in code for the dropbox that already exists in jitsi-meet config file, which I assume is what most are looking for.

I would also assume using an app key from NC would be an option too if MFA was being used on the NC install along with creds from the user the same as dropbox integration works.

Please point me in the right direction here in GH if I am not correct.

[azon2111]

I also see where the quick installer is using external storage option to see the jitsi-meet recordings share which is not the same as writing to a WebDAV based directory but more like just extending the NC side to get to the save directory config'd into Jitsi / Jibri.

Please aid in my understanding if you understand to be different.

[Ark74]

@azon2111 that's exactly it.

At some point I'll try to add some option to write to existing NC instances, since when you add new jibri nodes is not feasible to add more NC instances.

There is already some detailed work done on this:
https://community.jitsi.org/t/how-to-to-get-a-working-setup-of-google-drive-one-drive-or-other-cloud-services-in-jibri-my-comprehensive-tutorial-for-the-beginner/42228

[sunjam]

The requests are spread across various jitsi repositories. You can Google
them as "nextcloud jitsi GitHub" or "webdav jitsi GitHub", etc. I am
slammed for time, but we have discussed this in depth on help.nextcloud.com
and some in jitsi community forum.

You'll see the nextcloud team has given detailed info on how much
integration is possible, but they will not be rewriting jitsi in php so
external integration will be the thing... The work will be on the jitsi end
to support webdav and such. Hope this helps.

On Wed, May 20, 2020, 9:34 AM Luis Guzman [e-mail] wrote:

@azon2111 https://github.com/azon2111 that's exactly it.

At some point I'll try to add some option to write to existing NC
instances, since when you add new jibri nodes is not feasible to add more
NC instances.

There is already some detailed work done on this:

https://community.jitsi.org/t/how-to-to-get-a-working-setup-of-google-drive-one-drive-or-other-cloud-services-in-jibri-my-comprehensive-tutorial-for-the-beginner/42228

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jitsi/jitsi-meet/issues/5800#issuecomment-631587295,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANUKZTVKDGXLPSIHWGAW6LRSQBBTANCNFSM4MEDX3SA
.

[luixxiul]

Please remember there are priorities among tasks to be done. Cross-posting would not help that much.

[azon2111]

This is what I did instead if anyone cares:

Just a note here, the Jitsi-Jibri-NC script does not save to NC, what it does is extend External Storage feature of NC to the storage location of the recordings.

What I did was to mount a WebDAV directory directly in the Jibri servers to store the recordings directly into the NC storage instead. I do this at boot time so that it can be ensured the mount persists at each boot.

I used the info from these 2 locations

https://docs.nextcloud.com/server/15/user_manual/files/access_webdav.html

https://stefanoprenna.com/blog/2014/01/08/tutorial-how-to-automatically-mount-webdav-shares-at-boot-in-linux/

[azon2111]

@azon2111 that's exactly it.

At some point I'll try to add some option to write to existing NC instances, since when you add new jibri nodes is not feasible to add more NC instances.

There is already some detailed work done on this:
https://community.jitsi.org/t/how-to-to-get-a-working-setup-of-google-drive-one-drive-or-other-cloud-services-in-jibri-my-comprehensive-tutorial-for-the-beginner/42228

See my note here above this one about WebDAV mount points which alleviates the need for a NC instance being deployed in your script at all to connect to NC storage.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rosa2]

Keep it alive