From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass (mailfrom) smtp.mailfrom=protonmail.com (client-ip=185.70.40.131; helo=mail-40131.protonmail.ch; envelope-from=jvanveen@protonmail.com; receiver=) Authentication-Results: mail.toke.dk; dkim=pass (1024-bit key) header.d=protonmail.com header.i=@protonmail.com header.b=sS1nkNhG Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) by mail.toke.dk (Postfix) with ESMTPS id ACFC188BC5A for ; Mon, 23 Aug 2021 09:14:43 +0200 (CEST) Date: Mon, 23 Aug 2021 07:14:39 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1629702880; bh=iiXMJaQLK+IRoNsv8OU2seTTr04aA39zHF/Js2+T0A4=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=sS1nkNhG4YFt6B847Jkzlw4P7ziFYm6i3zHx3vWdLvXJENWSQYx8ZBpN5NhBBiIXd GN5yRfOuDOGegww43fdy/ARq6p6mGKuVIQD3QN5VIt16uPamvvUtFL3rlFXfpftW9y 4p2FSqs0ey28al70gBZkkzsOd/rNTE5nuY6KrSdk= To: Juliusz Chroboczek From: Jeroen van Veen Message-ID: <4BJAfKoyVo5cYBIDiKilE42niN_E0L7XbdXL3ZrNRREXM3JiF4YiqCDfeQAej7Eipu1PWrBmnvANCORZVqaC_ejORpzx7WYL_5T45IyMKKs=@protonmail.com> In-Reply-To: <878s0tlguf.wl-jch@irif.fr> References: <878s0tlguf.wl-jch@irif.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,WEIRD_PORT shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch Message-ID-Hash: 4PIXOY7FMXBCK5RLCMOOQVEHNWZIJYWK X-Message-ID-Hash: 4PIXOY7FMXBCK5RLCMOOQVEHNWZIJYWK X-MailFrom: jvanveen@protonmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "galene@lists.galene.org" X-Mailman-Version: 3.3.4 Precedence: list Reply-To: Jeroen van Veen Subject: [Galene] Re: Updating groups in a Galene instance 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: Hey Juliusz, Thanks for explaining. Making a http request to the group is fine. In that case I would trigger a http request to the groups endpoint after a group has been added. Would that work the same way for deleted groups and modified groups? Also, would that work the same way with data/passwd? The credentials in data/passwd may be useful for the administrator account. -- Jeroen =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Op zondag 22 augustus 2021 om 4:00 PM schreef Juliusz Chroboczek : > > I think I read a while back that groups are automatically updated, as > > > files change? > > The group will be updated the first time the file is needed. To make the > > group appear in public groups, just access the /group/whatever page (you > > don't need to actually login, just accessing the page is enough). > > If you prefer the command line, just do > > curl -kI https://galene.example.org:8443/group/whatever > > or > > wget --no-check-certificate -O /dev/null https://localhost:8443/group/wha= tever > > Shall I make Galene re-check the public groups periodically? Say, every > > 20 minutes or so? > > -- Juliusz > > Galene mailing list -- galene@lists.galene.org > > To unsubscribe send an email to galene-leave@lists.galene.org