lsposed/rss-to-telegram repository overview

rss订阅推送

# Please read https://github.com/Rongronggg9/RSS-to-Telegram-Bot/blob/master/docs/deployment-guide.md for more details.
version: '3.6'

services:
  main:
    image: lsposed/rss-to-telegram:dev 
    container_name: telegra_rsstt  # need to be unique
    volumes:
      - ./config:/app/config
    environment:
      - TOKEN=  # get it from @BotFather
      - MANAGER=  # get it from @userinfobot

# ↓------ To disable sending via Telegraph, comment out this area ------↓ #
# Get Telegraph API access tokens: https://api.telegra.ph/createAccount?short_name=RSStT&author_name=Generated%20by%20RSStT&author_url=https%3A%2F%2Fgithub.com%2FRongronggg9%2FRSS-to-Telegram-Bot
# Refresh the page every time you get a new token.
# If you have a lot of subscriptions, make sure to get at least 5 tokens.
#                            ↓ Replace with your access tokens ↓
      - TELEGRAPH_TOKEN=
        b377b0
        220216
        dac056
        3ac268
        20d546
# ↑------ To disable sending via Telegraph, comment out this area ------↑ #

# Please read https://github.com/Rongronggg9/RSS-to-Telegram-Bot/blob/master/docs/advanced-settings.md for more details.
# ↓------ Advanced settings ------↓ #
      #- MULTIUSER=0  # default: 1
      #- CRON_SECOND=30  # 0-59, default: 0
      #- DATABASE_URL=postgres://username:password@host:port/db_name  # default: sqlite://path/to/config/db.sqlite3
      #- API_ID=1025907  # get it from https://core.telegram.org/api/obtaining_api_id
      #- API_HASH=452b0359b988148995f22ff0f4229750  # get it from https://core.telegram.org/api/obtaining_api_id
      #- IMG_RELAY_SERVER=https://wsrv.nl/?url=  # default: https://rsstt-img-relay.rongrong.workers.dev/
      #- IMAGES_WESERV_NL=https://t0.nl/  # default: https://wsrv.nl/
      #- USER_AGENT=Mozilla/5.0 (Android 12; Mobile; rv:68.0) Gecko/68.0 Firefox/96.0  # default: RSStT/2.2 RSS Reader
      #- IPV6_PRIOR=1  # default: 0
      #- T_PROXY=socks5://172.17.0.1:1080  # Proxy used to connect to the Telegram API
      #- R_PROXY=socks5://172.17.0.1:1080  # Proxy used to fetch feeds
      #- PROXY_BYPASS_PRIVATE=1  # default: 0
      #- PROXY_BYPASS_DOMAINS=example.com;example.net
      #- HTTP_TIMEOUT=30  # default: 12
      #- HTTP_CONCURRENCY=0  # default: 1024
      #- HTTP_CONCURRENCY_PER_HOST=0  # default: 16
      #- TABLE_TO_IMAGE=1  # default: 0
      #- TRAFFIC_SAVING=1  # default: 0
      #- LAZY_MEDIA_VALIDATION=1  # default: 0
      #- MANAGER_PRIVILEGED=1  # default: 0
      #- NO_UVLOOP=1  # default: 0
      #- MULTIPROCESSING=1  # default: 0
      #- DEBUG=1  # debug logging, default: 0
# ↑------ Advanced settings ------↑ #
    networks:
      - mynetworks
    logging:
      driver: "json-file"
      options:
        max-size: "50m"
    restart: always
    # mem_limit: 100m
    # cpus: 0.2
    
networks:
  mynetworks:
    external: true

⁠Advanced Settings

⁠Env variables

⁠Required

⁠API settings

⁠Network settings

⁠Misc settings

⁠Manager options

————

⁠高级设置

⁠环境变量

⁠必需的

⁠API设置

⁠网络设置

⁠杂项设置

⁠管理员选项

阅数量限制 ^{13⁠ 12⁠} | 150 | -1 (无限制) | | sub_limit_reached_message | 与达到限制的警告附加的额外消息 | https://t.me/RSStT_Channel/58 | |

⁠Footnotes

1. Refresh the page every time you get a new token. If you have a lot of subscriptions, make sure to get at least 5 tokens. ↩⁠ ↩²⁠

2. Can be a list, separated by ;, ,, (space), (linebreak), or (tab) ↩⁠ ↩²⁠ ↩³⁠ ↩⁴⁠

3. If you would like to use a proxy in a docker container, but your proxy is in your host machine, the hostname should be 172.17.0.1 (Linux) or host.docker.internal (macOS/Windows). Note: your proxy program should also listen to it. ↩⁠ ↩²⁠ ↩³⁠ ↩⁴⁠

4. Use with caution. Enabling it will enforce the bot to try to fetch feeds over IPv6 (fallback to IPv4 if failed), which may be helpful if your IPv4 address gets banned by some feed providers. If it is disabled (by default), the bot will still try to fetch feeds over IPv4 and IPv6, but there is no clear priority. You should firstly ensure that the bot has IPv6 connectivity, especially if run in docker. ↩⁠ ↩²⁠

5. Use with caution. May cause media validating and sending slightly unreliable. Meanwhile, effectively disable webpage title detection for <iframe> tags, instead, the title will always be URL hostname. ↩⁠ ↩²⁠

6. Use with caution. Help cut down network traffic further. If enabled, RSStT no longer fetches media and validates it. Effectively disable long-pic detection and partially disable icon detection. ↩⁠ ↩²⁠

7. Ref: https://tortoise-orm.readthedocs.io/en/latest/databases.html⁠. Note that Railway.app will automatically fill this env variable. ↩⁠ ↩²⁠

8. Use with caution. If enabled, the bot manager can bypass the permission check before manipulating any users'/channels'/groups' subscriptions. The command format is like /sub @username, /sub +9999999999 (ordinary user) or /sub -1009999999999 (channel/group). Should only be used temporarily and be disabled after finishing the manipulation. This option is considered safe for bot users since the bot manager can always manipulate their subscriptions by manipulating the database manually. ↩⁠ ↩²⁠

9. Only valid when there are more than 1 CPU core, otherwise the process count is always 1. Enabling multiprocessing may help improve the performance on multicore CPUs if there are tons of subscriptions but consumes more memory. If your VPS comes with multiple cores but the performance of each is poor, you may want to enable this feature. ↩⁠ ↩²⁠

10. After a user subscribes to a feed, the default monitoring interval is applied. ↩⁠ ↩²⁠

11. The minimal monitoring interval a user can set for a subscription. ↩⁠ ↩²⁠

12. The bot manager will not be limited by this value. ↩⁠ ↩²⁠ ↩³⁠ ↩⁴⁠ ↩⁵⁠ ↩⁶⁠

13. Once reached the limit, no more subscriptions can be created. However, existing subscriptions will not be removed even if reaching the limit. As a bot manager, you can enable MANAGER_PRIVILEGED mode to manually unsubscribe their subscriptions. ↩⁠ ↩²⁠ ↩³⁠ ↩⁴⁠