bridge-manager

Beeper Bridge Manager

A tool for running self-hosted bridges with the Beeper Matrix server.

The primary use case is running custom/3rd-party bridges with Beeper. You can connect any^† standard Matrix application service to your Beeper account without having to self-host a whole Matrix homeserver. Note that if you run 3rd party bridges that don't support end-to-bridge encryption, message contents will be visible to Beeper servers.

_{†caveat: hungryserv does not implement the entire Matrix client-server API, so it's possible some bridges won't work - you can report such cases in the self-hosting support room linked below or in GitHub issues here}

You can also self-host the official bridges for maximum security using this tool (so that message re-encryption happens on a machine you control rather than on Beeper servers). However, not all the official bridges are supported yet. See the "Official bridges" section below for instructions and the list of supported bridges.

Please note that self-hosted bridges are not entitled to the usual level of customer support on Beeper. If you need help with self-hosting bridges using this tool, please join #self-hosting:beeper.com instead of asking in your support room.

Usage

1. Download the latest binary from GitHub releases or actions.
   • Alternatively, you can build it yourself by cloning the repo and running ./build.sh. Building requires Go 1.19 or higher.
   • bbctl supports amd64 and arm64 on Linux and macOS. Windows is not supported natively, please use WSL.
2. Log into your Beeper account with bbctl login.

Then continue with one of the sections below, depending on whether you want to run an official Beeper bridge or a 3rd party bridge.

Official bridges

1. Run bbctl run <name> to run the bridge.
   • <name> should start with sh- and consist of a-z, 0-9 and -.
   • If <name> contains the bridge type, it will be automatically detected. Otherwise pass the type with --type <type>.
   • Currently supported types: discord, whatsapp, imessage, heisenbridge, gmessages
   • The bridge will be installed to ~/.local/share/bbctl. You can change the directory in the config file at ~/.config/bbctl.json.
2. For now, you'll have to configure the bridge by sending a DM to the bridge bot. Configuring self-hosted bridges through the chat networks dialog will be available in the future. Spaces and starting chats are also not yet available, although you can start chats using the pm command with the bridge bot.

3rd party bridges

1. Run bbctl register -a <address> <name> to generate an appservice registration file.
   • <address> should be a publicly reachable https address where the Beeper server will push new events.
   • <name> is a short name for the bridge (a-z, 0-9, -). The name should start with sh-. The bridge user ID namespace will be @<name>_.+:beeper.local and the bridge bot will be @<name>bot:beeper.local.
2. Now you can configure and run the bridge by following the bridge's own documentation.

Note that the homeserver URL may change if you're moved to a different cluster. In general, that shouldn't happen, but it's not impossible.

If you want to get the registration again later, you can add the --get flag. Just re-running register is allowed too, but you need to provide the address again if you do that (which also means if you want to change the address, just re-run register with the new address).

You can use --json with register to get the whole response as JSON instead of registration YAML and pretty-printed extra details. This may be useful if you want to automate fetching the homeserver URL.

Deleting bridges

If you don't want a self-hosted bridge anymore, you can delete it using bbctl delete <name>. Deleting a bridge will permanently erase all traces of it from the Beeper servers (e.g. any rooms and ghost users it created). For official bridges, it will also delete the local data directory with the bridge config, database and python virtualenv (if applicable).