[GH-ISSUE #118] Email is not sent without cron in daemon mode #28

Closed
opened 2026-09-29 12:58:48 +00:00 by slurdge · 2 comments
Owner

Originally created by @spysir on GitHub (Feb 28, 2023).
Original GitHub issue: https://github.com/slurdge/goeland/issues/118

This is my config.toml

loglevel = "info"
dry-run = false
run-at-startup = true
purge-days = 5

[email]
host = "smtp.xxx.com"
port = 2525
authentication = "none"

[sources]

[sources.hackernews]
url = "https://hnrss.org/newest"
type = "feed"
filters = ["all", "today"]
allow-insecure = false

[pipes]

[pipes.hackernews]
disabled = false
source = "hackernews"
destination = "email"
email_to = ["a@a.com", "b@b.com"]
email_from = ["c@c.com"]

When running 'docker-compose up -d' ,Goeland sends an email, but the feeds will be updated in the future no email will be sent

Originally created by @spysir on GitHub (Feb 28, 2023). Original GitHub issue: https://github.com/slurdge/goeland/issues/118 This is my config.toml ```yaml loglevel = "info" dry-run = false run-at-startup = true purge-days = 5 [email] host = "smtp.xxx.com" port = 2525 authentication = "none" [sources] [sources.hackernews] url = "https://hnrss.org/newest" type = "feed" filters = ["all", "today"] allow-insecure = false [pipes] [pipes.hackernews] disabled = false source = "hackernews" destination = "email" email_to = ["a@a.com", "b@b.com"] email_from = ["c@c.com"] ``` When running 'docker-compose up -d' ,Goeland sends an email, but the feeds will be updated in the future no email will be sent
Author
Owner

@slurdge commented on GitHub (Feb 28, 2023):

Hello @spysir , this is normal, it's because you don't have a cron inside your pipe.
You need to add it like this:

[pipes.hackernews]
disabled = false
source = "hackernews"
destination = "email"
email_to = ["a@a.com", "b@b.com"]
email_from = ["c@c.com"]
cron = "30 12 * * *" #execute the schedule every day at 12h30

We lack documentation for this feature. You are among the first to use docker in daemon mode I think, most people are using a cron with the executable directly. Please inform me if it works correctly !
For cron syntax, you can use https://crontab.guru
Also you can check your logs, if a schedule is detected, it will be shown inside the logs.
To finish, you don't need disabled = false, pipes are enabled by default.

<!-- gh-comment-id:1448160150 --> @slurdge commented on GitHub (Feb 28, 2023): Hello @spysir , this is normal, it's because you don't have a `cron` inside your pipe. You need to add it like this: ```toml [pipes.hackernews] disabled = false source = "hackernews" destination = "email" email_to = ["a@a.com", "b@b.com"] email_from = ["c@c.com"] cron = "30 12 * * *" #execute the schedule every day at 12h30 ``` We lack documentation for this feature. You are among the first to use docker in daemon mode I think, most people are using a cron with the executable directly. Please inform me if it works correctly ! For cron syntax, you can use https://crontab.guru Also you can check your logs, if a schedule is detected, it will be shown inside the logs. To finish, you don't need `disabled = false`, pipes are enabled by default.
Author
Owner

@spysir commented on GitHub (Feb 28, 2023):

[pipes.hackernews]
disabled = false
source = "hackernews"
destination = "email"
email_to = ["a@a.com", "b@b.com"]
email_from = ["c@c.com"]
cron = "*/5 * * * *" ##execute the schedule every 5 seconds

It works ! Thanks

<!-- gh-comment-id:1448206316 --> @spysir commented on GitHub (Feb 28, 2023): > ```yaml [pipes.hackernews] disabled = false source = "hackernews" destination = "email" email_to = ["a@a.com", "b@b.com"] email_from = ["c@c.com"] cron = "*/5 * * * *" ##execute the schedule every 5 seconds ``` It works ! Thanks
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: slurdge/goeland#28
No description provided.