unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mekeor Melire <mekeor@posteo.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: 404 errors with hpcguix-web (e.g. for /packages.json)
Date: Wed, 27 Apr 2022 21:07:21 +0000	[thread overview]
Message-ID: <875ymub4zi.fsf@posteo.de> (raw)
In-Reply-To: <87y1zq2wv2.fsf@elephly.net>

Thank you for the hint. hpcguix-web is awesome! I installed it locally
with the following declaration:

--8<---------------cut here---------------start------------->8---
;; added modules: (guix channels) (gnu services web)
(service hpcguix-web-service-type
  (hpcguix-web-configuration
    (specs
      #~(define site-config
          (hpcweb-configuration
            (channels
              (cons*
                ;; ...
                %default-channels
                )))))))
--8<---------------cut here---------------end--------------->8---

When I open the website (http://127.0.0.1:5000) in the browser, no
packages are listed and the browser console shows 404-errors occurring
for the following routes:

http://127.0.0.1:5000/static/css/code.css
http://127.0.0.1:5000/static/images/h-separator-darker.png
http://127.0.0.1:5000/packages.json
http://127.0.0.1:5000/static/images/favicon.png

Does hpcguix-web depend on a web-server (like nginx) to server a certain
folder? Or what am I missing?



2022-04-27 / 20:37 / rekado@elephly.net:

> Hi Mekeor,
>
>> it would be nice to be able to search for a package (and/or a service)
>> by name or description etc. through many channels. AFAIK, there's no
>> such search engine yet. Please correct me if I'm wrong.
>>
>> I'm considering to implement it. I'd suggest to approach it with a
>> server where (1) Guix is installed; (2) a long list of channels is
>> activated; (3) a cron-job or so which regularly runs `guix pull`; (4) a
>> web-api-service written in Guile which leverages the Guix-library in
>> order to search for packages (-- I guess it'd be calling the
>> `guix-package*` function from /guix/scripts/package.scm?); (5) a
>> simplistic front-end web-site which talks to the web-api.
>
> See https://github.com/UMCUGenetics/hpcguix-web.  It handles the
> constant updates to all Guix channels and the search.  You’re welcome to
> contribute to it, e.g. to add an API, suggest changes in how results are
> displayed, etc.
>
> An example deployment can be found at https://guix.mdc-berlin.de
>
> Guix has a service for it that makes deployment easy.
>
> You’ll see that it lists packages from guix-science and other channels,
> e.g. https://guix.mdc-berlin.de/package/rstudio-server



  reply	other threads:[~2022-04-27 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 13:51 A package search engine for a curated list of channels Mekeor Melire
2022-04-27 15:08 ` Edouard Klein
2022-04-27 18:37 ` Ricardo Wurmus
2022-04-27 21:07   ` Mekeor Melire [this message]
2022-05-04 22:25     ` Show: Minimal Working Example of hpcguix-web Mekeor Melire
2022-05-04 22:29   ` A package search engine for a curated list of channels Mekeor Melire
2022-05-05  9:01     ` Ricardo Wurmus
2022-09-03 10:24   ` zimoun

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=875ymub4zi.fsf@posteo.de \
    --to=mekeor@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).