{"id":"6a8afcc06eebeb55735399cc","title":"2026 08 23 Issue 357","path":"how-to/committee/release-notes/2026-08-23-issue-357","contentMarkdown":"# 23-Aug-2026 — open-source Jitsi video meetings with self-hosting, admin config and committee planning [#357](https://github.com/nbarrett/ngx-ramblers/issues/357)\n\n## [build 846](https://github.com/nbarrett/ngx-ramblers/actions/runs/32643487238) — [commit f723e02](https://github.com/nbarrett/ngx-ramblers/commit/f723e025408f60e4c13faba1d932d38b37097d9a) · [build 848](https://github.com/nbarrett/ngx-ramblers/actions/runs/32661203418) — [commit 9c9f50d](https://github.com/nbarrett/ngx-ramblers/commit/9c9f50dc4167ff530ac22130812f42890c4af8e4)\n\n_____\n\n## What's new\n\nGroups can run committee meetings from the site. Plan a meeting on the walks calendar - in person, online or hybrid - with an agenda, an email invite and a calendar attachment, then edit or cancel it later with the invitees kept informed. Online meetings use Jitsi: free public Jitsi by default with no setup, or a single self-hosted server that runs the whole estate's meetings, with member identity, committee moderators, shared notes and AI minutes. That self-hosted server is one container, deployed once from admin to its own Fly app and shared by every site, so calls run on hardware we control with no third party in the middle and nothing recorded.\n\nBuild 848 fixed the self-hosted server's first deployment: two of its internal services need passwords, and the deploy was not setting them, so the container stopped at start-up. The deploy now sets those passwords automatically and the server starts first time. Nothing changes for groups using the default free public video service.\n\n## At a glance\n\n- Plan a committee meeting on the walks calendar: pick a date, choose in person, online or hybrid, draft an agenda, and invite guests and lists by email with a calendar attachment\n- Open an existing meeting from the calendar or the booked-meeting banner to edit it, or cancel it and notify everyone who was invited\n- Online meetings run on Jitsi: free public rooms by default with no setup, or a self-hosted server for member identity, committee moderators, shared notes and AI minutes\n- Self-hosting is one container for the whole estate, deployed once from admin to its own Fly app; the host and identity are set once in a global Video Meetings config and carried to every site, with only the brand name set per site\n- Deploying the self-hosted server now works first time - the internal service passwords are set by the deploy, with nothing to configure\n- In-person and hybrid meetings show a venue on the agenda and invite; online and hybrid get a join link\n- The calendar shows only committee meeting file types, so financial statements and the like stay off it\n- Time pickers keep the incrementers in the middle of the number boxes, including on Walk Edit\n- No calls are recorded or stored; video meetings stay off unless the estate turns them on","contentHtml":"<h1>23-Aug-2026 — open-source Jitsi video meetings with self-hosting, admin config and committee planning <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/357\">#357</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/32643487238\">build 846</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/f723e025408f60e4c13faba1d932d38b37097d9a\">commit f723e02</a> · <a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/32661203418\">build 848</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/9c9f50dc4167ff530ac22130812f42890c4af8e4\">commit 9c9f50d</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<p>Groups can run committee meetings from the site. Plan a meeting on the walks calendar - in person, online or hybrid - with an agenda, an email invite and a calendar attachment, then edit or cancel it later with the invitees kept informed. Online meetings use Jitsi: free public Jitsi by default with no setup, or a single self-hosted server that runs the whole estate&#39;s meetings, with member identity, committee moderators, shared notes and AI minutes. That self-hosted server is one container, deployed once from admin to its own Fly app and shared by every site, so calls run on hardware we control with no third party in the middle and nothing recorded.</p>\n<p>Build 848 fixed the self-hosted server&#39;s first deployment: two of its internal services need passwords, and the deploy was not setting them, so the container stopped at start-up. The deploy now sets those passwords automatically and the server starts first time. Nothing changes for groups using the default free public video service.</p>\n<h2>At a glance</h2>\n<ul>\n<li>Plan a committee meeting on the walks calendar: pick a date, choose in person, online or hybrid, draft an agenda, and invite guests and lists by email with a calendar attachment</li>\n<li>Open an existing meeting from the calendar or the booked-meeting banner to edit it, or cancel it and notify everyone who was invited</li>\n<li>Online meetings run on Jitsi: free public rooms by default with no setup, or a self-hosted server for member identity, committee moderators, shared notes and AI minutes</li>\n<li>Self-hosting is one container for the whole estate, deployed once from admin to its own Fly app; the host and identity are set once in a global Video Meetings config and carried to every site, with only the brand name set per site</li>\n<li>Deploying the self-hosted server now works first time - the internal service passwords are set by the deploy, with nothing to configure</li>\n<li>In-person and hybrid meetings show a venue on the agenda and invite; online and hybrid get a join link</li>\n<li>The calendar shows only committee meeting file types, so financial statements and the like stay off it</li>\n<li>Time pickers keep the incrementers in the middle of the number boxes, including on Walk Edit</li>\n<li>No calls are recorded or stored; video meetings stay off unless the estate turns them on</li>\n</ul>\n"}