On Thu, Mar 4, 2021 at 8:54 PM Rick Moen <rick@???> wrote:
>
> Quoting Gabe Stanton via Dng (dng@???):
>
> > This is incentive for me to take another crack at getting a jitsi
> > instance running. It will probably take me a couple months to get one
> > working since time is limited and there are many things higher on the
> > priorities list, but I'll work on that and get back to the list when I
> > have that running.
>
> Here are my (raw, and I stress, _raw_) notes from setting up Jitsi Meet
> (on Amazon EC2, on Debian 10) in a tearing hurry for the 2020 World
> Science Fiction Convention (the '2020 Worldcon'), which was forced by
> the exploding pandemic to suddenly convert itself into a virtual event,
> instead of being in Wellington, NZ:
> http://linuxmafia.com/~rick/jitsi.txt
>
> Here's the 2020 Worldcon's (CoNZealand's) Web site.
> https://conzealand.nz/
>
> The Worldcon is an all-volunteer-run, all-volunteer-staffed literary
> science fiction convention held annually somewhere on planet Earth
> (so far ;-> ). Usual attendance is about 3000 people who fly in from
> everywhere. A big Worldcon, like London's in 2014, is about 8000
> in-person attendees.
>
> My instance of Jitsi Meet had no performance problems whatsoever for the
> usage CoNZealand made -- though I was prepared to spin up more instances
> of Jitsi Videobridge2 if necessary to share the load. Honestly, once I
> stopped making a couple of dumb mistakes in site configuration
> (preserved in my raw notes), it was pretty darned easy to configure.
>
> There are sundry site-admin customisations that can be done, which I
> didn't fully cover in my notes, but aren't that hard to find, and I
> might even be able to refresh my memory about those if you need to ask.
>
> As you might gather from my notes, I got directives from above that
> changed during the project about whether to try to shim in an oauth2
> authentication layer (non-default) and then whether or not to configure
> an operating mode where only a list of people (staff) with prearranged
> admin credentials were permitted to create Jitsi Meet rooms. The
> eventual deployment did not include the latter security controls --
> making it work pretty much like meet.jit.si . However, those security
> controls weren't difficult to do if desired.
>
>
> Before any asks: No, I didn't do that on Devuan because I was in a
> huge hurry and had a known-good Amazon EC2 AMI of Debian 10 at my
> disposal. I expect that my setup instructions will work just great on
> Devuan.
I, for one, p l e a s e ? (!?!)