Cron code refactoring #178

New Issue

Jef Roosens · 2022-05-12T10:36:13+02:00

Jef Roosens commented

2022-05-12 10:36:13 +02:00

It might be possible to completely separate the cron code from Vieter & publish it separately to vpm. I'd really like to do this because I have other plans with the cron code, e.g. an automatic builder of Docker images.

The cron code currently is very heavily tailored towards Vieter. I'd like to gradually change this.

For one, I'd like all recurring actions to be placed inside the pqueue, instead of just the builds. Polling the repos, rebuilding the builder image... all of these things could be added to the pqueue by defining a struct which takes a function as an argument.

The next step then is to use generics to completely decouple the cron code from Vieter the way vweb does.

After these two steps, I think it would be possible to split the cron code completely from Vieter & publish it separately.

It might be possible to completely separate the cron code from Vieter & publish it separately to vpm. I'd really like to do this because I have other plans with the cron code, e.g. an automatic builder of Docker images. The cron code currently is very heavily tailored towards Vieter. I'd like to gradually change this. For one, I'd like all recurring actions to be placed inside the pqueue, instead of just the builds. Polling the repos, rebuilding the builder image... all of these things could be added to the pqueue by defining a struct which takes a function as an argument. The next step then is to use generics to completely decouple the cron code from Vieter the way vweb does. After these two steps, I think it would be possible to split the cron code completely from Vieter & publish it separately.

Jef Roosens added the

idea

label 2022-05-12 10:36:13 +02:00

Jef Roosens changed title from ~~Split cron code into own V package~~ to Cron code refactoring

2022-05-12 10:43:26 +02:00

Jef Roosens commented

2023-01-28 15:45:39 +01:00

Poster

The cron code is now contained in libvieter, so this issue is no longer relevant.

Jef Roosens closed this issue

2023-01-28 15:45:39 +01:00

Sign in to join this conversation.