Track repository information in database #326

New Issue

Jef Roosens · 2022-12-28T23:56:49+01:00

Jef Roosens commented

2022-12-28 23:56:49 +01:00

Having this information readily available in a (separate, managed by the RepoGroupManager) database could be very useful for later features.

The biggest one would be being able to query information about the repositories using the API. Metrics would be easier to collect as data is easily retrieved. Generally, a greater level of control over the repositories could be achieved.

Having efficient access to the dependencies of a package could also make it possible to rebuild packages on dependency updates, etc.

Having this information readily available in a (separate, managed by the RepoGroupManager) database could be very useful for later features. The biggest one would be being able to query information about the repositories using the API. Metrics would be easier to collect as data is easily retrieved. Generally, a greater level of control over the repositories could be achieved. Having efficient access to the dependencies of a package could also make it possible to rebuild packages on dependency updates, etc.

Jef Roosens added the

enhancement

label 2022-12-28 23:56:49 +01:00

Jef Roosens added a new dependency 2022-12-29 09:17:37 +01:00

#327 Interact with repositories using API

Jef Roosens added a new dependency 2022-12-29 10:19:03 +01:00

#133 Allow configuring base image per repo

Jef Roosens added this to the 0.6.0 milestone 2022-12-29 10:19:33 +01:00

Jef Roosens referenced this issue

2023-01-02 15:07:23 +01:00

Web UI #165

Jef Roosens commented

2023-01-03 13:22:00 +01:00

Poster

Some thoughts on this:

Libarchive allows writing arbitrary bytes into archive entries, so the contents of the desc & files files could be generated on the fly when re-creating the archives. Therefore, storing these files separately would no long be needed.
The HEAD request used by builds can be replaced by an API request.
Some of the repository code could probably use a refactor
Generating the contents of a desc file should probably be done using a string builder instead

Some thoughts on this: * Libarchive allows writing arbitrary bytes into archive entries, so the contents of the `desc` & `files` files could be generated on the fly when re-creating the archives. Therefore, storing these files separately would no long be needed. * The `HEAD` request used by builds can be replaced by an API request. * Some of the repository code could probably use a refactor * Generating the contents of a `desc` file should probably be done using a string builder instead

Jef Roosens modified the milestone from 0.6.0 to 0.7.0

2023-06-04 09:14:24 +02:00

Sign in to join this conversation.