On Fri, Jun 16, 2023 at 12:28:05PM +0200, Christian Kastner wrote:
> Hi,
>
> When I run `debci html update`, I get an index page, but no sub-pages.
> notably no package pages. I'd appreciate hints as to what I'm missing.
>
>
> Assuming a pristine debci instance:
>
> I enqueued tests for two packages, both completed successfully. On the
> collector host, the results are in /var/lib/data/{autopkgtest,status}.
>
> I then run `debci html update` and `debci html update_package <pkg>`,
> but no matter in what order I do this in, I don't get any output for the
> /packages packages (e.g.: /packages/libo/). index.html gets built
> correctly, it seems.
>
> In fact, in /var/lib/data/.html, the only html page generated is
> index.html itself.
>
> Can anyone give me a pointer to what I'm missing?
Most the static HTML generation has been dropped at this point, because
it doesn't scale well: there are too many files when you do the
combination of packages x architectures x suites number of files
generated for each package. We currently rely on the web application for
serving the web UI dynamically.
debci-collector should probably provide starting points for configuring
a web server, but the moment it doesn't. You can check our config
management repository for how to expose the web app via
apache2+passenger:
https://salsa.debian.org/ci-team/debian-ci-config/
In special for this:
https://salsa.debian.org/ci-team/debian-ci-config/-/blob/master/cookbooks/debci/templates/apache.conf.erb
Attachment:
signature.asc
Description: PGP signature