2024-02-19 00:08:20 +01:00
= mautrix-signal
2024-08-17 12:05:11 +02:00
image::https://img.shields.io/badge/Version-0.0.8-informational?style=flat-square[Version: 0.0.8]
2024-02-19 00:08:20 +01:00
image::https://img.shields.io/badge/Version-application-informational?style=flat-square[Type: application]
2024-08-17 03:56:11 +02:00
image::https://img.shields.io/badge/AppVersion-0.7.0-informational?style=flat-square[AppVersion: 0.7.0]
2024-02-19 00:08:20 +01:00
== Maintainers
.Maintainers
|===
| Name | Email | Url
| WrenIX
|
| <https://wrenix.eu>
|===
= Alpha
WARNING
====
We stop working on this Helm-Chart.
There are still many breaking change like:
* https://github.com/stalwartlabs/mail-server/issues/211[storage.fts in toml configuration has two meanings]
We hope that stalward mail-server becomes more stable.
====
== Usage
Helm must be installed and setup to your kubernetes cluster to use the charts.
Refer to Helm's https://helm.sh/docs[documentation] to get started.
Once Helm has been set up correctly, fetch the charts as follows:
[source,bash]
----
helm pull oci://codeberg.org/wrenix/helm-charts/mautrix-signal
----
You can install a chart release using the following command:
[source,bash]
----
helm install mautrix-signal-release oci://codeberg.org/wrenix/helm-charts/mautrix-signal --values values.yaml
----
To uninstall a chart release use `helm`'s delete command:
[source,bash]
----
helm uninstall mautrix-signal-release
----
== Values
.Values
|===
| Key | Type | Default | Description
| affinity
| object
| `{}`
|
| autoscaling.enabled
| bool
| `false`
|
| autoscaling.maxReplicas
| int
| `100`
|
| autoscaling.minReplicas
| int
| `1`
|
| autoscaling.targetCPUUtilizationPercentage
| int
| `80`
|
| config.appservice.address
| string
| `"http://localhost:29328"`
| The address that the homeserver can use to connect to this appservice.
2024-08-17 12:05:11 +02:00
| config.appservice.as_token
| string
| `""`
|
2024-02-19 00:08:20 +01:00
| config.appservice.async_transactions
| bool
| `false`
| 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.
| config.appservice.bot.avatar
| string
| `"mxc://maunium.net/wPJgTQbZOtpBFmDNkiNEMDUp"`
|
| config.appservice.bot.displayname
| string
| `"Signal bridge bot"`
| Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty to leave display name/avatar as-is.
| config.appservice.bot.username
| string
| `"signalbot"`
| Username of the appservice bot.
2024-08-17 12:05:11 +02:00
| config.appservice.ephemeral_events
| bool
| `true`
| Whether or not to receive ephemeral events via appservice transactions. Requires MSC2409 support (i.e. Synapse 1.22+).
| config.appservice.hostname
| string
| `"0.0.0.0"`
| The hostname and port where this appservice should listen.
| config.appservice.hs_token
| string
| `""`
|
| config.appservice.id
| string
| `"signal"`
| The unique ID of this appservice.
| config.appservice.port
| int
| `29328`
|
| config.appservice.public_address
2024-02-19 00:08:20 +01:00
| string
| `nil`
2024-08-17 12:05:11 +02:00
|
| config.appservice.username_template
| string
| `"signal_{{.}}"`
| Localpart template of MXIDs for Signal users. {{.}} is replaced with the internal ID of the Signal user.
| config.backfill.enabled
| bool
| `false`
|
| config.backfill.max_catchup_messages
| string
| `nil`
|
| config.backfill.max_initial_messages
| string
| `nil`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.backfill.queue.batch_delay
2024-02-19 00:08:20 +01:00
| string
| `nil`
|
2024-08-17 12:05:11 +02:00
| config.backfill.queue.batch_size
| string
| `nil`
|
| config.backfill.queue.enabled
| string
| `nil`
|
| config.backfill.queue.max_batches
2024-02-19 00:08:20 +01:00
| int
2024-08-17 12:05:11 +02:00
| `10`
2024-02-19 00:08:20 +01:00
|
2024-08-17 12:05:11 +02:00
| config.backfill.queue.max_batches_override.a
2024-02-19 00:08:20 +01:00
| int
2024-08-17 12:05:11 +02:00
| `10`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.backfill.threads.max_initial_messages
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `nil`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.backfill.unread_hours_threshold
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `nil`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.bridge.bridge_matrix_leave
| string
| `nil`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.bridge.cleanup_on_logout.bad_credentials.private
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `nil`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.bridge.cleanup_on_logout.bad_credentials.relayed
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `nil`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.bridge.cleanup_on_logout.bad_credentials.shared_has_users
| string
| `nil`
2024-02-19 00:08:20 +01:00
|
2024-08-17 12:05:11 +02:00
| config.bridge.cleanup_on_logout.bad_credentials.shared_no_users
| string
| `nil`
|
| config.bridge.cleanup_on_logout.enabled
| string
| `nil`
|
| config.bridge.cleanup_on_logout.manual.private
| string
| `nil`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.bridge.cleanup_on_logout.manual.relayed
| string
| `nil`
|
| config.bridge.cleanup_on_logout.manual.shared_has_users
| string
| `nil`
|
| config.bridge.cleanup_on_logout.manual.shared_no_users
| string
| `nil`
|
| config.bridge.command_prefix
| string
| `"!signal"`
| The prefix for commands. Only required in non-management rooms.
| config.bridge.mute_only_on_create
| string
| `nil`
|
| config.bridge.permissions."@admin:example.com"
| string
| `"admin"`
|
| config.bridge.permissions."example.com"
| string
| `"user"`
|
| config.bridge.permissions.*
| string
| `"relay"`
|
| config.bridge.personal_filtering_spaces
| bool
| `false`
| Should the bridge create a space for each logged-in user and add bridged rooms to it? Users who logged in before turning this on should run `!signal sync-space` to create and fill the space for the first time.
| config.bridge.private_chat_portal_meta
| string
| `"default"`
| 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.
| config.bridge.relay.admin_only
2024-02-19 00:08:20 +01:00
| bool
| `true`
2024-08-17 12:05:11 +02:00
| Should only admins be allowed to set themselves as relay users?
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.bridge.relay.default_relays
| string
| `nil`
|
| config.bridge.relay.displayname_format
| string
| `""`
|
| config.bridge.relay.enabled
2024-02-19 00:08:20 +01:00
| bool
| `false`
2024-08-17 12:05:11 +02:00
| Whether relay mode should be allowed. If allowed, `!wa set-relay` can be used to turn any authenticated user into a relaybot for that chat.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.bridge.relay.message_formats
| object
| `{"m.audio":"<b>{{ .Sender.Displayname }}</b> sent an audio file","m.emote":"* <b>{{ .Sender.Displayname }}</b> {{ .Message }}","m.file":"<b>{{ .Sender.Displayname }}</b> sent a file","m.image":"<b>{{ .Sender.Displayname }}</b> sent an image","m.location":"<b>{{ .Sender.Displayname }}</b> sent a location","m.notice":"<b>{{ .Sender.Displayname }}</b>: {{ .Message }}","m.text":"<b>{{ .Sender.Displayname }}</b>: {{ .Message }}","m.video":"<b>{{ .Sender.Displayname }}</b> sent a video"}`
| The formats to use when sending messages to Signal via the relaybot.
| config.bridge.tag_only_on_create
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `nil`
|
| config.database.max_conn_idle_time
| string
| `nil`
| Maximum connection idle time and lifetime before they're closed. Disabled if null. Parsed with https://pkg.go.dev/time#ParseDuration
| config.database.max_conn_lifetime
| string
| `nil`
|
| config.database.max_idle_conns
| int
| `2`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.database.max_open_conns
| int
| `20`
| Maximum number of connections. Mostly relevant for Postgres.
| config.database.type
| string
| `"postgres"`
| The database type. "sqlite3-fk-wal" and "postgres" are supported.
| config.database.uri
| string
| `"postgres://user:password@host/database?sslmode=disable"`
| The database URI. SQLite: A raw file path is supported, but `file:<path>?_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
| config.direct_media.allow_proxy
2024-02-19 00:08:20 +01:00
| bool
| `false`
2024-08-17 12:05:11 +02:00
|
| config.direct_media.enabled
| bool
| `false`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.direct_media.media_id_prefix
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `""`
|
| config.direct_media.server_key
| string
| `""`
|
| config.direct_media.server_name
| string
| `""`
|
| config.direct_media.well_known_response
| string
| `""`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.double_puppet.allow_discovery
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Allow using double puppeting from any server with a valid client .well-known file.
2024-08-17 12:05:11 +02:00
| config.double_puppet.secrets
| object
| `{"example.com":"foobar"}`
| 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.
| config.double_puppet.servers
2024-02-19 00:08:20 +01:00
| object
| `{"example.com":"https://example.com"}`
| Servers to always allow double puppeting from
2024-08-17 12:05:11 +02:00
| config.encryption.allow
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Allow encryption, work in group chat rooms with e2ee enabled
2024-08-17 12:05:11 +02:00
| config.encryption.allow_key_sharing
2024-02-19 00:08:20 +01:00
| bool
| `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.
2024-08-17 12:05:11 +02:00
| config.encryption.appservice
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data.
2024-08-17 12:05:11 +02:00
| config.encryption.default
2024-02-19 00:08:20 +01:00
| bool
| `false`
| 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.
2024-08-17 12:05:11 +02:00
| config.encryption.delete_keys
2024-02-19 00:08:20 +01:00
| object
| `{"delete_fully_used_on_decrypt":false,"delete_on_device_delete":false,"delete_outbound_on_ack":false,"delete_outdated_inbound":false,"delete_prev_on_new_session":false,"dont_store_outbound":false,"periodically_delete_expired":false,"ratchet_on_decrypt":false}`
| Options for deleting megolm sessions from the bridge.
2024-08-17 12:05:11 +02:00
| config.encryption.delete_keys.delete_fully_used_on_decrypt
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Delete fully used keys (index >= max_messages) after decrypting messages.
2024-08-17 12:05:11 +02:00
| config.encryption.delete_keys.delete_on_device_delete
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Delete megolm sessions received from a device when the device is deleted.
2024-08-17 12:05:11 +02:00
| config.encryption.delete_keys.delete_outbound_on_ack
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Beeper-specific: delete outbound sessions when hungryserv confirms that the user has uploaded the key to key backup.
2024-08-17 12:05:11 +02:00
| config.encryption.delete_keys.delete_outdated_inbound
2024-02-19 00:08:20 +01:00
| bool
| `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.
2024-08-17 12:05:11 +02:00
| config.encryption.delete_keys.delete_prev_on_new_session
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Delete previous megolm sessions from same device when receiving a new one.
2024-08-17 12:05:11 +02:00
| config.encryption.delete_keys.dont_store_outbound
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Don't store outbound sessions in the inbound table.
2024-08-17 12:05:11 +02:00
| config.encryption.delete_keys.periodically_delete_expired
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Periodically delete megolm sessions when 2x max_age has passed since receiving the session.
2024-08-17 12:05:11 +02:00
| config.encryption.delete_keys.ratchet_on_decrypt
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Ratchet megolm sessions forward after decrypting messages.
2024-08-17 12:05:11 +02:00
| config.encryption.pickle_key
| string
| `nil`
|
| config.encryption.plaintext_mentions
| string
| `nil`
|
| config.encryption.require
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Require encryption, drop any unencrypted messages.
2024-08-17 12:05:11 +02:00
| config.encryption.rotation.disable_device_change_key_rotation
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Disable rotating keys when a user's devices change? You should not enable this option unless you understand all the implications.
2024-08-17 12:05:11 +02:00
| config.encryption.rotation.enable_custom
2024-02-19 00:08:20 +01:00
| bool
| `false`
| Enable custom Megolm room key rotation settings. Note that these settings will only apply to rooms created after this option is set.
2024-08-17 12:05:11 +02:00
| config.encryption.rotation.messages
2024-02-19 00:08:20 +01:00
| int
| `100`
| 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.
2024-08-17 12:05:11 +02:00
| config.encryption.rotation.milliseconds
2024-02-19 00:08:20 +01:00
| int
| `604800000`
| The maximum number of milliseconds a session should be used before changing it. The Matrix spec recommends 604800000 (a week) as the default.
2024-08-17 12:05:11 +02:00
| config.encryption.verification_levels.receive
2024-02-19 00:08:20 +01:00
| string
| `"unverified"`
| Minimum level for which the bridge should send keys to when bridging messages from Signal to Matrix.
2024-08-17 12:05:11 +02:00
| config.encryption.verification_levels.send
2024-02-19 00:08:20 +01:00
| string
| `"unverified"`
| Minimum level that the bridge should accept for incoming Matrix messages.
2024-08-17 12:05:11 +02:00
| config.encryption.verification_levels.share
2024-02-19 00:08:20 +01:00
| string
| `"cross-signed-tofu"`
| Minimum level that the bridge should require for accepting key requests.
2024-08-17 12:05:11 +02:00
| config.homeserver.address
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"https://matrix.example.com"`
| The address that this appservice can use to connect to the homeserver.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.homeserver.async_media
| bool
| `false`
| Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.homeserver.domain
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"example.com"`
| The domain of the homeserver (also known as server_name, used for MXIDs, etc).
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.homeserver.message_send_checkpoint_endpoint
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `nil`
| Endpoint for reporting per-message status.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.homeserver.ping_interval_seconds
| int
| `0`
| How often should the websocket be pinged? Pinging will be disabled if this is zero.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.homeserver.public_address
| string
| `nil`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.homeserver.software
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"standard"`
| What software is the homeserver running? Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.homeserver.status_endpoint
2024-02-19 00:08:20 +01:00
| string
| `nil`
2024-08-17 12:05:11 +02:00
| The URL to push real-time bridge status to. If set, the bridge will make POST requests to this URL whenever a user's Signal connection state changes. The bridge will use the appservice as_token to authorize requests.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.homeserver.websocket
2024-02-19 00:08:20 +01:00
| bool
| `false`
2024-08-17 12:05:11 +02:00
| 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).
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.homeserver.websocket_proxy
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `""`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.logging.min_level
| string
| `"warn"`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.logging.writers[0].format
| string
| `"json"`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.logging.writers[0].type
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"stdout"`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.management_room_text.additional_help
| string
| `""`
| Optional extra text sent when joining a management room.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.management_room_text.welcome
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"Hello, I'm a Signal bridge bot."`
| Sent when joining a room.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.management_room_text.welcome_connected
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"Use `help` for help."`
| Sent when joining a management room and the user is already logged in.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.management_room_text.welcome_unconnected
| string
| `"Use `help` for help or `login` to log in."`
| Sent when joining a management room and the user is not logged in.
| config.matrix.delivery_receipts
2024-02-19 00:08:20 +01:00
| bool
| `false`
2024-08-17 12:05:11 +02:00
| Should the bridge send a read receipt from the bridge bot when a message has been sent to Signal?
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.matrix.federate_rooms
2024-02-19 00:08:20 +01:00
| bool
| `true`
2024-08-17 12:05:11 +02:00
| Whether or not created rooms should have federation enabled. If false, created portal rooms will never be federated.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.matrix.message_error_notices
2024-02-19 00:08:20 +01:00
| bool
2024-08-17 12:05:11 +02:00
| `true`
| Whether the bridge should send error notices via m.notice events when a message fails to bridge.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.matrix.message_status_events
2024-02-19 00:08:20 +01:00
| bool
| `false`
2024-08-17 12:05:11 +02:00
| Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.matrix.sync_direct_chat_list
2024-02-19 00:08:20 +01:00
| bool
| `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.
2024-08-17 12:05:11 +02:00
| config.metrics.enabled
2024-02-19 00:08:20 +01:00
| bool
2024-08-17 12:05:11 +02:00
| `true`
| Enable prometheus metrics?
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.metrics.listen
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"0.0.0.0:8000"`
| IP and port where the metrics listener should be. The path is always /metrics
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.provisioning.debug_endpoints
2024-02-19 00:08:20 +01:00
| bool
| `false`
2024-08-17 12:05:11 +02:00
| Enable debug API at /debug with provisioning authentication.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.provisioning.prefix
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"/_matrix/provision"`
| Prefix for the provisioning API paths.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.provisioning.shared_secret
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"generate"`
| 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.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.public_media.enabled
| bool
| `false`
|
| config.public_media.expiry
2024-02-19 00:08:20 +01:00
| int
| `0`
2024-08-17 12:05:11 +02:00
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.public_media.hash_length
| int
| `0`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.public_media.signing_key
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `""`
|
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.signal.device_name
| string
| `"mautrix-signal"`
| Default device name that shows up in the Signal app.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.signal.displayname_template
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"{{or .ProfileName .PhoneNumber \"Unknown user\"}}"`
| Displayname template for Signal users. This is also used as the room name in DMs if private_chat_portal_meta is enabled. {{.ProfileName}} - The Signal profile name set by the user. {{.ContactName}} - The name for the user from your phone's contact list. This is not safe on multi-user instances. {{.PhoneNumber}} - The phone number of the user. {{.UUID}} - The UUID of the Signal user. {{.AboutEmoji}} - The emoji set by the user in their profile.
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.signal.location_format
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"https://www.openstreetmap.org/?mlat=%[1]s&mlon=%[2]s"`
2024-02-19 00:08:20 +01:00
|
2024-08-17 12:05:11 +02:00
| config.signal.note_to_self_avatar
2024-02-19 00:08:20 +01:00
| string
2024-08-17 12:05:11 +02:00
| `"mxc://maunium.net/REBIVrqjZwmaWpssCZpBlmlL"`
2024-02-19 00:08:20 +01:00
|
2024-08-17 12:05:11 +02:00
| config.signal.number_in_topic
2024-02-19 00:08:20 +01:00
| bool
| `true`
2024-08-17 12:05:11 +02:00
| Should the Signal user's phone number be included in the room topic in private chat portal rooms?
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.signal.sync_contacts_on_startup
| bool
| `true`
| Should the bridge request the user's contact list from the phone on startup?
2024-02-19 00:08:20 +01:00
2024-08-17 12:05:11 +02:00
| config.signal.use_contact_avatars
| bool
| `false`
| Should avatars from the user's contact list be used? This is not safe on multi-user instances.
| config.signal.use_outdated_profiles
| bool
| `false`
| Should the bridge sync ghost user info even if profile fetching fails? This is not safe on multi-user instances.
2024-02-19 00:08:20 +01:00
| fullnameOverride
| string
| `""`
|
| global.image.pullPolicy
| string
| `nil`
| if set it will overwrite all pullPolicy
| global.image.registry
| string
| `nil`
| if set it will overwrite all registry entries
| image.pullPolicy
| string
| `"IfNotPresent"`
|
| image.registry
| string
| `"dock.mau.dev"`
|
| image.repository
| string
| `"mautrix/signal"`
|
| image.tag
| string
| `""`
|
| imagePullSecrets
| list
| `[]`
|
| ingress.annotations
| object
| `{}`
|
| ingress.className
| string
| `""`
|
| ingress.enabled
| bool
| `false`
|
| ingress.hosts[0].host
| string
| `"chart-example.local"`
|
| ingress.hosts[0].paths[0].path
| string
| `"/"`
|
| ingress.hosts[0].paths[0].pathType
| string
| `"ImplementationSpecific"`
|
| ingress.tls
| list
| `[]`
|
| livenessProbe.httpGet.path
| string
| `"/_matrix/mau/live"`
|
| livenessProbe.httpGet.port
| string
| `"http"`
|
| nameOverride
| string
| `""`
|
| nodeSelector
| object
| `{}`
|
| persistence.accessMode
| string
| `"ReadWriteOnce"`
| accessMode
| persistence.annotations
| object
| `{}`
|
| persistence.enabled
| bool
| `true`
| Enable persistence using Persistent Volume Claims ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
| persistence.existingClaim
| string
| `nil`
| A manually managed Persistent Volume and Claim Requires persistence.enabled: true If defined, PVC must be created manually before volume will be bound
| persistence.hostPath
| string
| `nil`
| Do not create an PVC, direct use hostPath in Pod
| persistence.size
| string
| `"10Gi"`
| size
| persistence.storageClass
| string
| `nil`
| Persistent Volume Storage Class If defined, storageClassName: <storageClass> If set to "-", storageClassName: "", which disables dynamic provisioning If undefined (the default) or set to null, no storageClassName spec is set, choosing the default provisioner. (gp2 on AWS, standard on GKE, AWS & OpenStack)
| podAnnotations
| object
| `{}`
|
| podLabels
| object
| `{}`
|
| podSecurityContext
| object
| `{}`
|
| prometheus.servicemonitor.enabled
| bool
| `false`
|
| prometheus.servicemonitor.labels
| object
| `{}`
|
| readinessProbe.httpGet.path
| string
| `"/_matrix/mau/ready"`
|
| readinessProbe.httpGet.port
| string
| `"http"`
|
| registration."de.sorunome.msc2409.push_ephemeral"
| bool
| `true`
|
| registration.namespaces.users[0].exclusive
| bool
| `true`
|
| registration.namespaces.users[0].regex
| string
| `"^@signalbot:example.org$"`
|
| registration.namespaces.users[1].exclusive
| bool
| `true`
|
| registration.namespaces.users[1].regex
| string
| `"^@signal_.*:example.org$"`
|
| registration.push_ephemeral
| bool
| `true`
|
| registration.rate_limited
| bool
| `false`
|
| replicaCount
| int
| `1`
|
| resources
| object
| `{}`
|
| securityContext
| object
| `{}`
|
| service.type
| string
| `"ClusterIP"`
|
| serviceAccount.annotations
| object
| `{}`
|
| serviceAccount.automount
| bool
| `false`
|
| serviceAccount.create
| bool
| `false`
|
| serviceAccount.name
| string
| `""`
|
| tolerations
| list
| `[]`
|
| volumeMounts
| list
| `[]`
|
| volumes
| list
| `[]`
|
|===
Autogenerated from chart metadata using https://github.com/norwoodj/helm-docs[helm-docs]