all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: <guix-devel@gnu.org>
Cc: guix-sysadmin <guix-sysadmin@gnu.org>,
	Simon Tournier <zimon.toutoune@gmail.com>
Subject: Builds of https://guix.gnu.org/{packages,sources}.json
Date: Wed, 04 Jan 2023 23:30:21 +0100	[thread overview]
Message-ID: <87lemi3pc2.fsf@gnu.org> (raw)

Hello Guix!

Until now, the files https://guix.gnu.org/{packages,sources}.json were
built as part of the web site’s build process, via Haunt.  Since these
files provide metadata about packages available in the tip of the Guix
repo, this required getting an inferior for that, and fiddling with it.

This was expensive and made the build process rather complicated (on
bayfront, which currently hosts the web site, missing substitutes would
often cause the web site to not build within the allocate 1h time slot;
this is why recent blog posts took hours to get there).

Thus I moved the former (apps packages builder) module of the web site
to a script in maintenance.git, and had it run as a periodic mcron job
populating /srv/package-metadata, with nginx serving these two files
from that directory:

  5664984 * hydra: web: Add mcron job to build /packages.json and /sources.json.
  318db3e * hydra: Add 'build-package-metadata.scm' script.

I then removed the corresponding bits in guix-artwork.git:

  fe11359 website: Remove references to the latest Guix in '.guix.scm'.
  f71ca12 website: Remove (apps packages builder).

I reconfigured both berlin and bayfront, so they’re now using this
method to build and publish these files.

Feedback welcome!

Ludo’.


             reply	other threads:[~2023-01-04 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 22:30 Ludovic Courtès [this message]
2023-01-05  8:51 ` Builds of https://guix.gnu.org/{packages,sources}.json zimoun
2023-01-09 11:15   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lemi3pc2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-sysadmin@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.