example-config.yaml 9.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217
  1. # Homeserver details
  2. homeserver:
  3. # The address that this appservice can use to connect to the homeserver.
  4. address: https://example.com
  5. # The domain of the homeserver (for MXIDs, etc).
  6. domain: example.com
  7. # Whether or not to verify the SSL certificate of the homeserver.
  8. # Only applies if address starts with https://
  9. verify_ssl: true
  10. asmux: false
  11. # Application service host/registration related details
  12. # Changing these values requires regeneration of the registration.
  13. appservice:
  14. # The address that the homeserver can use to connect to this appservice.
  15. address: http://localhost:29330
  16. # When using https:// the TLS certificate and key files for the address.
  17. tls_cert: false
  18. tls_key: false
  19. # The hostname and port where this appservice should listen.
  20. hostname: 0.0.0.0
  21. port: 29330
  22. # The maximum body size of appservice API requests (from the homeserver) in mebibytes
  23. # Usually 1 is enough, but on high-traffic bridges you might need to increase this to avoid 413s
  24. max_body_size: 1
  25. # The full URI to the database. Only Postgres is currently supported.
  26. database: postgres://username:password@hostname/db
  27. # The unique ID of this appservice.
  28. id: instagram
  29. # Username of the appservice bot.
  30. bot_username: instagrambot
  31. # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
  32. # to leave display name/avatar as-is.
  33. bot_displayname: Instagram bridge bot
  34. bot_avatar: mxc://maunium.net/JxjlbZUlCPULEeHZSwleUXQv
  35. # Community ID for bridged users (changes registration file) and rooms.
  36. # Must be created manually.
  37. #
  38. # Example: "+instagram:example.com". Set to false to disable.
  39. community_id: false
  40. # Whether or not to receive ephemeral events via appservice transactions.
  41. # Requires MSC2409 support (i.e. Synapse 1.22+).
  42. # You should disable bridge -> sync_with_custom_puppets when this is enabled.
  43. ephemeral_events: false
  44. # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
  45. as_token: "This value is generated when generating the registration"
  46. hs_token: "This value is generated when generating the registration"
  47. # Prometheus telemetry config. Requires prometheus-client to be installed.
  48. metrics:
  49. enabled: false
  50. listen_port: 8000
  51. instagram:
  52. # Seed for generating devices. This is secret because the seed is used to generate
  53. # device IDs, which can apparently be used to bypass two-factor authentication after
  54. # logging out, because Instagram is insecure.
  55. device_seed: generate
  56. # Bridge config
  57. bridge:
  58. # Localpart template of MXIDs for Instagram users.
  59. # {userid} is replaced with the user ID of the Instagram user.
  60. username_template: "instagram_{userid}"
  61. # Displayname template for Instagram users.
  62. # {displayname} is replaced with the display name of the Instagram user.
  63. # {username} is replaced with the username of the Instagram user.
  64. displayname_template: "{username} (Instagram)"
  65. # Maximum length of displayname
  66. displayname_max_length: 100
  67. # Maximum number of seconds since the last activity in a chat to automatically create portals.
  68. portal_create_max_age: 86400
  69. # Whether or not to use /sync to get read receipts and typing notifications
  70. # when double puppeting is enabled
  71. sync_with_custom_puppets: true
  72. # Whether or not to update the m.direct account data event when double puppeting is enabled.
  73. # Note that updating the m.direct event is not atomic (except with mautrix-asmux)
  74. # and is therefore prone to race conditions.
  75. sync_direct_chat_list: false
  76. # Allow using double puppeting from any server with a valid client .well-known file.
  77. double_puppet_allow_discovery: false
  78. # Servers to allow double puppeting from, even if double_puppet_allow_discovery is false.
  79. double_puppet_server_map:
  80. example.com: https://example.com
  81. # Shared secret for https://github.com/devture/matrix-synapse-shared-secret-auth
  82. #
  83. # If set, custom puppets will be enabled automatically for local users
  84. # instead of users having to find an access token and run `login-matrix`
  85. # manually.
  86. # If using this for other servers than the bridge's server,
  87. # you must also set the URL in the double_puppet_server_map.
  88. login_shared_secret_map:
  89. example.com: foo
  90. # Whether or not created rooms should have federation enabled.
  91. # If false, created portal rooms will never be federated.
  92. federate_rooms: true
  93. # Settings for backfilling messages from Instagram.
  94. backfill:
  95. # Whether or not the Instagram users of logged in Matrix users should be
  96. # invited to private chats when backfilling history from Instagram. This is
  97. # usually needed to prevent rate limits and to allow timestamp massaging.
  98. invite_own_puppet: true
  99. # Maximum number of messages to backfill initially.
  100. # Set to 0 to disable backfilling when creating portal.
  101. initial_limit: 0
  102. # Maximum number of messages to backfill if messages were missed while
  103. # the bridge was disconnected.
  104. # Set to 0 to disable backfilling missed messages.
  105. missed_limit: 1000
  106. # If using double puppeting, should notifications be disabled
  107. # while the initial backfill is in progress?
  108. disable_notifications: false
  109. # End-to-bridge encryption support options. You must install the e2be optional dependency for
  110. # this to work. See https://github.com/tulir/mautrix-telegram/wiki/End‐to‐bridge-encryption
  111. encryption:
  112. # Allow encryption, work in group chat rooms with e2ee enabled
  113. allow: false
  114. # Default to encryption, force-enable encryption in all portals the bridge creates
  115. # This will cause the bridge bot to be in private chats for the encryption to work properly.
  116. default: false
  117. # Options for automatic key sharing.
  118. key_sharing:
  119. # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
  120. # You must use a client that supports requesting keys from other users to use this feature.
  121. allow: false
  122. # Require the requesting device to have a valid cross-signing signature?
  123. # This doesn't require that the bridge has verified the device, only that the user has verified it.
  124. # Not yet implemented.
  125. require_cross_signing: false
  126. # Require devices to be verified by the bridge?
  127. # Verification by the bridge is not yet implemented.
  128. require_verification: true
  129. # Whether or not to explicitly set the avatar and room name for private
  130. # chat portal rooms. This will be implicitly enabled if encryption.default is true.
  131. private_chat_portal_meta: false
  132. # Whether or not the bridge should send a read receipt from the bridge bot when a message has
  133. # been sent to Instagram.
  134. delivery_receipts: false
  135. # Whether or not delivery errors should be reported as messages in the Matrix room.
  136. delivery_error_reports: false
  137. # Set this to true to tell the bridge to re-send m.bridge events to all rooms on the next run.
  138. # This field will automatically be changed back to false after it,
  139. # except if the config file is not writable.
  140. resend_bridge_info: false
  141. # Whether or not unimportant bridge notices should be sent to the user.
  142. # (e.g. connected, disconnected but will retry)
  143. unimportant_bridge_notices: true
  144. # Provisioning API part of the web server for automated portal creation and fetching information.
  145. # Used by things like mautrix-manager (https://github.com/tulir/mautrix-manager).
  146. provisioning:
  147. # Whether or not the provisioning API should be enabled.
  148. enabled: true
  149. # The prefix to use in the provisioning API endpoints.
  150. prefix: /_matrix/provision/v1
  151. # The shared secret to authorize users of the API.
  152. # Set to "generate" to generate and save a new token.
  153. shared_secret: generate
  154. # The prefix for commands. Only required in non-management rooms.
  155. command_prefix: "!ig"
  156. # Permissions for using the bridge.
  157. # Permitted values:
  158. # user - Use the bridge with puppeting.
  159. # admin - Use and administrate the bridge.
  160. # Permitted keys:
  161. # * - All Matrix users
  162. # domain - All users on that homeserver
  163. # mxid - Specific user
  164. permissions:
  165. "example.com": "user"
  166. "@admin:example.com": "admin"
  167. # Python logging configuration.
  168. #
  169. # See section 16.7.2 of the Python documentation for more info:
  170. # https://docs.python.org/3.6/library/logging.config.html#configuration-dictionary-schema
  171. logging:
  172. version: 1
  173. formatters:
  174. colored:
  175. (): mautrix_instagram.util.ColorFormatter
  176. format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s"
  177. normal:
  178. format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s"
  179. handlers:
  180. file:
  181. class: logging.handlers.RotatingFileHandler
  182. formatter: normal
  183. filename: ./mautrix-instagram.log
  184. maxBytes: 10485760
  185. backupCount: 10
  186. console:
  187. class: logging.StreamHandler
  188. formatter: colored
  189. loggers:
  190. mau:
  191. level: DEBUG
  192. mauigpapi:
  193. level: DEBUG
  194. aiohttp:
  195. level: INFO
  196. paho.mqtt:
  197. level: INFO
  198. root:
  199. level: DEBUG
  200. handlers: [file, console]