[Docker] Prevent initial run when using cron_schedule

[726a67]

When deployed via docker, podsync performs an initial run and then uses either update_period or cron_schedule to determine when subsequent runs will be performed.

Generally speaking, the purpose of utilizing a cron schedule is to ensure that a given automated process kicks off at a fixed time, date, or interval. In podsync's case, the initial run at least partially undermines the purpose of the cron schedule, since the automated process can be kicked off outside of the defined schedule.

While this isn't a huge issue in and of itself, it can lead to some problematic outcomes, including increased API token usage if the docker container/stack is frequently recreated, and unintended inter-container dependency issues (e.g. podsync attempts to perform a run before a linked vpn container is ready).

One solution to this problem might be to prevent podsync from performing its initial run for feeds where cron_schedule is defined.

Thoughts?

[mxpv]

@claude can you take a look and make a PR?

[claude]

Claude finished @mxpv's task —— View job • claude/issue-138-20250722-0346 • Create PR ➔

---

Task Completed ✅

Summary:

Fixed the issue by preventing initial updates when cron_schedule is explicitly configured. The change detects feeds with explicit cron schedules and skips the initial update to prevent unwanted API calls and container dependency issues in Docker deployments.

Changes Made:

• Modified cmd/podsync/main.go:202-223 to check if feed has explicit cron_schedule
• Only perform initial update for feeds using default update_period scheduling
• Feeds with explicit cron schedules now wait for their scheduled time

Testing:

• ✅ All tests pass (make test)
• ✅ Changes committed and pushed to branch