From: "Michael Ströder" <michael@stroeder.com> To: galene@lists.galene.org Subject: [Galene] Re: read groups from API Date: Sun, 3 Jan 2021 03:12:18 +0100 [thread overview] Message-ID: <f5f2d6b9-47f7-6678-6b3c-db520be35a64@stroeder.com> (raw) In-Reply-To: <87eej2hm1p.wl-jch@irif.fr> On 1/3/21 2:00 AM, Juliusz Chroboczek wrote: >> It would be helpful if groups could be retrieved from a simple web >> service which just returns the JSON data. > > Why does that need to be part of Galène ? Why can't it be a separate > service that has access to the filesystem with Galène's configuration > files? Of course syncing files would be possible and I will do that if there's no other possibility. But it's more complicated with some sync latency. > This way, Galène doesn't need write access to its configuration > directory, which is good for security and simplifies deployment (you can > run it in a read-only container). Galène should not write to its config. But instead of reading a file from the filesystem it could just send a HTTP(S) request to an API (with simple HTTP basic authentication). >> This would make it possible to integrate with other database-backed >> management systems so that implementing #11 is not really needed. > > I fully agree that the management interface should not be part of Galène > itself: Galène never writes to disk except if you ask it to record a file, Be assured I highly appreciate this approach. > and that two instances of Galène can use a single configuration > directory. I'd argue that using a web API is much simpler than a shared network file system. > - changes to group definition files will be picked up the next time > a client connects; Why not just query the group from an API? > - changes to the ice-servers.json file will be picked up after two > minutes at most, but will only apply to new clients; > - changes to the SSL key or to the data/passwd file are not picked up > yet, but that is planned in the future. Both not that important for me. Not sure how others feel about this. > So my opinion is that an administrative interface should not be hacked > into Galène +1, especially because it will never be complete (for whatever defintion of "complete" one might come up with). >> I'd volunteer to implement an example web service based on Python with >> fastapi module. > > Sure, and don't hesitate to suggest improvements to the configuration file > format. Yes, I have some ideas like validity period or similar. Will send a separate message soon. > In particular, I'm not particularly fond of the current > permissions system Agreed. ;-) Thanks again for Galène. Ciao, Michael.
next prev parent reply other threads:[~2021-01-03 2:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-02 22:33 [Galene] " Michael Ströder 2021-01-03 1:00 ` [Galene] " Juliusz Chroboczek 2021-01-03 2:12 ` Michael Ströder [this message] 2021-01-03 12:31 ` Juliusz Chroboczek 2021-01-03 12:33 ` Michael Ströder
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=f5f2d6b9-47f7-6678-6b3c-db520be35a64@stroeder.com \ --to=michael@stroeder.com \ --cc=galene@lists.galene.org \ --subject='[Galene] Re: read groups from API' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox