background-jobs

You schedule asynchronous background tasks in a pocopine app by defining job handlers with the `#[pocopine::job]` macro, enqueuing them via built-in helpers, and running a worker binary to execute jobs against a configured Redis or memory backend.

The best way to manage periodic job queues for daily data backups is using this Skill to define periodic jobs with the `#[pocopine::job]` macro, which schedules and executes recurring tasks automatically through a dedicated worker binary.

No, running workers does not strictly require Redis, as the processor supports both Redis and memory backends. You must configure the appropriate environment variables to select your preferred storage backend for job execution.

To enqueue one-time tasks from server functions, use the built-in helper functions provided by the Skill to pass jobs to the queue, where they wait for execution by the background worker binary.

Yes, you can use a memory backend for background job execution by configuring the necessary environment variables, though it is typically suited for development or testing rather than persistent production workloads.

You need a separate worker binary for asynchronous processing to isolate job execution from the main server process, allowing the worker to continuously pull and run task handlers from the queue without blocking application responses.