One-off jobs: run a command once against your service
What a one-off job is for, from a database migration to a data backfill, and how to run a task against your Voroa service and its database at the moment.
What this covers
A one-off job runs a single command in the same environment as your service, with the same code and the same variables, and then exits. The classic uses are a database migration after a release, a one-time backfill of a column, or a script to correct data after a bug. Doing it this way rather than from your own machine matters because the job sees exactly what your service sees, so it cannot fail because of a version difference or a missing variable on your laptop.
One-off jobs are not available on Voroa today. A command that needs to run once can be scheduled as a task and removed afterwards, or run from your own machine against the database directly.