marcusholtz/partylinepager repository overview

⁠marcusholtz/partylinepager

Open a room on a chat network, and everyone who subscribed on any chat network gets a way into it. Supports Tor, I2P, Reticulum party lines, and WebRTC browser links. Fans credentials to nine chat networks. No database, no accounts, nothing remembered.

This is the daemon-only image: one container per network/transport you enable, no ttyd, no bundled wizard, no port 7681.

There is no separate "wizard edition" of this image.

The setup wizard (partylinepager.sh) is a script in the git repo⁠, you can download.

It runs on your host, writes .env, policy.toml and adapters.toml for you, and then calls docker compose to pull and run this exact image.

⁠Supported Architectures

⁠Quick Start: Wizard (recommended)

git clone https://github.com/MarcusHoltz/partylinepager.git && cd partylinepager
./partylinepager.sh

• Menu walks you through: adapters → policy → which providers
• Writes config/policy.toml, config/adapters.toml, .env
• Sets COMPOSE_FILE to pull marcusholtz/partylinepager:latest (not build)
• Runs docker compose up -d for you
• Same script doubles as admin console after setup (roster, pause/resume, Signal link)
• To hand-edit the TOML yourself: quit the script first, it owns those files while running

⁠Quick Start: Manual (no wizard)

For scripted or config-management deployments where you'd rather not clone the whole repo. Requires a policy.toml and adapters.toml already sitting in ./config, written against the config reference⁠.

⁠docker-compose

Save as docker-compose.yml, then run docker compose up -d:

services:
  partylinepagerd:
    image: marcusholtz/partylinepager:latest
    container_name: partylinepagerd
    restart: unless-stopped
    user: "1000:1000"
    volumes:
      - ./config:/etc/partylinepager
    environment:
      - RUST_LOG=info
      - TELEGRAM_TOKEN=your-bot-token
    command: ["--state", "/etc/partylinepager/state"]

⁠docker cli

docker run -d \
  --name partylinepagerd \
  --restart unless-stopped \
  --user 1000:1000 \
  -v ./config:/etc/partylinepager \
  -e RUST_LOG=info \
  -e TELEGRAM_TOKEN=your-bot-token \
  marcusholtz/partylinepager:latest \
  --state /etc/partylinepager/state

⁠First run

1. policy.toml and adapters.toml are already in ./config (see above)
2. --user matches your host uid:gid, or ./config/state ends up root-owned
3. Only the adapters you set a token for should be [enabled = true] in adapters.toml
4. docker compose run --rm partylinepagerd --check validates config before starting anything
5. docker compose up -d starts the daemon

No web terminal, no port to publish. Administration is docker compose exec only, same as any headless deployment.

docker compose exec partylinepagerd partylinepagerctl who
docker compose exec partylinepagerd partylinepagerctl approve telegram:123456789

⁠Parameters

⁠Core

⁠Adapters

Enable an adapter by setting enabled = true under its section in adapters.toml, then pass the matching secret through -e. Only adapters you pass a secret for receive room notifications.

Signal ([signal]) takes no token here: it needs a second container, bbernhard/signal-cli-rest-api⁠, linked or registered separately and mounted at /home/.local/share/signal-cli. Apprise (apprise: endpoints, added at runtime, not in adapters.toml) needs caronc/apprise⁠ as a stateless sidecar.

⁠Party lines (Tor, I2P, Reticulum)

Off by default. Turning one on in policy.toml ([provider.tor], [provider.i2p], [provider.rns]) means this container also needs the Docker socket, because the provider hooks bring the transport up and down as its own container.

[provider.web] needs neither. If you're only running web rooms, leave the socket out entirely: docker compose config | grep -c docker.sock should print 0.

⁠How It Works

A subscriber sends a command (partyline or web) on any connected chat network. The engine:

1. Spins up a fresh room on the requested transport (new .onion, .b32.i2p, destination hash, or URL)
2. Fans the connection details to every subscriber whose quiet hours are closed
3. Tears the room down when the TTL expires

One room at a time. No occupancy tracking, no catch-up, no record of who joined.

⁠Verifying a Deployment

# Config check before ever starting the daemon
docker compose run --rm partylinepagerd --check

# Logs: look for "ok" from the check, then normal startup
docker compose logs partylinepagerd

# Roster check
docker compose exec partylinepagerd partylinepagerctl who

⁠The Party Line Trifecta

Three transports, same encryption, same TUI:

Tor Party Line⁠	I2P Party Line⁠	Reticulum Party Line⁠

PartylinePager orchestrates all three (plus WebRTC) and fans credentials across nine chat networks.

⁠License

MIT