Selfhosted

57215 readers

620 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Which wiki software to host (lemmy.nocturnal.garden)

submitted 4 days ago by tofu@lemmy.nocturnal.garden to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

cross-posted from: https://lemmy.nocturnal.garden/post/552459

For a hobby of mine, there's an outdated lore wiki on Fandom. I dislike Fandom and would like to host an alternative. It's supposed to be accessible to all kinds of people.

I started with mediawiki as that's what Fandom and Wikipedia are using, so people would be familiar with page structures at least and maybe the editor.

It turned out to be a bit of a pain though. It only has unofficial container images, the documentation is outdated and (what I consider as) core functionality like WYSIWYG editor or simple infoboxes has to be added by extensions or templates. I'm in the process of setting it all up and wondering if it's worth it (and if I want to maintain it). There's so many wiki projects it's hard to keep track, what are y'all using for stuff that's used by larger communities and simple to use with close-to-default settings?

you are viewing a single comment's thread
view the rest of the comments

[–] tofu@lemmy.nocturnal.garden 5 points 4 days ago (1 children)

Need? No
Want? Yes

[–] vestigeofgreen@lemmy.dbzer0.com 3 points 4 days ago

I settled on mediawiki myself due to basically how trustworthy mediawiki and mediawiki skins look. I use https://github.com/CanastaWiki/Canasta-DockerCompose myself but the default includes caddy, which I just overrode in the docker compose override. I believe Canasta is mainly driven by someone who works on a wiki farm.

I also know of https://github.com/nasa/meza.

However, I want to repeat my recommendation of miraheze. When I run into an issue or need an extension, I just look at what miraheze does or what people associated with miraheze do. I also believe that due to the nature of mediawiki it's a better use of resources to have a wiki farm as opposed to many separate instances. If they will host your wiki, I think they're the best choice.