On 2026-01-24 10:34, Christopher Baines wrote:
[email protected] writes:
but... the cgit service isn't cooperating at all, and my knowledge is
not good enough to troubleshoot what's going wrong. I can run the
nginx service for my main web site, or the cgit service, but not both
at the same time. I've attached what my services look like in the main
configuration file (I replace "website" with my domain when I want to
test it). Does anyone know what could be the problem?
Why can't you run both at the same time? What specifically doesn't
work?
I can technically implement both, and my regular web page at
"website.org" loads just fine, but with the services config snippet I
attached previously, "git.website.org" gives a 403 response after a long
wait time. I am not sure what to do about that. If I use just a plain
`(service cgit-service-type)` with the default configuration (and remove
the other nginx service for "website.org" due to the conflictson port
80), then that works to load the cgit interface at "website.org", it's
specifically trying to get the original nginx service for "website.org"
and the other from cgit at "git.website.org" when things don't seem to
work. My apologies for the confusion. Aside from the services snippet I
uploaded, there's nothing else in the system configuration aside from
disks/filesystem boilerplate and adding emacs as a system package.
Also, your NGinx configuration for cgit looks incomplete, there's
nothing telling NGinx to use the cgit named location, e.g. "(try-files
(list "$uri" "@cgit"))" from the default Guix configuration.
I see, I saw this looking into the cgit.scm methods and wasn't sure what
it did. I'm still figuring out what things mean in Scheme as I read it.
Would that mean that the finished system configuration at
https://raven.hallsby.com/running-your-website-using-guix-system.html is
incomplete, too? I don't see any mention of it there, either, and I've
been following along with that.
