telegabber/config.yml.example
2026-07-28 23:14:32 -04:00

44 lines
1.7 KiB
Text

:telegram:
:loglevel: :warn
:content:
:path: '/var/www/telegabber/content' # webserver workdir
:link: 'http://tlgrm.localhost/content' # webserver public address
:upload: 'https:///xmppfiles.localhost' # xmpp http upload address
:user: 'www-data' # owner of content files
:quota: '256MB' # maximum storage size
:tdlib_verbosity: 1
:mam_threshold: 7 # in days
:tdlib:
:datadir: './sessions/'
:client:
:api_id: '17349'
:api_hash: '344583e45741c457fe1862106095a5eb'
:device_model: 'telegabber'
:application_version: '2.0'
:use_chat_info_database: false
:use_secret_chats: true
:catch_timeout: 60
:xmpp:
:loglevel: :warn
:jid: 'tlgrm.localhost'
:host: '127.0.0.1'
:port: 5347
:password: 'password'
:db: 'session.dat'
# Optional. OMEMO (XEP-0384) end-to-end encryption for personal-chat
# pseudo-JIDs - off by default. When present but :enabled is left out
# or false, telegabber behaves exactly as if this whole block didn't
# exist. Every OMEMO generation this build supports (omemo0/omemo1/
# omemo2) is always published/served/accepted at once - there's no
# version to pick here; which one is actually used for a given chat is
# negotiated automatically (omemo0 by default, upgrading once that
# chat's peer is seen using a newer one). See README.md for the
# account-level (:omemo) and per-chat opt-in triggers on top of this
# deploy-time master switch.
#:e2ee:
# :enabled: true
# :backend: 'omemo'
# :db: 'e2ee'
# :encryption_passphrase: 'change-me' # empty disables encryption-at-rest