[lug] Wiki server suggestions for small organization

[Jed S. Baer]

On Thu, 11 Mar 2021 15:06:11 -0700
Vince Dean wrote:

>   * The site should be easy for our team members to search and update.
>     Artists are not known for their tech skills.

How much tech burden can you hope for? Since you mentioned wiki, this
implies that you think they can at least get the hang of wiki markup. A
WYSISYG editor helps here, of course.

Also, do you have any in-house IT support? Are you (the association)
already providing some functions, such as e-mail? Or is everyone involved
just using personal e-mail and their home computerss?

My thought was dropping a Pi or something like that onto your network, and
running DokuWiki on it. But that requires you have a network at all. I'm
not sure what to read into, "don't want to own or maintain a public-facing
web server", because that implies to me a private server, somewhere, which
fits with your example of an in-house wiki.

I like DokuWiki because it's so simple to set up and administer. But you do
need to have a web server to run it on. Thus my question re. in-house IT
support. For my own purposes, I don't find it a burden to run Apache at
home, but I don't kid myself that my Apache config is properly hardened for
being accessible to the WWW at large. The ports are simply not open. Maybe
nginx or lighthttpd are easier to administer.

How do you expect your users to access this wiki, or whatever CMS type of
thing you set up?

Just using DokuWiki as an example, you can easily install it on a
shared-hosting environment somewhere, and set it up to require a logon to
access at all, IOW no public read access. Is that good enough for you? Will
you be storing any sensitive data within this repository?

-- 
All operating systems suck, but Linux just sucks less
 - Linus Torvalds