From: Jim Dupont <jmikedupont2@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: cuirass building and deployment
Date: Sun, 24 Mar 2024 07:48:07 -0400 [thread overview]
Message-ID: <CAAaxPMtsjrY-13BR5uVAWoNq5ukvUs367qJWFkqkTedxzKUesw@mail.gmail.com> (raw)
In-Reply-To: <8734sfrhs9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]
i will report more, for now you can see there are thousands of build errors
tryign to bootstrap
http://34.41.82.208:8080/eval/7?status=failed
On Sun, Mar 24, 2024, 07:27 Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> Jim Dupont <jmikedupont2@gmail.com> skribis:
>
> > have been struggling to deploy cuirass on a gcp cluster.
> > I was able to install it manually on one machine and use it from guix
> > talking to postgres and nginx running in ubuntu. the shepherd wont build
> or
> > install, needs more love.
> > I have gotten to finally build on guix and can export the package from
> one
> > system to another.
> > Can someone help me understand how to document the exact steps to
> reproduce
> > a build?
> > There are constant issues with guile modules not found or loading,
> > autoconfig failing or other errors,
>
> Could you be more specific about the build errors you encounter?
>
> To run Cuirass, the best option is install the ‘cuirass’ package in
> Guix: ‘guix install cuirass’. Then you can start the ‘cuirass register’
> and ‘cuirass web’ processes manually or get systemd to handle them (I
> don’t think Cuirass provides ‘.service’ files, but it should.)
>
> If you want to be on the bleeding edge (not recommended), the easiest
> way is to run ‘guix build -f guix.scm’ from the Cuirass source tree.
>
> HTH!
>
> Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 1911 bytes --]
prev parent reply other threads:[~2024-03-24 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 20:25 cuirass building and deployment Jim Dupont
2024-03-24 11:27 ` Ludovic Courtès
2024-03-24 11:48 ` Jim Dupont [this message]
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=CAAaxPMtsjrY-13BR5uVAWoNq5ukvUs367qJWFkqkTedxzKUesw@mail.gmail.com \
--to=jmikedupont2@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).