Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] ANNOUNCE: Galene 0.9
Date: Sun, 26 May 2024 20:30:38 +0200	[thread overview]
Message-ID: <87le3w1l4h.wl-jch@irif.fr> (raw)

Dear all,

Galene-0.9 is available by doing

    git clone -b galene-0.9 https://github.com/jech/galene

The main news in this version are a new format for group configuration
files and an HTTP API to administer the group configurations.  There is
currently no UI for the administrative interface, except for a single page
that allows changing a user's password, just under the user name in the
right-hand side menu.

It is possible to start galene-0.9 with your current configuration, and
old-style configuration files will be parsed correctly in most cases.
There are some exceptions:

  - the format of the "config.json" file has changed incompatibly, you
    will need to manually convert any administrator passwords;

  - it is no longer possible to have multiple users with the same username
    and different passwords, you might need to rename some users;

  - it is no longer possible to have multiple wildcard users (users that
    can log-in with an arbitrary password), you might need to make some
    users non-anonymous;

  - the "allow-anonymous" keyword is no longer supported, this is now the
    default behaviour.

In all cases, you should find a friendly warning in the logs, which will
tell you what changes you need to make manually.

A fairly complete changelog follows.

-- Juliusz

26 May 2024: Galene 0.9

  * Reworked the group definition format to be more modular.  There are
    some incompatible changes: multiple users with the same username but
    distinct passords are no longer supported, and the field
    "allow-anonymous" is ignored.
  * Reworked the definition of administrator passwords in config.json.
    The old field "admin" is ignored, a new field "users" is required.
    This is an incompatible change.
  * Implemented an administrative API over HTTP.  Set the field
    "writableGroups" in config.json to enable it.  The API is described in
    the file "README.API", a JavaScript library is in management.js.
  * Implemented a form to allow users to change their password.  If the
    HTTP API is enabled, a link will appear in the side menu.
  * Implemented a new command "/identify" (also availble in the users
    menu) that discloses the IP address from which a user connected.
  * Implemented a contextual menu that triggers on a double click on
    a chat entry.
  * Added a new command "/stopshare".
  * Added a new permission "message" and new commands "shutup" and "unshutup".
  * Changed stateless token validation to attempt all keys rather than
    just the first matching one.

                 reply	other threads:[~2024-05-26 18:30 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

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

  git send-email \
    --in-reply-to=87le3w1l4h.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=galene@lists.galene.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox