Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using a cron like settings #16

Closed
wants to merge 1 commit into from
Closed

Using a cron like settings #16

wants to merge 1 commit into from

Conversation

feddar
Copy link

@feddar feddar commented Sep 17, 2018

Check a time like cron settings instead of every x minutes. See #13

Check a time like cron settings instead of every x minutes. See #13
@djmaze
Copy link
Collaborator

djmaze commented Sep 17, 2018

Well, thanks for your effort, but that code is currently not in a state as clean as I like it to.

I am currently thinking of building a real swarm scheduler as a separate service. Then shepherd would just add have a service label for its cron schedule.

@stale
Copy link

stale bot commented Jul 22, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 22, 2019
@stale stale bot closed this Jul 29, 2019
@bf8392
Copy link

bf8392 commented Apr 10, 2020

I've maybe a solution for that...how would be using crazymax/cronjob for this? It's a swarm enabled sheduler...nervertheless some adjustments to the code have to be made, as the container would have to exit after the updates...otherwise it wouldn't work...would also love to see this "cron like shedule" implemented =) It's more convinient if you run a stack with collabora or something like this, because if the container get's updated unexpectedly, userdata is possibly lost...so I do this updates nirmally at 2.00 am...

@djmaze
Copy link
Collaborator

djmaze commented Apr 11, 2020

Yes, I was planning to use crazymax/swarm-cronjob for this. Unfortunately, it does not work correctly for containers deployed in global mode, so using it for backing up all your nodes is currently a rather awkward experience. Looks like job support will be part of the next Docker release, so we might finally be able to solve this problem.

Also, using swarm-cronjob would mean to have a different approach for people using swarm vs plain docker/compose setups. Will have to see if it would rather make sense to have a separate script for swarm setups.

@bf8392
Copy link

bf8392 commented Apr 12, 2020

Okay very cool =). I'ts the last missing feature for beeing a completely perfect solution for automatic-updates on swarm =). Thanks for all the effort =)

@n1nj4888
Copy link

n1nj4888 commented Oct 9, 2020

@djmaze Any update on this? Would be great to have cron-style scheduling support in shepherd!

@djmaze
Copy link
Collaborator

djmaze commented Oct 14, 2020

I did not yet find time to work on this.

@djmaze
Copy link
Collaborator

djmaze commented Dec 20, 2022

See #89.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants