From 3e6f210f46e2c1c88abb832c9372dc1c4620b22c Mon Sep 17 00:00:00 2001 From: Lotus CI Date: Wed, 28 Oct 2026 21:08:45 -0400 Subject: [PATCH] Add mautrix-discord bridge config and installer Bot-login Discord bridge on LXC 151: config template (DB password is filled in on the server), systemd unit, and a one-time install script run from the Proxmox node that sets up the PostgreSQL role/database, installs the checksum-verified v0.7.7 binary, generates the appservice registration, adds it to Synapse and restarts Synapse once. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5 --- README.md | 46 ++++ discord-bridge/config.yaml | 386 ++++++++++++++++++++++++++++++++ discord-bridge/install.sh | 103 +++++++++ systemd/mautrix-discord.service | 30 +++ 4 files changed, 565 insertions(+) create mode 100644 discord-bridge/config.yaml create mode 100755 discord-bridge/install.sh create mode 100644 systemd/mautrix-discord.service diff --git a/README.md b/README.md index 547aee4..a9fd466 100644 --- a/README.md +++ b/README.md @@ -26,6 +26,9 @@ matrix/ │ └── index.html # matrix.lotusguild.org landing page ├── draupnir/ │ └── production.yaml # Draupnir config (access token is redacted — see rotation docs below) +├── discord-bridge/ +│ ├── config.yaml # mautrix-discord config (DB password filled in on the server, never committed) +│ └── install.sh # One-time installer, run on the Proxmox node hosting LXC 109 + 151 ├── deploy/ # Auto-deployment infrastructure │ ├── lxc151-hookshot.sh # Deploy script for LXC 151 (matrix/hookshot/livekit) │ ├── lxc106-cinny.sh # Deploy script for LXC 106 (cinny) @@ -41,6 +44,7 @@ matrix/ ├── livekit-graceful-restart.service # oneshot — checks pending restart flag ├── livekit-graceful-restart.timer # Runs every 5 min ├── draupnir.service + ├── mautrix-discord.service # Discord bridge (LXC 151) └── cinny-upstream-check.cron # Installed to /etc/cron.d/ on LXC 106 — runs daily at noon ``` @@ -286,6 +290,7 @@ The token in `draupnir/production.yaml` in this repo is **intentionally redacted | 9002 | Hookshot bridge (appservice) | 127.0.0.1 | | 9003 | Hookshot webhooks | 0.0.0.0 | | 9004 | Hookshot metrics | 0.0.0.0 | +| 29334 | mautrix-discord (appservice) | 127.0.0.1 | | 9100 | node_exporter | 0.0.0.0 | | 9101 | matrix-admin exporter | 0.0.0.0 | | 9500 | webhook (auto-deploy) | 0.0.0.0 | @@ -381,6 +386,45 @@ bash /opt/matrix-config/hookshot/deploy.sh proxmox.js # deploy one --- +## Discord Bridge (mautrix-discord v0.7.7) + +Bridges Discord channels to Matrix rooms on LXC 151. The bridge logs in as a **Discord bot** +(not anyone's personal account, which breaks Discord's ToS): Discord users appear in Matrix as +`@discord_:matrix.lotusguild.org` ghosts, and Matrix users are relayed into Discord through a +channel webhook with their own display name. + +- Bridge bot: `@discordbot:matrix.lotusguild.org` +- Config: `/opt/mautrix-discord/config.yaml` (template in `discord-bridge/config.yaml`; the bridge + rewrites it on start, so it is **not** auto-deployed) +- Registration: `/etc/matrix-synapse/discord-registration.yaml` (listed in `app_service_config_files`) +- Database: `mautrix_discord` on LXC 109, role `mautrix_discord`, allowed from 10.10.10.29 in `pg_hba.conf` +- Service: `systemctl status mautrix-discord`, logs in `journalctl -u mautrix-discord` and `/var/log/mautrix-discord/` +- End-to-bridge encryption is allowed, so it can join encrypted rooms + +**Install (one time):** after this repo's `main` has reached `/opt/matrix-config` on LXC 151, run this +on the Proxmox node hosting LXC 109 and 151. It restarts Synapse once and is safe to re-run. + +```bash +pct exec 151 -- cat /opt/matrix-config/discord-bridge/install.sh | bash +``` + +**Discord side:** Developer Portal → application → Bot. Turn on the **Message Content** and +**Server Members** intents. Invite the bot with the `bot` scope and View Channels, Send Messages, +Read Message History, Manage Webhooks, Attach Files, Add Reactions, Manage Messages and Embed Links. + +**Linking a room:** +1. DM `@discordbot:matrix.lotusguild.org`: `login-token bot ` (the token lives only in the bridge DB) +2. `guilds bridge ` — the server ID comes from Discord Developer Mode → right-click +3. In the Matrix room: invite `@discordbot`, then `!discord bridge ` and `!discord set-relay --create` + +**Rotating the bot token:** reset it in the Developer Portal, then DM the bridge bot `logout` and +`login-token bot `. + +**Not set up yet:** `bridge.public_address`, so Matrix users' avatars aren't shown on their relayed +Discord messages (names are). It needs a public NPM route to `/mautrix-discord/avatar/`. + +--- + ## Moderation (Draupnir v2.9.0) Draupnir runs on LXC 110, manages moderation across all protected rooms (including the Lotus Guild space) via `#management:matrix.lotusguild.org`. @@ -823,6 +867,7 @@ Leaving a space does **not** leave its child rooms; they are independent rooms w - [x] Per-service JS transformation functions (stored in git, auto-deployed) - [x] Per-service virtual user avatars - [x] NPM reverse proxy for `/webhook` path +- [ ] mautrix-discord bridge (bot login + webhook relay) — config and installer in `discord-bridge/` ### Room Structure - [x] The Lotus Guild space with all core rooms @@ -1057,6 +1102,7 @@ All commands use the `!` prefix. Run `!help` in any room for the full list. | Moderation | Draupnir | 2.9.0 | | SSO | Authelia (OIDC) + LLDAP | — | | Webhook bridge | matrix-hookshot | 7.3.2 | +| Discord bridge | mautrix-discord | 0.7.7 | | Reverse proxy | Nginx Proxy Manager | — | | Web client | Lotus Cinny (fork of `cinnyapp/cinny` main) | custom | | Element Call embed | `@lotusguild/element-call-embedded` (self-built fork of `element-hq/element-call`) | 0.20.1-lotus.1 | diff --git a/discord-bridge/config.yaml b/discord-bridge/config.yaml new file mode 100644 index 0000000..9bc0802 --- /dev/null +++ b/discord-bridge/config.yaml @@ -0,0 +1,386 @@ +# Homeserver details. +homeserver: + # The address that this appservice can use to connect to the homeserver. + address: http://127.0.0.1:8008 + # The domain of the homeserver (also known as server_name, used for MXIDs, etc). + domain: matrix.lotusguild.org + + # What software is the homeserver running? + # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here. + software: standard + # The URL to push real-time bridge status to. + # If set, the bridge will make POST requests to this URL whenever a user's discord connection state changes. + # The bridge will use the appservice as_token to authorize requests. + status_endpoint: null + # Endpoint for reporting per-message status. + message_send_checkpoint_endpoint: null + # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246? + async_media: false + + # Should the bridge use a websocket for connecting to the homeserver? + # The server side is currently not documented anywhere and is only implemented by mautrix-wsproxy, + # mautrix-asmux (deprecated), and hungryserv (proprietary). + websocket: false + # How often should the websocket be pinged? Pinging will be disabled if this is zero. + ping_interval_seconds: 0 + +# Application service host/registration related details. +# Changing these values requires regeneration of the registration. +appservice: + # The address that the homeserver can use to connect to this appservice. + address: http://127.0.0.1:29334 + + # The hostname and port where this appservice should listen. + hostname: 127.0.0.1 + port: 29334 + + # Database config. + database: + # The database type. "sqlite3-fk-wal" and "postgres" are supported. + type: postgres + # The database URI. + # SQLite: A raw file path is supported, but `file:?_txlock=immediate` is recommended. + # https://github.com/mattn/go-sqlite3#connection-string + # Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable + # To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql + # Password is filled in on the server by install.sh; never commit it. + uri: postgres://mautrix_discord:DB_PASSWORD@10.10.10.44/mautrix_discord?sslmode=disable + # Maximum number of connections. Mostly relevant for Postgres. + max_open_conns: 20 + max_idle_conns: 2 + # Maximum connection idle time and lifetime before they're closed. Disabled if null. + # Parsed with https://pkg.go.dev/time#ParseDuration + max_conn_idle_time: null + max_conn_lifetime: null + + # The unique ID of this appservice. + id: discord + # Appservice bot details. + bot: + # Username of the appservice bot. + username: discordbot + # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty + # to leave display name/avatar as-is. + displayname: Discord bridge bot + avatar: mxc://maunium.net/nIdEykemnwdisvHbpxflpDlC + + # Whether or not to receive ephemeral events via appservice transactions. + # Requires MSC2409 support (i.e. Synapse 1.22+). + ephemeral_events: true + + # Should incoming events be handled asynchronously? + # This may be necessary for large public instances with lots of messages going through. + # However, messages will not be guaranteed to be bridged in the same order they were sent in. + async_transactions: false + + # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify. + as_token: "This value is generated when generating the registration" + hs_token: "This value is generated when generating the registration" + +# Bridge config +bridge: + # Localpart template of MXIDs for Discord users. + # {{.}} is replaced with the internal ID of the Discord user. + username_template: discord_{{.}} + # Displayname template for Discord users. This is also used as the room name in DMs if private_chat_portal_meta is enabled. + # Available variables: + # .ID - Internal user ID + # .Username - Legacy display/username on Discord + # .GlobalName - New displayname on Discord + # .Discriminator - The 4 numbers after the name on Discord + # .Bot - Whether the user is a bot + # .System - Whether the user is an official system user + # .Webhook - Whether the user is a webhook and is not an application + # .Application - Whether the user is an application + displayname_template: '{{if .Webhook}}Webhook{{else}}{{or .GlobalName .Username}}{{if .Bot}} (bot){{end}}{{end}}' + # Displayname template for Discord channels (bridged as rooms, or spaces when type=4). + # Available variables: + # .Name - Channel name, or user displayname (pre-formatted with displayname_template) in DMs. + # .ParentName - Parent channel name (used for categories). + # .GuildName - Guild name. + # .NSFW - Whether the channel is marked as NSFW. + # .Type - Channel type (see values at https://github.com/bwmarrin/discordgo/blob/v0.25.0/structs.go#L251-L267) + channel_name_template: '{{if or (eq .Type 3) (eq .Type 4)}}{{.Name}}{{else}}#{{.Name}}{{end}}' + # Displayname template for Discord guilds (bridged as spaces). + # Available variables: + # .Name - Guild name + guild_name_template: '{{.Name}}' + # Whether to explicitly set the avatar and room name for private chat portal rooms. + # If set to `default`, this will be enabled in encrypted rooms and disabled in unencrypted rooms. + # If set to `always`, all DM rooms will have explicit names and avatars set. + # If set to `never`, DM rooms will never have names and avatars set. + private_chat_portal_meta: default + + # Publicly accessible base URL that Discord can use to reach the bridge, used for avatars in relay mode. + # If not set, avatars will not be bridged. Only the /mautrix-discord/avatar/{server}/{id}/{hash} endpoint is used on this address. + # This should not have a trailing slash, the endpoint above will be appended to the provided address. + public_address: null + # A random key used to sign the avatar URLs. The bridge will only accept requests with a valid signature. + avatar_proxy_key: generate + + portal_message_buffer: 128 + + # Number of private channel portals to create on bridge startup. + # Other portals will be created when receiving messages. + startup_private_channel_create_limit: 5 + # Should the bridge send a read receipt from the bridge bot when a message has been sent to Discord? + delivery_receipts: false + # Whether the bridge should send the message status as a custom com.beeper.message_send_status event. + message_status_events: false + # Whether the bridge should send error notices via m.notice events when a message fails to bridge. + message_error_notices: true + # Should the bridge use space-restricted join rules instead of invite-only for guild rooms? + # This can avoid unnecessary invite events in guild rooms when members are synced in. + restricted_rooms: false + # Should the bridge automatically join the user to threads on Discord when the thread is opened on Matrix? + # This only works with clients that support thread read receipts (MSC3771 added in Matrix v1.4). + autojoin_thread_on_open: true + # Should inline fields in Discord embeds be bridged as HTML tables to Matrix? + # Tables aren't supported in all clients, but are the only way to emulate the Discord inline field UI. + embed_fields_as_tables: true + # Should guild channels be muted when the portal is created? This only meant for single-user instances, + # it won't mute it for all users if there are multiple Matrix users in the same Discord guild. + mute_channels_on_create: false + # Should the bridge update the m.direct account data event when double puppeting is enabled. + # Note that updating the m.direct event is not atomic (except with mautrix-asmux) + # and is therefore prone to race conditions. + sync_direct_chat_list: false + # Set this to true to tell the bridge to re-send m.bridge events to all rooms on the next run. + # This field will automatically be changed back to false after it, except if the config file is not writable. + resend_bridge_info: false + # Should incoming custom emoji reactions be bridged as mxc:// URIs? + # If set to false, custom emoji reactions will be bridged as the shortcode instead, and the image won't be available. + custom_emoji_reactions: true + # Should the bridge attempt to completely delete portal rooms when a channel is deleted on Discord? + # If true, the bridge will try to kick Matrix users from the room. Otherwise, the bridge only makes ghosts leave. + delete_portal_on_channel_delete: false + # Should the bridge delete all portal rooms when you leave a guild on Discord? + # This only applies if the guild has no other Matrix users on this bridge instance. + delete_guild_on_leave: true + # Whether or not created rooms should have federation enabled. + # If false, created portal rooms will never be federated. + federate_rooms: true + # Prefix messages from webhooks with the profile info? This can be used along with a custom displayname_template + # to better handle webhooks that change their name all the time (like ones used by bridges). + # + # This will use the fallback mode in MSC4144, which means clients that support MSC4144 will not show the prefix + # (and will instead show the name and avatar as the message sender). + prefix_webhook_messages: true + # Bridge webhook avatars? + enable_webhook_avatars: false + # Should the bridge upload media to the Discord CDN directly before sending the message when using a user token, + # like the official client does? The other option is sending the media in the message send request as a form part + # (which is always used by bots and webhooks). + use_discord_cdn_upload: true + # Should the bridge forbid direct messages from users to other users who they aren't friends with? Discord generally + # considers this to be a "risky" action. Note that the bridge will conservatively reject all outgoing DMs from users + # until it has synced that user's relationships from Discord. + forbid_dming_strangers: true + # Proxy for Discord connections + proxy: + # Should mxc uris copied from Discord be cached? + # This can be `never` to never cache, `unencrypted` to only cache unencrypted mxc uris, or `always` to cache everything. + # If you have a media repo that generates non-unique mxc uris, you should set this to never. + cache_media: unencrypted + # Settings for converting Discord media to custom mxc:// URIs instead of reuploading. + # More details can be found at https://docs.mau.fi/bridges/go/discord/direct-media.html + direct_media: + # Should custom mxc:// URIs be used instead of reuploading media? + enabled: false + # The server name to use for the custom mxc:// URIs. + # This server name will effectively be a real Matrix server, it just won't implement anything other than media. + # You must either set up .well-known delegation from this domain to the bridge, or proxy the domain directly to the bridge. + server_name: discord-media.example.com + # Optionally a custom .well-known response. This defaults to `server_name:443` + well_known_response: + # The bridge supports MSC3860 media download redirects and will use them if the requester supports it. + # Optionally, you can force redirects and not allow proxying at all by setting this to false. + allow_proxy: true + # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file. + # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them. + server_key: generate + # Settings for converting animated stickers. + animated_sticker: + # Format to which animated stickers should be converted. + # disable - No conversion, send as-is (lottie JSON) + # png - converts to non-animated png (fastest) + # gif - converts to animated gif + # webm - converts to webm video, requires ffmpeg executable with vp9 codec and webm container support + # webp - converts to animated webp, requires ffmpeg executable with webp codec/container support + target: webp + # Arguments for converter. All converters take width and height. + args: + width: 320 + height: 320 + fps: 25 # only for webm, webp and gif (2, 5, 10, 20 or 25 recommended) + # Servers to always allow double puppeting from + double_puppet_server_map: + example.com: https://example.com + # Allow using double puppeting from any server with a valid client .well-known file. + double_puppet_allow_discovery: false + # Shared secrets for https://github.com/devture/matrix-synapse-shared-secret-auth + # + # If set, double puppeting will be enabled automatically for local users + # instead of users having to find an access token and run `login-matrix` + # manually. + login_shared_secret_map: + example.com: foobar + + # The prefix for commands. Only required in non-management rooms. + command_prefix: '!discord' + # Messages sent upon joining a management room. + # Markdown is supported. The defaults are listed below. + management_room_text: + # Sent when joining a room. + welcome: "Hello, I'm a Discord bridge bot." + # Sent when joining a management room and the user is already logged in. + welcome_connected: "Use `help` for help." + # Sent when joining a management room and the user is not logged in. + welcome_unconnected: "Use `help` for help or `login` to log in." + # Optional extra text sent when joining a management room. + additional_help: "" + + # Settings for backfilling messages. + backfill: + # Limits for forward backfilling. + forward_limits: + # Initial backfill (when creating portal). 0 means backfill is disabled. + # A special unlimited value is not supported, you must set a limit. Initial backfill will + # fetch all messages first before backfilling anything, so high limits can take a lot of time. + initial: + dm: 0 + channel: 0 + thread: 0 + # Missed message backfill (on startup). + # 0 means backfill is disabled, -1 means fetch all messages since last bridged message. + # When using unlimited backfill (-1), messages are backfilled as they are fetched. + # With limits, all messages up to the limit are fetched first and backfilled afterwards. + missed: + dm: 0 + channel: 0 + thread: 0 + # Maximum members in a guild to enable backfilling. Set to -1 to disable limit. + # This can be used as a rough heuristic to disable backfilling in channels that are too active. + # Currently only applies to missed message backfill. + max_guild_members: -1 + + # End-to-bridge encryption support options. + # + # See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info. + encryption: + # Allow encryption, work in group chat rooms with e2ee enabled + allow: true + # Default to encryption, force-enable encryption in all portals the bridge creates + # This will cause the bridge bot to be in private chats for the encryption to work properly. + default: false + # Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data. + # Changing this option requires updating the appservice registration file. + appservice: false + # Whether to use MSC4190 instead of appservice login to create the bridge bot device. + # Requires the homeserver to support MSC4190 and the device masquerading parts of MSC3202. + # Only relevant when using end-to-bridge encryption, required when using encryption with next-gen auth (MSC3861). + # Changing this option requires updating the appservice registration file. + msc4190: false + # Require encryption, drop any unencrypted messages. + require: false + # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled. + # You must use a client that supports requesting keys from other users to use this feature. + allow_key_sharing: false + # Should users mentions be in the event wire content to enable the server to send push notifications? + plaintext_mentions: false + # Options for deleting megolm sessions from the bridge. + delete_keys: + # Beeper-specific: delete outbound sessions when hungryserv confirms + # that the user has uploaded the key to key backup. + delete_outbound_on_ack: false + # Don't store outbound sessions in the inbound table. + dont_store_outbound: false + # Ratchet megolm sessions forward after decrypting messages. + ratchet_on_decrypt: false + # Delete fully used keys (index >= max_messages) after decrypting messages. + delete_fully_used_on_decrypt: false + # Delete previous megolm sessions from same device when receiving a new one. + delete_prev_on_new_session: false + # Delete megolm sessions received from a device when the device is deleted. + delete_on_device_delete: false + # Periodically delete megolm sessions when 2x max_age has passed since receiving the session. + periodically_delete_expired: false + # Delete inbound megolm sessions that don't have the received_at field used for + # automatic ratcheting and expired session deletion. This is meant as a migration + # to delete old keys prior to the bridge update. + delete_outdated_inbound: false + # What level of device verification should be required from users? + # + # Valid levels: + # unverified - Send keys to all device in the room. + # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys. + # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes). + # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot. + # Note that creating user signatures from the bridge bot is not currently possible. + # verified - Require manual per-device verification + # (currently only possible by modifying the `trust` column in the `crypto_device` database table). + verification_levels: + # Minimum level for which the bridge should send keys to when bridging messages from WhatsApp to Matrix. + receive: unverified + # Minimum level that the bridge should accept for incoming Matrix messages. + send: unverified + # Minimum level that the bridge should require for accepting key requests. + share: cross-signed-tofu + # Options for Megolm room key rotation. These options allow you to + # configure the m.room.encryption event content. See: + # https://spec.matrix.org/v1.3/client-server-api/#mroomencryption for + # more information about that event. + rotation: + # Enable custom Megolm room key rotation settings. Note that these + # settings will only apply to rooms created after this option is + # set. + enable_custom: false + # The maximum number of milliseconds a session should be used + # before changing it. The Matrix spec recommends 604800000 (a week) + # as the default. + milliseconds: 604800000 + # The maximum number of messages that should be sent with a given a + # session before changing it. The Matrix spec recommends 100 as the + # default. + messages: 100 + + # Disable rotating keys when a user's devices change? + # You should not enable this option unless you understand all the implications. + disable_device_change_key_rotation: false + + # Settings for provisioning API + provisioning: + # Prefix for the provisioning API paths. + prefix: /_matrix/provision + # Shared secret for authentication. If set to "generate", a random secret will be generated, + # or if set to "disable", the provisioning API will be disabled. + shared_secret: generate + # Enable debug API at /debug with provisioning authentication. + debug_endpoints: false + + # Permissions for using the bridge. + # Permitted values: + # relay - Talk through the relaybot (if enabled), no access otherwise + # user - Access to use the bridge to chat with a Discord account. + # admin - User level and some additional administration tools + # Permitted keys: + # * - All Matrix users + # domain - All users on that homeserver + # mxid - Specific user + permissions: + "*": relay + "matrix.lotusguild.org": user + "@jared:matrix.lotusguild.org": admin + +# Logging config. See https://github.com/tulir/zeroconfig for details. +logging: + min_level: info + writers: + - type: stdout + format: pretty-colored + - type: file + format: json + filename: /var/log/mautrix-discord/mautrix-discord.log + max_size: 100 + max_backups: 10 + compress: true diff --git a/discord-bridge/install.sh b/discord-bridge/install.sh new file mode 100755 index 0000000..adcd89e --- /dev/null +++ b/discord-bridge/install.sh @@ -0,0 +1,103 @@ +#!/bin/bash +# One-time install of the mautrix-discord bridge. +# Run on the Proxmox node that hosts LXC 109 (PostgreSQL) and LXC 151 (Synapse): +# pct exec 151 -- cat /opt/matrix-config/discord-bridge/install.sh | bash +# Needs this repo's main branch already pulled to /opt/matrix-config on LXC 151 +# (the auto-deploy does that). Restarts Synapse once (~30-60s of downtime). +# Safe to re-run: existing database, user, config and registration are kept. +set -euo pipefail + +VERSION="v0.7.7" +SHA256="1f3b6953b4eae00d141ce706f6e97c1b5d0e50268a447bc605df2fa4f44c5d9d" +PG_CT=109 +SYNAPSE_CT=151 +SYNAPSE_IP="10.10.10.29" + +# Only used if the database role does not exist yet; never printed. +DB_PASSWORD="$(openssl rand -hex 24 /root/.mautrix-discord-role-existed +else + su postgres -c "psql -v ON_ERROR_STOP=1 -q" </dev/null +echo "ok" +PG + +ROLE_EXISTED=$(pct exec "$PG_CT" -- sh -c 'test -f /root/.mautrix-discord-role-existed && echo yes || echo no' /dev/null 2>&1 || useradd --system --home "$DIR" --shell /usr/sbin/nologin mautrix-discord +mkdir -p "$DIR" /var/log/mautrix-discord + +curl -fsSL -o "$DIR/mautrix-discord.new" "https://github.com/mautrix/discord/releases/download/$VERSION/mautrix-discord-amd64" +echo "$SHA256 $DIR/mautrix-discord.new" | sha256sum -c - +chmod 755 "$DIR/mautrix-discord.new" +mv "$DIR/mautrix-discord.new" "$DIR/mautrix-discord" + +if [ ! -f "$DIR/config.yaml" ]; then + if [ "$ROLE_EXISTED" = yes ]; then + echo "ERROR: DB role already existed but there is no config; set the password in $DIR/config.yaml by hand" >&2 + exit 1 + fi + sed "s/DB_PASSWORD/$PW/" "$SRC/discord-bridge/config.yaml" > "$DIR/config.yaml" +fi +if [ ! -f "$DIR/registration.yaml" ]; then + (cd "$DIR" && ./mautrix-discord -g -c config.yaml -r registration.yaml) +fi +chown -R mautrix-discord:mautrix-discord "$DIR" /var/log/mautrix-discord +chmod 600 "$DIR/config.yaml" +install -m 640 -o root -g matrix-synapse "$DIR/registration.yaml" /etc/matrix-synapse/discord-registration.yaml + +install -m 644 "$SRC/systemd/mautrix-discord.service" /etc/systemd/system/mautrix-discord.service +systemctl daemon-reload + +HS=/etc/matrix-synapse/homeserver.yaml +if ! grep -q discord-registration.yaml "$HS"; then + cp "$HS" "$HS.bak-$(date +%Y%m%d%H%M%S)-discord" + sed -i '/^ - \/etc\/matrix-synapse\/hookshot-registration.yaml/a \ - /etc/matrix-synapse/discord-registration.yaml' "$HS" +fi +grep -A3 '^app_service_config_files' "$HS" +echo "ok" +BR + +echo "== [3/3] Restart Synapse, start bridge ==" +pct exec "$SYNAPSE_CT" -- bash -s <<'RS' +set -euo pipefail +systemctl restart matrix-synapse +for i in $(seq 1 60); do + curl -fsS -o /dev/null http://127.0.0.1:8008/health && break + sleep 2 +done +curl -fsS http://127.0.0.1:8008/health && echo " (synapse healthy)" +systemctl enable --now mautrix-discord +sleep 5 +systemctl --no-pager --lines=15 status mautrix-discord +RS + +pct exec "$PG_CT" -- rm -f /root/.mautrix-discord-role-existed " diff --git a/systemd/mautrix-discord.service b/systemd/mautrix-discord.service new file mode 100644 index 0000000..3a0570b --- /dev/null +++ b/systemd/mautrix-discord.service @@ -0,0 +1,30 @@ +[Unit] +Description=mautrix-discord Matrix-Discord bridge +After=network-online.target matrix-synapse.service +Wants=network-online.target + +[Service] +Type=simple +User=mautrix-discord +Group=mautrix-discord +WorkingDirectory=/opt/mautrix-discord +ExecStart=/opt/mautrix-discord/mautrix-discord -c /opt/mautrix-discord/config.yaml -r /opt/mautrix-discord/registration.yaml +Restart=on-failure +RestartSec=10 +StandardOutput=journal +StandardError=journal +SyslogIdentifier=mautrix-discord + +# Resource limits +MemoryMax=512M +CPUQuota=80% + +# Hardening +NoNewPrivileges=yes +ProtectSystem=strict +ProtectHome=yes +PrivateTmp=yes +ReadWritePaths=/opt/mautrix-discord /var/log/mautrix-discord + +[Install] +WantedBy=multi-user.target -- 2.47.3