marcusholtz/partylinepager-full repository overview

⁠marcusholtz/partylinepager-full

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.

⁠Supported Architectures

⁠Quick Start: Wizard Mode

Pull and run the web terminal. Configure adapters, policy, and providers through a browser.

⁠docker-compose (recommended)

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

services:
  partylinepager:
    image: marcusholtz/partylinepager-full:latest
    container_name: partylinepager
    restart: unless-stopped
    ports:
      - "7681:7681"
    volumes:
      - ./config:/config
    environment:
      - TTYD_CREDENTIAL=admin:changeme

Open http://<host>:7681 and follow the wizard.

⁠docker cli

docker run -d \
  --name partylinepager \
  --restart unless-stopped \
  -p 7681:7681 \
  -v ./config:/config \
  -e TTYD_CREDENTIAL=admin:changeme \
  marcusholtz/partylinepager-full:latest

⁠First run

1. Open http://<host>:7681 in a browser
2. The wizard walks you through adapter setup (Telegram, Matrix, IRC, etc.)
3. Configure which providers to enable (tor, i2p, rns, web)
4. Config files are written to /config automatically
5. Start the daemon from the wizard menu

About five minutes of configuration, then a 20+ minute first build you can walk away from.

⁠Quick Start: Headless Daemon

Run the daemon without a web terminal. Requires valid config from a prior wizard run.

⁠docker-compose

services:
  partylinepager:
    image: marcusholtz/partylinepager-full:latest
    container_name: partylinepager
    restart: unless-stopped
    volumes:
      - ./config:/config
    environment:
      - PLP_HEADLESS=1
      - PLP_PROVIDERS=tor,i2p,rns,web
      - TELEGRAM_TOKEN=your-bot-token

⁠docker cli

docker run -d \
  --name partylinepager \
  --restart unless-stopped \
  -v ./config:/config \
  -e PLP_HEADLESS=1 \
  -e PLP_PROVIDERS=tor,i2p,rns,web \
  -e TELEGRAM_TOKEN=your-bot-token \
  marcusholtz/partylinepager-full:latest

No ttyd, no wizard, no port 7681. Administration is docker exec only:

docker exec partylinepager partylinepagerctl --state /config/state roster
docker exec partylinepager partylinepagerctl --state /config/state pause

⁠Parameters

⁠Core

⁠Adapters

Enable an adapter by providing its credentials. Only enabled adapters receive room notifications.

⁠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

# Logs: look for "partylinepagerd is up"
docker logs partylinepager

# Processes: tini, ttyd (if not headless), partylinepagerd
docker exec partylinepager ps aux

# Roster check:
docker exec partylinepager partylinepagerctl --state /config/state roster

⁠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