Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Jeroen van Veen <>
To: "" <>
Subject: [Galene] Pyrite Manager Interface & Users
Date: Mon, 27 Sep 2021 19:06:46 +0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1338 bytes --]


I'm currently working on and off a Galene management interface in Pyrite (Screenshot shows some initial work, branch is at
The basic idea is that a manager can easily switch between conference mode and manager mode with two separate logins(one for user groups
and one for the manager section). So far, there are two planned features:
* Groups Management
* Recordings Management

Groups can have users assigned to them (through op/presenter/other), however I would like a central place to manager users (a users.json or similar).
Modifying a user there (e.g. a password change) would mean updating all user references in group files as well. This should work, however I'm
curious whether there are alternatives to this.

Also, I don't know yet how to deal with actions like group renaming or deletion. The file action itself is not that complicated, but how
would Galene respond to a removed/renamed group? I assume the group is kept in memory? Should I connected the Galene manager
backend with Galene itself (using protocol.js) and kick all users out, before attempting to remove the group for instance?
If so, would it be an idea to introduce a 'hidden' superuser, that can act on behalf of such a backend without showing up
in the Galene user list?


[-- Attachment #1.2: Type: text/html, Size: 1870 bytes --]

[-- Attachment #2: pyrite-manager.png --]
[-- Type: image/png, Size: 62635 bytes --]

                 reply	other threads:[~2021-09-27 19:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \
    --subject='Re: [Galene] Pyrite Manager Interface & Users' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox