From: Juliusz Chroboczek <jch@irif.fr>
To: Dirk-Willem van Gulik <dirkx@webweaving.org>
Cc: galene@lists.galene.org
Subject: [Galene] Re: wildcard users
Date: Mon, 02 Nov 2026 13:27:41 +0100 [thread overview]
Message-ID: <87h5hzctaa.wl-jch@irif.fr> (raw)
In-Reply-To: <CAEDFD8A-5280-4662-8B57-6A6CEA233A69@webweaving.org>
> as that is much easier to fit into our automation/IDS-es which is fairly
> limited in terms of what networking it can do
[...]
> will look if we can still somehow use the API in lieu of the files
No need to change, in your setup it's clearly easier to edit the files
directly. And you're obviously not worried about race conditions since
Galene is not running when you generate the files.
(I really should look into providing a machine-readable schema for Galene's
configuration files. I like CDDL myself, but I guess that most folks
already have the tooling for JSON-Schema.)
-- Juliusz
prev parent reply other threads:[~2026-11-02 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 11:12 [Galene] wildcard users Dirk-Willem van Gulik
2026-11-02 12:05 ` [Galene] " Juliusz Chroboczek
2026-11-02 12:13 ` Dirk-Willem van Gulik
2026-11-02 12:27 ` 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=87h5hzctaa.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=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