From: "Timothée Jaussoin" <edhelas@movim.eu>
To: galene@lists.galene.org
Subject: [Galene] Galene HTTP API error and various feedback
Date: Thu, 9 Jul 2026 17:43:19 +0200 [thread overview]
Message-ID: <a83f751c-57d9-42ac-9fd2-e048f68dcaf3@movim.eu> (raw)
Hi,
Thanks for the awesome work, I'm currently trying to wrap Galene into my
project and I have an HTTP API error and a few feedback to provide as well:
curl -v -X PUT -u "admin:123" -H "Accept: */*" -H "If-None-Match:*" -H
"Content-Type:application/json"
http://localhost:8444/galene-api/v0/.groups/city-watch-4
Is returning:
2026/07/09 17:25:25 HTTP server error: EOF
Where
./galenectl create-group -group city-watch4
Works properly, with galenetctl.json config file being
{
"server": "http://localhost:8444",
"admin-username": "admin",
"admin-password": "123"
}
Feedback:
1. Its not written in the documentation that the API authentication is
actually using Basic Auth, its a small thing but I had to dive in into
galenectl code to understand that
2. I'd really like to be able to directly pass the admin-username and
admin-password or directly an admin-api-key when launching ./galene,
this will allow projects that wraps Galene like mine to not have to deal
with galenectl and its custom file and generate a random
username/password or api-key each time galene is launched.
3. For projects that wrap Galene it would also be interesting if the API
calls and open Websockets requests could be restricted to the local
machine only (to prevent so security issues if the API is unfortunatelly
exposed publicly).
4. I'm not there yet but it seems that each "user" have to create a
dedicated Websocket (see
https://galene.org/galene-protocol.html#connecting) when wrapping Galene
server side. This means that the wrapper will have to maintain dozens of
Websockets. Would it be possible to provide a "admin" Websocket where
all the messages are sent through it (with a specific user id to
differenciate them) ?
Thanks again for this really nice project :)
Regards,
edhelas
reply other threads:[~2026-07-09 15:43 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=a83f751c-57d9-42ac-9fd2-e048f68dcaf3@movim.eu \
--to=edhelas@movim.eu \
--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