From: Juliusz Chroboczek <jch@irif.fr>
To: Francis Bolduc <fbolduc@gmail.com>
Cc: Michael McMahon <michael@gnu.org>, galene@lists.galene.org
Subject: [Galene] Re: Anonymous access
Date: Mon, 02 Nov 2026 14:04:30 +0100 [thread overview]
Message-ID: <87fqxjcrkx.wl-jch@irif.fr> (raw)
In-Reply-To: <CAHpL4=ize4AgA_5txd7eSAqCzkdszJxSiomXTPCFmndRG2jXrQ@mail.gmail.com>
> My only gripe with galenectl is that it needs galene to run to work
Yes, that's the design.
> I understand the utility of changing configs on a live server. But
> have you considered having galenectl work directly on the JSON files
The API is required, since people want to be able to programatically
administer a running Galene server from arbitrary languages:
- JavaScript: static/change-password.js
- Python: <https://github.com/zulip/zulip/pull/39792>
- PHP: <https://github.com/movim/movim/tree/master/app/Workers/Galener/>
Galenectl is just a thin wrapper around the API, it's a convenient
byproduct. But I agree this has some limitations:
- the server has to be running;
- there is a need for a Galene-specific authorisation mechanism,
adequate Unix permissions are not enough.
Since editing files on disk is still supported, I think this doesn't
warrant spending time on writing a second backend for galenectl.
> and then send SIGHUP to the running galene process (if any) to reload
> configs?
No need, if you modify a file on disk Galene will notice it at the next
login and invalidate its cached copy. (Assuming your filesystem
implements modification time correctly, please don't put your config on
a CP/M filesystem.)
-- Juliusz
prev parent reply other threads:[~2026-11-02 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 22:53 [Galene] Anonymous access Francis Bolduc
2026-11-01 23:56 ` [Galene] " Michael McMahon
2026-11-02 11:37 ` Juliusz Chroboczek
2026-11-02 12:03 ` Francis Bolduc
2026-11-02 12:21 ` Juliusz Chroboczek
2026-11-02 12:44 ` Francis Bolduc
2026-11-02 13:04 ` Juliusz Chroboczek [this message]
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=87fqxjcrkx.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=fbolduc@gmail.com \
--cc=galene@lists.galene.org \
--cc=michael@gnu.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