Proposal: Cron support about encore HOT 6 CLOSED

Adding that support would make the configuration much more complex. I think your idea of supporting querying the environment at runtime is a reasonable one and something we need for other use cases as well!

from encore.

I agree with taking Kubernetes CronJob design approach, it looks straightforward and what I would expect without any supripses. I like the config approach as well.

I am not a fan of endpoints without params only limitation. Sometimes it would be very helpful to be able to have params available for use. If it's unreasonably time expensive to implement I will be able to live without it, no problem with that.

from encore.

Thanks @pbrazdil for the feedback! What use cases are you thinking of for passing parameters? Could you define a parameter-less endpoint for use with cron that calls another endpoint with parameters?

from encore.

What do you think about the posibility to run cron jobs for individual environments? We have a use case where we have an environment for demo purposes (a production environment) which we regularly want to add new data to.

Is there otherwise any way to dynamically in the endpoint retreive what environment we are running in, e.g. via some environment variable? In that case we could guard when to run the code.

from encore.

Seems like a good pragmatic approach for the short/mid term to me. Long term, I think it would be nice to consider the possibility of a "task/job queue" approach to this, which might let us specify some of the retry semantics, and open up the possibility of a more powerful API for programatic tasks (e.g. I want to spawn some job every hour after somebody signs up in my app for the first 8 hours). We'd also then get sub-minute resolution (I'm currently building a system outside of encore which requires this).

There are some existing projects you could take inspiration from like. https://github.com/RichardKnop/machinery

from encore.

This is now live in v0.19.0! 🎉

from encore.