G'day marto,

Many thanks for your suggestions. Some of these have already been looked into. Here's a brief summary of those.

• Work on creating a local CPAN mirror was started quite some time ago (before I joined the company). It ran into various difficulties and was never fully operational. Fixing (or finding an alternative to) this is part of my current task. For now, I've put this into the overkill bucket; although, that doesn't preclude revisiting at some future point.
• My current research looked into the option of using MetaCPAN locally; I did encounter Docker which you mentioned. While not entirely abandoned, I felt this also fell into the overkill bucket.
• I had looked at both CPAN::Mini::Webserver and minicpan_webserver. The latter does have more documentation; although, how to achieve various tasks is not shown. As an example, it uses static CSS, via CPAN::Mini::Webserver::Templates::CSS: I imagine there would be some way to either tweak what that provides, or to specify a completely different style sheet, but there is no information on how to do that.
  Compare with Pod::Html (and, by extension, pod2html) which has a fairly straightforward --css=stylesheet option. CPAN::Mini::Webserver uses Moose but I can't see any obvious 'has css' statements; the code is fairly long, and includes a number of use and extends statements, so I imagine I will eventually be able to find what I need — it's just annoying that I need to do this at all.

Thanks for pointing me towards App::lcpan [for anyone else reading this, that's a lowercase case 'L', not an uppercase 'i']. I've had a brief look at this but will need to spend more time on it. There does appear to be a lot of documentation, especially in App::lcpan::Manual; at present, a lot of that is just "TODO" but the author (fellow monk, perlancar) appears to be working on that at the moment — I see four distribution updates in the last three days.

Overall, there's nothing currently set in stone. I'll be starting a proof-of-concept tomorrow using the DarkPAN solution outlined in the OP — of course, that may change as work progresses. Given tomorrow is only a few minutes away in my timezone, I should probably get some sleep first. :-)

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.