server.yml 3.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. # ntfy server config file
  2. # Public facing base URL of the service (e.g. https://ntfy.sh or https://ntfy.example.com)
  3. # This setting is currently only used by the e-mail sending feature (outgoing mail only).
  4. #
  5. # base-url:
  6. # Listen address for the HTTP & HTTPS web server. If "listen-https" is set, you must also
  7. # set "key-file" and "cert-file". Format: <hostname>:<port>
  8. #
  9. # listen-http: ":80"
  10. # listen-https:
  11. # Path to the private key & cert file for the HTTPS web server. Not used if "listen-https" is not set.
  12. #
  13. # key-file:
  14. # cert-file:
  15. # If set, also publish messages to a Firebase Cloud Messaging (FCM) topic for your app.
  16. # This is optional and only required to save battery when using the Android app.
  17. #
  18. # firebase-key-file: <filename>
  19. # If set, messages are cached in a local SQLite database instead of only in-memory. This
  20. # allows for service restarts without losing messages in support of the since= parameter.
  21. #
  22. # To disable the cache entirely (on-disk/in-memory), set "cache-duration" to 0.
  23. #
  24. # Note: If you are running ntfy with systemd, make sure this cache file is owned by the
  25. # ntfy user and group by running: chown ntfy.ntfy <filename>.
  26. #
  27. # cache-file: <filename>
  28. # Duration for which messages will be buffered before they are deleted.
  29. # This is required to support the "since=..." and "poll=1" parameter.
  30. #
  31. # You can disable the cache entirely by setting this to 0.
  32. #
  33. # cache-duration: 12h
  34. # If set, the X-Forwarded-For header is used to determine the visitor IP address
  35. # instead of the remote address of the connection.
  36. #
  37. # WARNING: If you are behind a proxy, you must set this, otherwise all visitors are rate limited
  38. # as if they are one.
  39. #
  40. # behind-proxy: false
  41. # If enabled, allow outgoing e-mail notifications via the 'X-Email' header. If this header is set,
  42. # messages will additionally be sent out as e-mail using an external SMTP server. As of today, only
  43. # SMTP servers with plain text auth and STARTLS are supported. Please also refer to the rate limiting settings
  44. # below (visitor-email-limit-burst & visitor-email-limit-burst).
  45. #
  46. # - smtp-sender-addr is the hostname:port of the SMTP server
  47. # - smtp-sender-user/smtp-sender-pass are the username and password of the SMTP user
  48. # - smtp-sender-from is the e-mail address of the sender
  49. #
  50. # smtp-sender-addr:
  51. # smtp-sender-user:
  52. # smtp-sender-pass:
  53. # smtp-sender-from:
  54. # XXXXXXXXXXXXXXXXXXXXxx
  55. # smtp-server-listen:
  56. # smtp-server-domain:
  57. # smtp-server-addr-prefix:
  58. # Interval in which keepalive messages are sent to the client. This is to prevent
  59. # intermediaries closing the connection for inactivity.
  60. #
  61. # Note that the Android app has a hardcoded timeout at 77s, so it should be less than that.
  62. #
  63. # keepalive-interval: 30s
  64. # Interval in which the manager prunes old messages, deletes topics
  65. # and prints the stats.
  66. #
  67. # manager-interval: 1m
  68. # Rate limiting: Total number of topics before the server rejects new topics.
  69. #
  70. # global-topic-limit: 5000
  71. # Rate limiting: Number of subscriptions per visitor (IP address)
  72. #
  73. # visitor-subscription-limit: 30
  74. # Rate limiting: Allowed GET/PUT/POST requests per second, per visitor:
  75. # - visitor-request-limit-burst is the initial bucket of requests each visitor has
  76. # - visitor-request-limit-replenish is the rate at which the bucket is refilled
  77. #
  78. # visitor-request-limit-burst: 60
  79. # visitor-request-limit-replenish: 10s
  80. # Rate limiting: Allowed emails per visitor:
  81. # - visitor-email-limit-burst is the initial bucket of emails each visitor has
  82. # - visitor-email-limit-replenish is the rate at which the bucket is refilled
  83. #
  84. # visitor-email-limit-burst: 16
  85. # visitor-email-limit-replenish: 1h