From: Ingo Schwarze <schwarze@usta.de>
To: Aisha Tammy <openbsd@aisha.cc>
Cc: discuss@mandoc.bsd.lv
Subject: Re: Help with setting up man.cgi with nginx
Date: Thu, 10 Dec 2020 14:46:16 +0100 [thread overview]
Message-ID: <20201210134616.GF69368@athene.usta.de> (raw)
In-Reply-To: <00b30a32-e90b-7f72-3120-63e0d38fe36a@aisha.cc>
Hi Aisha,
Aisha Tammy wrote on Wed, Dec 09, 2020 at 07:06:46PM -0500:
> I was trying to set up man.cgi to view my manual pages online and
> haven't been able to find a lot of documentation for setting it up.
Did you look at
https://man.openbsd.org/man.cgi.8
?
> I managed to get the main page to load but its not able to show any
> man pages, only the front page.
I suggest that you inspect the web server logs. That is the usual
method for debugging non-working web server setups.
> I am on Gentoo and am using the nginx webserver.
This sounds as if your question might be more related to how nginx
works than to man.cgi(8). I have very little experience with nginx,
so i fear i won't be able to provide much help for that program.
> I am using the fcgiwrap for passing to man.cgi.
> As man.cgi wants the /man folder to be present and nginx doesnt have chroot
???
To be honest, running a webserver without chroot in 2020 sounds
rather crazy.
In the design of man.cgi, Kristaps and myself did not even consider
supporting non-chroot setups. It may or may not work, but i don't
feel like spending time on considering whether it might work, or how.
Just use a chroot, as everybody else does, and be done with it,
i would say...
> I had to symlink my /var/www/man to /man (as a temporary work around).
>
> the folder /man contains a single file - manpath.conf with just a
> single line - system
>
> the /man/system directory contains man1/ man2/ ... folders with the
> man pages in them.
That sounds good as far as it goes.
Did you remember to do
# cd /var/www/man/
# makewhatis system
after copying the manual pages into the system/man1/ system/man2/ ...
directories?
> But when I go to http://localhost , while I can see the main page, clicking on
> any of the links man.cgi(8) or apropos(1) just shows the same page.
>
> Can anyone point out what I am missing.
>
> nginx.conf:
I fear i can't reasonably comment on nginx or fcgiwrap.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2020-12-10 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 0:06 Aisha Tammy
2020-12-10 13:46 ` Ingo Schwarze [this message]
2020-12-10 14:26 ` Aisha Tammy
2020-12-10 15:01 ` Ingo Schwarze
2020-12-10 15:26 ` Aisha Tammy
2020-12-10 15:26 ` Aisha Tammy
2020-12-16 3:28 ` Stephen Gregoratto
2020-12-16 4:51 ` Aisha Tammy
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=20201210134616.GF69368@athene.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mandoc.bsd.lv \
--cc=openbsd@aisha.cc \
/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 NNTP newsgroup(s).