vvvomit/interzone
Watch
1
0
Fork
You've already forked interzone
 0
Code Issues Pull requests Projects Releases 50 Packages Wiki Activity Actions
Page: Components
Pages
Blackout mode fa Blackout mode Components Administration fa Components Administration Components Authentication fa Components Authentication Components Bots fa Components Bots Components Bridges fa Components Bridges Components Calls and extras fa Components Calls and extras Components Clients fa Components Clients Components Core services fa Components Core services Components File storage fa Components File storage Components fa Components Home Screenshots fa Screenshots Setup guide fa Setup guide
2 Components
vvvomit edited this page 2026-10-30 04:44:29 +03:30
Table of contents

فارسی · Home · Setup guide

Components

interzone can install 63 components on top of the homeserver. This page says how to add, change and remove them; each category has its own page with a guide for every component in it:

Category What's in it
Core services Calls relay (Coturn), email, the base domain, dynamic DNS, an external database
Clients Web apps to chat in: Element, Cinny, Sable, Hydrogen, SchildiChat, FluffyChat, Commet
Authentication MAS logins, admin panels, LDAP and other ways to log in, antispam
File storage Keeping media in S3, or in matrix-media-repo
Bridges Telegram, WhatsApp, Signal, Discord, email, IRC and 9 more
Bots AI chat, reminders, a helpdesk, moderation, web forms
Administration Grafana, Borg backups, cleanup, statistics
Calls & extras Element Call, Jitsi, Etherpad, ntfy push, comments, and more

Adding a component

While setting up, on the Components step. Later, from Manage: Change the setup (w) and ctrl+n until you reach Components. Your earlier answers are kept.

The Components step

  1. ←→ switch between the category tabs. / searches every component by name or description.
  2. ↑↓ move, space ticks. The card at the top says what the selected one does, the subdomain it needs (DNS) and the playbook document about it. Ones marked needs settings ask for something on the next step.
  3. Press enter for Settings and fill in what's marked *.

The Settings step

  1. Press ctrl+n for Review. If the component has a subdomain of its own, z shows the DNS record to add; add it and press c until the check is green.
  2. Press enter, then y. Running the install again is safe: your data and the other components stay as they are.

A component needs settings interzone doesn't ask for? On Settings, move past the last field (or click Advanced on the right) and paste the lines from the playbook's document there. They are added to the end of vars.yml and win over interzone's own.

Changing or removing one

Change its settings the same way: Change the setup (w), then Settings, Review, y.

To remove one, untick it and deploy. Unticking stops interzone configuring it, but the playbook's quick install doesn't remove what's already on the server: run Start, stop or reinstall services (p) and reinstall everything to clear it out.

Bot and bridge addresses

Bots and bridges live on your base domain, not on matrix.: the Telegram bridge's bot is @telegrambot:example.org, not @telegrambot:matrix.example.org. Start a chat with it from Element like with anyone else.

Each guide links the playbook's own document for the component. If GitHub is out of reach, the same documents are in the playbook's mirror: https://itsjustadream.g0th.ir/spantaleev/matrix-docker-ansible-deploy/src/branch/master/docs.

Home

English

فارسی