TGTGInsighttelegram intelligenceLIVE / telegram public index
← 凌莞的奇奇怪怪的分享

TGINSIGHT SIMILAR POSTS

查找相似内容

Source channel @ttyUSB0w · Post #1663 · 5月12日

#出售#电子垃圾#zigbee 联系 Clansty ad Astra 价格 18 + 邮费 zigbee USB dongle 基于 TYZS13 EFR32MG13,支持 z2m 和 zha 自己刷机刷炸了,现在寄给闲鱼卖家刷,不想再出两份邮费了,刷完之后直接寄给你。你只要付寄给你的邮费 预览模式,不会发送到频道,请注意,您的用户名需要手动更新才能确保发送时和此处一致。

Results

找到 3 条相似帖子

搜索 #webhook

当前筛选 #webhook清除筛选
djangoproject

@djangoproject · Post #121 · 2016/08/25 04:39

https://gist.github.com/leandrotoledo/4e9362acdc5db33ae16c # This file is an annotated example of a #webhook based #bot for #telegram. It does not do anything useful, other than provide a quick # template for whipping up a testbot. Basically, fill in the CONFIG # section and run it. # Dependencies (use pip to install them): # - python-telegram-bot: https://github.com/leandrotoledo/python-telegram-bot # - Flask : http://flask.pocoo.org/ # Self-signed SSL certificate (make sure 'Common Name' matches your FQDN): # $ openssl req -new -x509 -nodes -newkey rsa:1024 -keyout server.key -out server.crt -days 3650 # You can test SSL handshake running this script and trying to connect using wget: # $ wget -O /dev/null https://$HOST:$PORT/

探索号

@seeker_rc · Post #19936 · 2026/05/08 02:25

开发了个简单的 ping-pong+监控的小软件 软件有三个功能: 1. 启动时会访问设置好的 webhook (目的:在系统启动成功或母机意外重启时给自己发一条通知,能及时知道) 2. 启动一个 ping-pong http 服务,默认端口 10101 (目的:可以让另外一台主机检测本机是否运行正常) 3. 可以监控一个或多个设定的 url (一个简单的定检测功能,可以监控给定的 url 是否正常运行,如果访问失败,会请求前面设定的 webhook ,并支持修改参数) github: <https://github.com/yafoo/ping-pong> 如果你有这方面需求可以试试。 ... via V2EX 分享创造 标签: #ping#pong#webhook ⚡️探索号频道 ⚡️探索者频道 ⚡️探索者交流群 ⚡️ Youtube 频道:科技探索者 每天推荐有趣内容,欢迎订阅、转发。

djangoproject

@djangoproject · Post #122 · 2016/08/25 04:45

https://github.com/python-telegram-bot/python-telegram-bot/wiki/Webhooks#heroku On #Heroku using #webhook can be beneficial on the free-plan because it will automatically manage the downtime required. The reverse proxy is set up for you and an environment is created. From this environment you will have to extract the port the #bot is supposed to listen on. Heroku manages the #SSL on the #proxy side, so you don't have provide the certificate yourself.