this post was submitted on 28 Mar 2026
38 points (97.5% liked)

Selfhosted

56958 readers
1271 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
38
Do you prefer bare bones software that you customize with plugins, or an all-in-one solution that does everything you need out of the box? (lemmy.world)
submitted 8 hours ago by early_riser@lemmy.world to c/selfhosted@lemmy.world
12 comments fedilink hide all child comments
 

In my wiki roundup post I complained about DokuWiki's reliance on plugins, but after scouring the landscape of FOSS wiki offerings nothing else offers exactly what I need. So I settled on DokuWiki with a bunch of plugins. I have plugins for tagging pages, moving pages, blogging (which I use as a place to quickly catch ideas as they come to me before pushing them to the wiki proper), listing orphaned and wanted pages, among others.

The reason I initially disliked the idea of relying on plugins are that they may interfere with one another, interacting with the different plugins is inconsistent, and updating and management become more complex. But like I said, they get me what I need.

On the other hand, I've also been working with BookStack for another project. In many ways it's the opposite of DokuWiki. It looks modern, it has a noob-friendly wysiwyg editor (important when you need people of different technical skill levels to use it), and tries to be "batteries included" in the dev's words. The problem it's missing some features I consider essential for a wiki, chief of which is the ability to link to nonexistent pages. There isn't really a centralized way to manage uploads, either. And since it isn't extensible, you're stuck with those features unless the dev decides to add them later.

So I can see why people may prefer one approach over the other, but how about you?

you are viewing a single comment's thread
view the rest of the comments
[–] neidu3@sh.itjust.works 2 points 4 hours ago* (last edited 2 hours ago)

Barebones, usually. In general I prefer software that does only one thing and one thing well. Input or output to/from said software can be handled by other pieces software.

I'm a big fan of modular designs where you can swap out any layer with something else, provided that the data interchange is c9mpatible.

Lacking the above, I usually go for softwares with support for plugins/extensions.