From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; dkim=pass header.d=irif.fr header.i=@irif.fr header.a=rsa-sha256 header.s=dkim-irif header.b=WvT80c8j; arc=none (Message is not ARC signed); dmarc=none Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by mail.toke.dk (Postfix) with ESMTPS id 6D0F9197E35E for ; Mon, 02 Nov 2026 14:04:39 +0100 (CET) Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 6A2D4WFU028621; Mon, 2 Nov 2026 14:04:32 +0100 Received: from mailhub.math.univ-paris-diderot.fr (unknown [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 769156386C; Mon, 2 Nov 2026 14:04:32 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=irif.fr; h= content-type:content-type:mime-version:user-agent:references :in-reply-to:subject:subject:from:from:message-id:date:date :received:received; s=dkim-irif; t=1793624671; x=1794488672; bh= FzFx6EzWeT4zggj31AoK0TrAw3OOUlxHwkckiNqxkoo=; b=WvT80c8jF8WVlhqL WFN0Af5UyB/poXfYuMF17AdWdh/d2Zyhh7ucBcus2c0Y7idpn0+YFCcn+pTn2sAy T9yLSORuUB+rScW+25FeqQWYvDwyskcYPIHlXPHMCCW1CW/2d5SuBmI7M5Kz7DYF SZ2pIqycjkXVgb4q0OZKlGv9sq5To/K+d0R6fm9ZyQ5y5Ngu3/pavLcCr2tl71sr wtA/L9c4hznK6GeLbIoqxq6m3xN8uvrRuxHcswKMcqUNbH3Q8a7eaQNAQjxRa8wi z6bOt1mtiVs8tx4asCo0TXhMpPJ1VKrgppPMK2+N3KhQ6/H0GCUxZBjaYaT1o9Hl tysEKg== X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 3hquKAgHNxJs; Mon, 2 Nov 2026 14:04:31 +0100 (CET) Received: from trurl.irif.fr (unknown [82.64.191.149]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 084A763AB7; Mon, 2 Nov 2026 14:04:30 +0100 (CET) Date: Mon, 02 Nov 2026 14:04:30 +0100 Message-ID: <87fqxjcrkx.wl-jch@irif.fr> From: Juliusz Chroboczek To: Francis Bolduc Cc: Michael McMahon , galene@lists.galene.org In-Reply-To: References: <87ld7bcvl4.wl-jch@irif.fr> <87ik2fctl8.wl-jch@irif.fr> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/30.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 02 Nov 2026 14:04:32 +0100 (CET) X-Miltered: at korolev with ID 6AE88A60.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 6AE88A60.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/ X-j-chkmail-Score: MSGID : 6AE88A60.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000 X-j-chkmail-Status: Ham Message-ID-Hash: OXB4PVRF5RUZ4ZNZUEYH7X3HKPALJJ4L X-Message-ID-Hash: OXB4PVRF5RUZ4ZNZUEYH7X3HKPALJJ4L X-MailFrom: jch@irif.fr X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Subject: [Galene] Re: Anonymous access List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > 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: - PHP: 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