DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

CrazyMax
CrazyMax

Posted on • Updated on

swarm-cronjob

GitHub logo crazy-max / swarm-cronjob

πŸ“… Create jobs on a time-based schedule on Docker Swarm

GitHub release Total downloads Build Status Docker Stars Docker Pulls
Go Report Code Quality Become a sponsor Donate Paypal

About

swarm-cronjob creates jobs on a time-based schedule on Swarm with a dedicated service in a distributed manner that configures itself automatically and dynamically through labels and Docker API.

πŸ’‘ Want to be notified of new releases? Check out πŸ”” Diun (Docker Image Update Notifier) project!

Features

  • Continuously updates its configuration (no restart)
  • Cron implementation through go routines
  • Allow to skip a job if the service is currently running
  • Timezone can be changed for the scheduler

Documentation

How can I help?

All kinds of contributions are welcome πŸ™Œ! The most basic way to show your support is to star 🌟 the project, or to raise issues πŸ’¬ You can also support this project by becoming a sponsor on GitHub πŸ‘ or by making a Paypal donation to ensure this journey continues indefinitely! πŸš€

Thanks again for your support…




πŸ“… swarm-cronjob creates jobs on a time-based schedule on Swarm 🐳 with a dedicated service in a distributed manner that configures itself automatically and dynamically through labels and Docker API. Here are the main features:

  • Continuously updates its configuration (no restart)
  • Cron implementation through go routines
  • Allow to skip a job if the service is currently running
  • Timezone can be changed for the scheduler

Hope it will help some of you. Your comments are welcome!


Support this project by becoming a sponsor on GitHub πŸ‘ or by making a Paypal donation to ensure this journey continues indefinitely! πŸš€

Thanks again for your support, it is much appreciated! πŸ™

Top comments (0)

Timeless DEV post...

How to write a kickass README

Arguably the single most important piece of documentation for any open source project is the README. A good README not only informs people what the project does and who it is for but also how they use and contribute to it.

If you write a README without sufficient explanation of what your project does or how people can use it then it pretty much defeats the purpose of being open source as other developers are less likely to engage with or contribute towards it.