Kallithea issues archive

I would love this feature as well! We need a way to disable/enable/schedule this function per repo so that each individual repo can be scheduled differently.

This would be beneficial for my company as well .. either to have this built in kallithea or some documentation on recommendations how to achieve this reliably

I have a working implementation for this. But it requires celerybeat. So it makes the setup a bit more complicated because it needs 2 celery processes.

FWIW, this is quite simple to do by using an external scheduler (like cron on *nix or the equivalent Windows thing I don't remember the name of) to send a requests to the Kallithea JSON-RPC API. There's even an example on the API docs page:

curl https://kallithea.example.com/_admin/api -X POST -H 'content-type:text/plain' \
--data-binary '{"id":1,"api_key":"xe7cdb2v278e4evbdf5vs04v832v0efvcbcve4a3","method":"pull","args":{"repo":"CPython"}}'

@kwi thanks for the example, this would most certainly be doable. The thing is cron is a bit unreliable for what we're trying to achieve, and that is near instant sync after the change is done to the remote repository, not to mention that we have 100+ repositories, and some of them are not that active, so we'd be requesting for update when there are no changes.

My thought was setting up a hook on the remote repository that would notify Kallithea to pull on every successful change to the repository source, and your example with using the JSON-RPC API might just do the trick. That way Kallithea would pull the changes from the remote only when there are actual changes on the source.

To be fair this issue is opened with scheduled updates in mind so your suggestion is very much valid :)

Yeah, for "live" syncing, you'll need a hook on the source... and in that case, it might be preferable to have that hook push to Kallithea, ensuring that the original "hg push" does not return before the changes have been synced to the mirror.