Skip to content

fix: accept both GET and POST for cron trigger endpoint cron-job.org sends GET by default. Using app.get + app.post ensures the trigger works regardless of which HTTP method the cron service uses. Also renames "Automated Data Collection" to "Automated Weather Refresh" in README and fixes Email Notifications section references.#6

Merged
giancarloerra merged 1 commit intomainfrom
fix/get-post-trigger
Mar 10, 2026

Conversation

@giancarloerra
Copy link
Owner

Summary

Accept both GET and POST methods for the cron trigger endpoint.

Motivation

This change ensures compatibility with cron services like cron-job.org that default to using GET requests.

Changes

  • Updated the cron trigger endpoint to accept both GET and POST requests.

  • Renamed "Automated Data Collection" to "Automated Weather Refresh" in the README.

  • Fixed references in the Email Notifications section.

Testing

  • npm run lint passes

  • npm run typecheck passes

  • npm test passes

  • Verified manually in dev / built production mode

Breaking changes

  • No breaking changes

  • Breaking change — describe migration steps below:

Screenshots (if applicable)


By submitting this pull request I confirm that my contribution is made under the terms of the GNU Affero General Public License v3.0 or later.

cron-job.org sends GET by default. Using app.get + app.post ensures
the trigger works regardless of which HTTP method the cron service uses.
Also renames "Automated Data Collection" to "Automated Weather Refresh"
in README and fixes Email Notifications section references.
@giancarloerra giancarloerra self-assigned this Mar 10, 2026
@giancarloerra giancarloerra merged commit 80e6a14 into main Mar 10, 2026
3 checks passed
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.

1 participant