vvvomit/interzone
Watch
1
0
Fork
You've already forked interzone
 0
Code Issues Pull requests Projects Releases 50 Packages Wiki Activity Actions
50 releases 50 tags
  • v0.5.26 94d5ac8d8c

    v0.5.26 Stable

    vvvomit released this 2026-10-29 05:54:33 +03:30 | 92 commits to main since this release

    Alerts, rooms, a server tester, and locks that keep a running server safe

    New

    • Alerts. The server checks itself on a timer, even when your computer is off. It looks for failed services, the homeserver not answering, a certificate expiring within 14 days, a disk over 90% full and a mirror not answering. It sends one message when something breaks and one when it's fixed. Messages go to an ntfy topic, to a webhook (Hookshot, Slack, Discord, Mattermost), or into a Matrix room as formatted messages: a coloured headline and a list. Once a day it also sends the playbook's new changelog entries, marking with ★ the ones about your homeserver or components. Find it under Manage › Alerts.
    • Test any Matrix server. A new Test section in the menu takes one or more server names, user IDs or URLs and checks each from this computer, as other servers and apps would:
      • where federation goes (well-known, SRV records or port 8448), the signing keys, and which software and version answer;
      • the client well-known and its CORS header, the client API, the ways to log in and the support file;
      • what Element X needs: sliding sync, OAuth 2.0 logins and a call server.
    • Rooms (Synapse): every room on the server, biggest first. Block or unblock one, delete one for everyone here, or delete its history older than a number of days.
    • Add many users at once from a CSV file with lines of the form username[,password][,admin]. Missing passwords are generated, and all of them are saved next to the file as …-passwords.csv, readable only by you.
    • The Dashboard shows 30 days of history: load, memory and disk as small graphs, and roughly when the disk will be full at the current rate.
    • Review checks more before deploying:
      • the memory and disk your choice of components needs;
      • the ports a firewall must let in, and whether each one gets through from outside;
      • federation, the way a federation tester does;
      • the server as apps see it.
    • DNS records as zone-file lines, to paste into your DNS provider: z on Review, or interzone dns.
    • Updates: see the playbook's new changelog entries first, yours on top, and d does a dry run that shows what an update would change on the server before it does.
    • Federate with only some servers, or with all but some, on the Server step.
    • Maintenance › Disk: see what uses the disk, prune Docker, and set how long media cached from other servers is kept.
    • Plain mode for screen readers and logs: -plain or INTERZONE_PLAIN=1. It gives you no colours, ASCII boxes and bars, and no animation.
    • Start fresh: R on the Servers screen, or --reset, makes interzone forget every server and opens the wizard. Nothing is deleted: its config and data folders are moved aside as *.old-DATE.

    Changed

    • Choices a running server can't survive are locked. After installing or importing a server, its domain, its homeserver and (on Synapse) whether it uses MAS can't be changed in the setup, and deploys refuse to change them. Each lock says why, and what to do instead.
    • --reset used to show empty answers for the active server only. It now resets everything, as Start fresh does.

    Update with interzone self-update or Manage › Update interzone.

    Downloads