Closed phgross closed 5 years ago
Initial thoughts:
bin/instance run
for stuff which requires guarantees of when the jobs run
There seems to be decent scaffolding to build upon: https://github.com/plone/ansible.plone_server https://github.com/plone/ansible.plone_server/blob/6b738ead23a5e499e35868ca2fc18c793ed4f241/tasks/main.yml#L351
https://pypi.python.org/pypi/slc.zopescript
Just spotted this: are we building our current ones on top of that or how are we rolling?
CastleCMS is using Celery:
@Rotonen We may also need a queueing / messaging solution for the SPV, depending in which path we walk. It would be great to have your opinion on that too: https://basecamp.com/2768704/projects/13482340/todos/313087237
@jone from my point of view these are the same thing - there is no sense in doing something which would not cover both.
update from a quick discussion regarding consistency checks: also check expected service version (e.g. for bumblebee), add required service endpoint to do so if required
This seems to have been superseded by https://github.com/4teamwork/opengever.core/pull/5566 ?
With the Nightly Jobs feature (#5566) there is now a setup for nightly jobs. New jobs like the removal of the original files or trashed documents, is now possible by registering an additional JobAdapter.
Usecases GEVER:
Karrenzfrist
is expiredKarrenzfrist
is expiredmyteamraum:
plone maintenance in general:
ftw.copymovepatches
' fixesIdeas, questions and thoughts
SearchableText
for all objects, the system should be able to split that up into batches and run them over a period of multiple nights.