Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
To: galene@lists.galene.org
Subject: [Galene] Virtual groups v.s. new API branch
Date: Tue, 13 Feb 2024 10:20:36 +0100	[thread overview]
Message-ID: <9C5BACF6-2E9E-45E2-A3CB-619BB60DE670@webweaving.org> (raw)

I've been using a bit of a hack in 

	group/Update)
		https://github.com/jech/galene/blob/0f53bf037368a2a82a0af30ffd07bf5943b0abb1/group/group.go#L1335

and especially
	group/GetDescription()
		https://github.com/jech/galene/blob/0f53bf037368a2a82a0af30ffd07bf5943b0abb1/group/group.go#L1007

to be able to have the /var/db/galene/groups directory (i.e. the -groups cmd line argument) live on a nearby webserver. Basically it just fetches the JSON remote every time. 

The main reason for this is to allow the ad-hoc creation of short lived ephemeral rooms that you discover you need, rather than preconfigured. (the jsons are generated on the fly in typical 'cgi-bin' conceptual fashion).

And this http/rev-proxy separation also makes it easier to limit the access galene has; much like the galene-ldap separation/pattern.

Now I just noticed this https://github.com/jech/galene/tree/api. Fair to assume that this will be the `proper' way ? 

Or is there also a plan for a more 'reactive' mechanism -- i.e. one that does not require a configuration sitting pretty `ahead' of time. We're finding this quite useful (and then lock the room one we're started).

With kind regards,

Dw





             reply	other threads:[~2024-02-13  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  9:20 Dirk-Willem van Gulik [this message]
2024-02-13 13:14 ` [Galene] " Juliusz Chroboczek
2024-02-13 13:55   ` Dirk-Willem van Gulik
2024-02-13 15:15     ` Juliusz Chroboczek
2024-03-03 16:07     ` Juliusz Chroboczek

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=9C5BACF6-2E9E-45E2-A3CB-619BB60DE670@webweaving.org \
    --to=dirkx@webweaving.org \
    --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