unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jim Dupont <jmikedupont2@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: cuirass building and deployment
Date: Sun, 24 Mar 2024 12:27:50 +0100	[thread overview]
Message-ID: <8734sfrhs9.fsf@gnu.org> (raw)
In-Reply-To: <CAAaxPMt+KODsJB1_mhSTnwPSq7KDndnhLqcTiFO8JobSHq1m_g@mail.gmail.com> (Jim Dupont's message of "Sat, 23 Mar 2024 16:25:47 -0400")

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’.


  reply	other threads:[~2024-03-24 11:28 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 [this message]
2024-03-24 11:48   ` Jim Dupont

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=8734sfrhs9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jmikedupont2@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 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).