Automated tasks with cron jobs and actions

Run automated tasks for your applications with cron jobs. You can define cron jobs using crontab syntax with a command to run in a container. Every cron job execution output will be logged and reported in case of failure.

Some stacks know which cron jobs to run

Some of the services, especially stack-specific (e.g. PHP service for Laravel stack), come with pre-defined cron jobs. They can optionally disabled or completely removed on a stack level. You can adjust cron schedules in stack configuration or per app instance.

Cron jobs execution logged

Every cron jobs execution logged. In case of failure you will be notified of the error to give heads up if something is broken. You can examine history of jobs that were run on schedule and their status.

Run different cron jobs per environment

Sometimes cron jobs that you run in production may differ from the one you run in dev and staging environments. With Wodby you can configure different cron schedules for each environment.

Actions

Actions is a feature offered by our services to execute routine tasks during certain events such as stack upgrade, after deployment or on-demand. You can also define your own actions via post-deployments scripts in your git repository.

Many services provide out-of-the-box actions to execute routine tasks on certain events such as after deployment or stack upgrade, for example to run upgrade action when a service updated (e.g. think of mysql-upgrade and mysql-check for MySQL).

To automatically execute routine tasks such as database migrations, cache clearance you can write your own post-deployment scripts that will run automatically after each deployment as a part of your CI/CD workflow.

Run actions from UI

For convenience some services offer button actions that can be executed from UI, for example routine cache clearing commands.