sample.config.yaml

bridge:
  # Port to host the bridge on which your homeserver will connect to
  port: 6000
  # Address for the bridge to bind to; if running as a Docker container, you
  # probably want 0.0.0.0 here
  bindAddress: localhost
  # Name of your homeserver
  domain: matrix.myhomeserver.com
  # URL where the bridge can connect to your homeserver
  homeserverUrl: http://localhost:8008

provisioning:
  # Which users are allowed to issue commands to @_twitterpuppet_bot
  whitelist:
    - "@username:matrix\\.myhomeserver\\.com"
  # A blacklist can be used instead:
  # blacklist:
  #   - "@username:matrix\\.myhomeserver\\.com"

  # Shared secret for the provisioning API for use by integration managers.
  # If this is not set, the provisioning API will not be enabled.
  #sharedSecret: random string
  # Path prefix for the provisioning API. /v1 will be appended to the prefix automatically.
  apiPrefix: /_matrix/provision

twitter:
  # You will need to set up a Twitter application with all permissions and add
  # its credentials and environment here
  # Set up your app here: https://developer.twitter.com/en/apps
  consumerKey: ""
  consumerSecret: ""
  accessToken: ""
  accessTokenSecret: ""
  environment: ""
  # The twitter app ID (https://developer.twitter.com/en/apps/<app id>) used for message deduplication
  appId: 0
  server:
    # The bridge uses Twitter's webhooks API. For this to work, you need a
    # publically accessible URL with SSL on port 443; Twitter will refuse to
    # send webhooks to any other port. You will likely want to configure a
    # reverse proxy such as Nginx to handle this
    url: https://twitter-bridge.myhomeserver.com
    # The path that the nginx proxy will have to redirect
    path: /_matrix/twitter/webhook