jobber pulls statistics

DEPRECATION NOTICE

This project is not actively maintained. See dshearer/jobber#334 for more details.

Quick reference

• Maintained by:
  Jobber

• Where to get help:
  the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow

Supported tags and respective Dockerfile links

No supported tags

Quick reference (cont.)

• Where to file issues:
  https://github.com/dshearer/jobber-docker/issues

• Supported architectures: (more info)
  No supported architectures

• Published image artifact details:
  repo-info repo's repos/jobber/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images repo's library/jobber label
  official-images repo's library/jobber file (history)

• Source of this description:
  docs repo's jobber/ directory (history)

What is Jobber?

Jobber is a utility for Unix-like systems that can run arbitrary commands, or "jobs", according to a schedule. It is meant to be a better alternative to the classic Unix utility cron.

Along with the functionality of cron, Jobber also provides:

• Job execution history: you can see what jobs have recently run, and whether they succeeded or failed.
• Sophisticated error handling: you can control whether and when a job is run again after it fails. For example, after an initial failure of a job, Jobber can schedule future runs using an exponential backoff algorithm.
• Sophisticated error reporting: you can control whether Jobber notifies you about each failed run, or only about jobs that have been disabled due to repeated failures.

How to use this image

This image contains Jobber running as an unprivileged user named "jobberuser". The jobs are defined in the file /home/jobberuser/.jobber. By default, the only job is one that prints "Jobber is running!" every second. You should replace it with your own jobs. Refer to the documentation to learn how to do this.

License

Jobber's license

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's jobber/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.