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: galenectl
Date: Fri, 25 Oct 2024 16:34:57 +0200	[thread overview]
Message-ID: <87frokz1wu.wl-jch@irif.fr> (raw)

Hi,

I've just merged a management utility for Galene into master.  It's
designed to be easily scriptable but also useful for the command line.


0. Upgrade your Galene instance to current master

(Really do.  In principle, the management interface has been stable for
months, but while developing galenectl I've found and fixed a number of
bugs.)

1. Build galenectl and put it somewhere in your path

    cd galenectl
    go build
    mv galenectl ~/bin/

2. If you haven't done so already, create a server administrator

Type

    galenectl hash-password -type bcrypt

then copy the resulting password into your `data/config.json` file, which
should look like this:

    {
        "writableGroups": true,
        "users": {"jch": {"password": {"type":"bcrypt","key":"..."}, "permissions": "admin"}},
        "publicServer": true
    }

3. Set up your `~/.config/galene/galenectl.json`.  It should look like this:

    {
        "server": "https://galene.example.org:8443/",
        "admin-username": "jch",
        "admin-password": "topsecret"
    }

4. Create a group

    galenectl create-group -group example

5. Create a few users

    galenectl create-user -group example -user jch -permissions op
    galenectl create-user -group example -user bob
    galenectl create-user -group example -wildcard -permissions observe

The first user is a group operator.  The second has default permissions.
The third one is the wildcard user, used for any username other than "jch"
and "bob".

6. Set the user's initial passwords

    galenectl set-password -group example -user jch
    galenectl set-password -group example -user bob
    galenectl set-password -group example -wildcard -type wildcard

We've set ordinary password for users jch and bob (hashed on the client
side, so the server never sees the cleartext password).  As to the
wildcard user, we've set it to have a wildcard password -- any password
will do.

Please test, and let me know if any changes are required.  As to myself,
I'll now implement token management in galenectl, and then setting
individual group parameters.

-- Juliusz


    



    



                 reply	other threads:[~2024-10-25 14:35 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=87frokz1wu.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