Question 1

How do I install Supercronic in a Docker container?

Accepted Answer

Download a pre-built binary from the releases page and add it to your Dockerfile using example stanzas provided, such as with ADD commands. The README recommends supercronic-linux-amd64 for most cases.

Question 2

Supercronic vs regular cron: which is better for Kubernetes?

Accepted Answer

Supercronic is designed for containers, handling signals gracefully and logging to stdout/stderr for Kubernetes integration, while regular cron may orphan jobs or purge environment variables, causing issues in pods.

Question 3

How can I reload the crontab without restarting Supercronic?

Accepted Answer

Send SIGUSR2 to the Supercronic process or use the -inotify flag to watch for file changes, allowing dynamic reloads in environments like Kubernetes with configMaps, as described in the 'Reload crontab' section.

Question 4

Does Supercronic support running jobs every few seconds?

Accepted Answer

Yes, it supports second-resolution schedules using the cronexpr package, allowing patterns like */5 * * * * * * for every 5 seconds, detailed in the 'Crontab format' section of the README.

Question 5

How to handle environment variables with Supercronic in Docker?

Accepted Answer

Set environment variables in the Dockerfile or via docker run -e, and Supercronic will preserve them for jobs, inheriting as expected. The README advises against using crontab KEY=VALUE syntax for compatibility.

Question 6

Can I integrate error tracking with Supercronic?

Accepted Answer

Yes, optional Sentry integration is available using the -sentry-dsn flag or SENTRY_DSN environment variable, with additional configuration for environment and release tags, as outlined in the 'Sentry' section.

supercronic

What is supercronic?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions