Selfhosted
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!
view the rest of the comments
I use Dokuwiki for my small fantasy wiki project. I use many plugins to achieve the functionality and style that I want, but it works well for my needs. None of the others I looked at could do quite everything I wanted.
I'm currently migrating my worldbuilding and conlanging project to Dokuwiki. Right now I have an Obsidian vault used for brainstorming and drafting and a public Mediawiki for stuff I feel is worth showing off. Like Obsidian, DW stores everything as plaintext (it's not markdown but it's readable and the tables are better IMO). Like Mediawiki, DW keeps a version history so I can keep track of how my ideas evolve over time, which is crucial for conlang documentation. I keep tons of example texts that may reflect earlier phases of the grammar and vocab that I may need to reference. Unlike both Obsidian and MW, Dokuwiki has access control, so I can keep a private namespace for drafts and a public namespace for stuff I think is polished enough to show.
I'm not sure DW meet's OP's requirements for "out of the box" functionality though. I think it's intended to be rather bare bones but be very easy to extend with plugins. The plugin browser is built in, so customization is a breeze. Plugins can be individually installed, enabled, disabled, and updated through the admin GUI.
If you wouldn't mind sharing, I'd love to take a gander at what you're cooking up!
The DW instance isn't public (yet) but here's a link to the currently public mediawiki instance.
https://constructed.world/
I never invested the time to make the content very discoverable, so you'll have to make copious use of the random page and what links here features if you want to see what I've written.
Enjoy my stress-induced maladaptive daydreams.
Thanks for sharing! I don't have a ton of experience with MediaWiki and cannot figure out how to go to a random page lol
It's behind the hamburger menu (3 horizontal lines on the top left of the page), at least with the latest default skin. You can also check out a list of all pages by searching
Special:AllPages, and a list of all categories withspecial:categoriesThe categories will in turn take you to lists of pages tagged with that category. It's great for going on wiki walks.If I haven't scared you away with my nonsense, the DW instance is now public. The link I provided earlier should point to the new server. https://constructed.world/
Not at all! I did poke around some random pages after you helped me, sorry I didn't come back to my. Thanks for sharing the update, I'm keen to see how you're using DW.
Judging by how productive I've been just in the last 8 hours, I'd say going from Mediawiki to Dokuwiki was a good choice. I'm not even sure why. DW still uses markup instead of a WYSIWYG editor, which I'm fine with. I think it's the namespaces. MW does have them, but you have to set them up with a config file on the server, and adding and removing them cannot be done lightly. With DW it's as easy as searching for
new_namespace:some_new_article, and the namespace is created along with the article. So I have a scratchpad namespace where I can work on drafts, a stories namespace to put my attempts at creative writing, a lore namespace for, well, canonized lore tidbits, and so on. And I don't need to worry about names colliding like I did with MW where lore articles and story titles often conflicted.DW lets you use hierarchy when it works, and loose categories (tags) when it doesn't (with the tags plugin that is). With MW you just have categories but no hierarchy. Bookstack is the opposite. It forces you to use its shelf>book>chapter>page organization system. It does have tags, too, but you can't have pages outside of books, and the pages have an explicit order. You can fairly easily change that order, but it's always there.
Back to DokuWiki, the blog plugin has proven invaluable over the last few days. I can jot down ideas as blog entries and push them to the main lore namespace if I think they're worth keeping.
How did you approach finding the proper plugins?
I considered functions that I wanted (for example, tags) and looked to see if there was a plugin that did what I wanted. Dokuwiki's plugin browser was very useful for this.