-
Notifications
You must be signed in to change notification settings - Fork 87
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
run shepherd via cron #76
Conversation
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the very late response!
Running shepherd via cron is a good idea. I find this approach using crond
a bit ugly but I guess it's the easist way to do this cross-platform..
Wondering if it is the right way to handle it inside shepherd. |
in relation to my previous comment, I just discovered the option |
@rbauduin You are absolutely right. I am using that approach all the time but somehow this thought did not come to my mind when looking at this PR. I would go even further and say the usage of swarm-cronjob should be the recommended approach of using shepherd. I guess we should adjust the README accordingly. @shizunge Very sorry for the delay and everything, but with the above said it does not make sense to merge this PR. |
This comment was marked as spam.
This comment was marked as spam.
See #89. |
No description provided.