ops-jrz1/secrets/secrets.yaml.example
Dan ab5aebb161 Phase 3: Extract and sanitize Matrix platform modules from ops-base
Extracted modules:
- Matrix homeserver (matrix-continuwuity.nix)
- mautrix bridges (slack, whatsapp, gmessages)
- Security modules (fail2ban, ssh-hardening)
- Development services module
- Matrix secrets module

All modules sanitized to remove personal information:
- Domains: example.com, matrix.example.org
- IPs: 10.0.0.x, 203.0.113.10
- Paths: /home/user, /path/to/ops-base
- Emails: admin@example.com

Configuration:
- Updated flake.nix with sops-nix and nixpkgs-unstable
- Updated hosts/ops-jrz1.nix to import all extracted modules
- Added example files (secrets, minimal config)
- Generated flake.lock

Generated with Claude Code - https://claude.com/claude-code
2025-10-13 14:51:14 -07:00

32 lines
1.1 KiB
Plaintext

# Example secrets file for ops-jrz1 Matrix platform
# Copy this file to secrets.yaml and replace with your actual secrets
# Then encrypt with: sops -e -i secrets/secrets.yaml
# Matrix homeserver configuration
matrix-registration-token: "GENERATE_WITH_openssl_rand_hex_32"
# ACME/Let's Encrypt email for certificate notifications
acme-email: "admin@example.com"
# mautrix-slack bridge secrets
mautrix-slack:
app-token: "xapp-YOUR-SLACK-APP-TOKEN"
bot-token: "xoxb-YOUR-SLACK-BOT-TOKEN"
# mautrix-whatsapp bridge secrets (no long-term secrets, QR code pairing)
# Configuration is stored in bridge database after pairing
# mautrix-gmessages bridge secrets
mautrix-gmessages:
# Google Messages pairing data stored in bridge database
google-account-token: "GENERATED_AFTER_PAIRING"
# Fail2ban notification email (optional)
fail2ban-notification-email: "admin@example.com"
# PostgreSQL database passwords
postgresql:
mautrix-slack-password: "GENERATE_SECURE_PASSWORD"
mautrix-whatsapp-password: "GENERATE_SECURE_PASSWORD"
mautrix-gmessages-password: "GENERATE_SECURE_PASSWORD"