Ah, you're encountering the age-old problem of asynchronous recurring tasks, better known as cron. Your current GitHub Actions workflow is a clever workaround, but it might not be the most efficient or scalable solution in the long run. Given that you're already using specific tooling for your product, I'd suggest one of the following options:
Alternatively, you can roll your own solution. For example, #daylang runs in a single Docker container on Railway. This container bundles the API, cron task emitter, and cron task consumer as a Go application.
Each approach has its merits, so choose the one that best fits your stack and workflow.
Ah, you're encountering the age-old problem of asynchronous recurring tasks, better known as cron. Your current GitHub Actions workflow is a clever workaround, but it might not be the most efficient or scalable solution in the long run. Given that you're already using specific tooling for your product, I'd suggest one of the following options:
Alternatively, you can roll your own solution. For example, #daylang runs in a single Docker container on Railway. This container bundles the API, cron task emitter, and cron task consumer as a Go application.
Each approach has its merits, so choose the one that best fits your stack and workflow.