At the risk of taking this thread somewhat off-topic (sorry) but in the
broader context of answering the “what path” question:
On 2017-08-25 15:27, John MacFarlane wrote:
> The main reason both are languishing is that I have limited
> time to work on software, and since I don't actually use
> gitit any more for my own purposes, it's lower priority than
Having used and enjoyed gitit on previous projects, I'm currently
setting up some infrastructure for a new one … and am wondering which
wiki / free-form linked document management system to use for this new
set-up. My original plan was to use gitit again this time round.
Coupled with a certain amount of fiddle (not yet solved) getting a
working gitit up and running on Devuan Linux 2.0 / aarch64, though, the
above quote makes me think that it might be wise to look away from gitit
to some other solution.
What do you (or anyone else on the mailing list, for that matter!) use,
these days, in lieu of gitit, as the document and notes management tool
in your workflows?
Would be very interested to hear what people find works well, and indeed
what to avoid!
My requirements are essentially not great, and remain more-or-less as
they were when we switched from TWiki (via foswiki) to gitit on those
old projects: sensible wiki syntax (clearly markdown is fine, other
basic / standard wiki formatting markup also fine); ability to render
maths into MathML for the browser from some sane markup (e.g. LaTeX)
(either natively or using a plug-in); and ability to edit off-line and
resolve divergences and conflicts using standard tools (for example, and
ideally really, as with gitit, using git to maintain a local copy of the
document repository). Free software and the ability to run the server on
Linux-arm64 are also quite high on the priority list. Ideally, the
ability fairly straightforwardly to identify and authorise users using
information from their X.509 client certificates as presented to the
server (in my case I've previously done this via a reverse proxy in
apache, which places appropriate fields from the certificates into the
environment for gitit to use), would also be present.
Reading that back makes me think I should battle on with attempting to
get gitit up and running on my devuan 2.0 arm64 system, … but it is not
what I should really be spending my time on! Unfortunately, I don't
speak anything other than extremely basic Haskell, and am equally
unfamiliar with the tools (stack, cabal, …). That means that taking on
any meaningful level of maintenance or improvement work with gitit
myself is not a viable option at the moment (particularly given my wish
to avoid the need for substantial tooling work diverting me from the
grist of a project into playing with the tools supporting it, leading to
a loss of project momentum!).
All thoughts and ideas most welcome!