chore:interval

.github/workflows/main.yml

@@ -2,7 +2,8 @@ name: 'Update schedule'
 
 on:
   schedule:
-    - cron: '0 */12 * * *'
+    - cron: '0 22 * * *'
+    - cron: '0 10 * * *'
   workflow_dispatch:
     branches:
       - master

Dockerfile

@@ -43,7 +43,9 @@ RUN apt-get update && apt-get install -y --no-install-recommends cron
 RUN if [ "$LITE" = False ]; then apt-get install -y --no-install-recommends chromium chromium-driver; fi \
   && apt-get clean && rm -rf /var/lib/apt/lists/*
 
-RUN (crontab -l ; echo "0 */12 * * * cd $APP_WORKDIR && /.venv/bin/python main.py";) | crontab -
+RUN (crontab -l ; \
+  echo "0 22 * * * cd $APP_WORKDIR && /.venv/bin/python main.py"; \
+  echo "0 10 * * * cd $APP_WORKDIR && /.venv/bin/python main.py") | crontab -
 
 EXPOSE 8000
 

README.md

@@ -93,7 +93,7 @@
 - ✅ 支持多种获取源方式：组播源、酒店源、订阅源、关键字搜索
 - ✅ 接口测速验效，响应时间、分辨率优先级，过滤无效接口
 - ✅ 偏好设置：IPv6、接口来源排序优先级与数量配置、接口白名单
-- ✅ 定时执行，每 12 小时更新一次
+- ✅ 定时执行，北京时间每日 6:00 与 18:00 执行更新
 - ✅ 支持多种运行方式：工作流、命令行、GUI 软件、Docker(amd64/arm64/arm v7)
 - ✨ 更多功能请见[配置参数](./docs/config.md)
 

README_en.md

@@ -93,7 +93,7 @@
 - ✅ Supports multiple source acquisition methods: multicast source, hotel source, subscription source, keyword search
 - ✅ Interface speed testing and verification, with priority on response time and resolution, filtering out ineffective interfaces
 - ✅ Preferences: IPv6, priority and quantity of interface source sorting, and interface whitelist
-- ✅ The result is updated every 12 hours
+- ✅ Scheduled execution at 6:00 AM and 18:00 PM Beijing time daily
 - ✅ Supports various execution methods: workflows, command line, GUI software, Docker(amd64/arm64/arm v7)
 - ✨ For more features, see [Config parameter](./docs/config_en.md)
 

docs/tutorial.md

@@ -149,16 +149,17 @@ https://mirror.ghproxy.com/raw.githubusercontent.com/您的github用户名/仓
 
 如果访问该链接能正常返回更新后的接口内容，说明您的直播源接口链接已经大功告成了！将该链接复制粘贴到 TVBox 等软件配置栏中即可使用~
 
-- 注意：除了首次执行工作流需要您手动触发，后续执行（默认每 12 小时）将自动触发。如果您修改了模板或配置文件想立刻执行更新，可手动触发（2）中的 Run workflow 即可。
+- 注意：除了首次执行工作流需要您手动触发，后续执行（默认北京时间每日 6:00 与 18:00）将自动触发。如果您修改了模板或配置文件想立刻执行更新，可手动触发（2）中的 Run workflow 即可。
 
 ### 4.修改工作流更新频率（可选）
 
-如果您想修改更新频率（默认每 12 小时），可修改 on:schedule:- cron 字段：
+如果您想修改更新频率（默认北京时间每日 6:00 与 18:00），可修改 on:schedule:- cron 字段：
 ![.github/workflows/main.yml](./images/schedule-cron.png '.github/workflows/main.yml')
 如果您想 每 2 天执行更新可以这样修改：
 
 ```bash
 - cron: '0 22 */2 * *'
+- cron: '0 10 */2 * *'
 ```
 
 #### 1. 强烈不建议修改更新频率过高，因为短时间内的接口内容并无差异，过高的更新频率与高耗时运行的工作流都有可能被判定为资源滥用，导致仓库与账户被封禁的风险。

docs/tutorial_en.md

@@ -146,16 +146,17 @@ https://mirror.ghproxy.com/raw.githubusercontent.com/your github username/reposi
 
 If you can access this link and it returns the updated interface content, then your live source interface link has been successfully created! Simply copy and paste this link into software like TVBox in the configuration field to use~
 
-- Note: Except for the first execution of the workflow, which requires you to manually trigger it, subsequent executions (default every 12 hours) will be automatically triggered. If you have modified the template or configuration files and want to execute the update immediately, you can manually trigger (2) Run workflow.
+- Note: Except for the first execution of the workflow, which requires you to manually trigger it, subsequent executions (default: 6:00 AM and 18:00 PM Beijing time daily) will be automatically triggered. If you have modified the template or configuration files and want to execute the update immediately, you can manually trigger (2) Run workflow.
 
 ### 4.Modify Workflow Update Frequency(optional)
 
-If you want to modify the update frequency (default every 12 hours), you can modify the on:schedule:- cron field.
+If you want to modify the update frequency (default: 6:00 AM and 18:00 PM Beijing time daily), you can modify the on:schedule:- cron field.
 ![.github/workflows/main.yml](./images/schedule-cron.png '.github/workflows/main.yml')
 If you want to perform updates every 2 days, you can modify it like this:
 
 ```bash
 - cron: '0 22 */2 * *'
+- cron: '0 10 */2 * *'
 ```
 
 #### 1. It is strongly not recommended to modify and update too frequently, because the interface content does not differ within a short period of time, and too high update frequency and time-consuming workflow may be judged as resource abuse, resulting in the risk of warehouse and account being blocked.