Skip to content

Conversation

@tennisleng
Copy link

Fixes issue #163 where config.yaml modifications were not picked up in Docker deployments

Problem

In Docker deployments (especially on Feiniu NAS), config.yaml changes were not being read because the CONFIG was loaded once at module import time and cached throughout the process lifetime.

Solution

  • Move CONFIG loading from module level to main() function so config is reloaded on each execution
  • Add early return in run() method when crawler is disabled to prevent unnecessary processing
  • This ensures Docker cron jobs pick up config changes on each run

Testing

  • Verified config changes are now picked up on each run
  • Confirmed enable_crawler=false properly disables crawling without running data fetch operations
  • All other config options (report mode, push window, webhooks, etc.) are now reloadable

Resolves: #163

- Fix issue where config.yaml modifications were not picked up in Docker deployments
- Move CONFIG loading from module level to main() function so config is reloaded on each execution
- Add early return in run() method when crawler is disabled to prevent unnecessary processing
- This resolves the reported issue sansan0#163 where config changes in Feiniu NAS Docker deployment were ineffective
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[问题] 我在飞牛NAS的docker部署过程中修改config.yaml无效

1 participant