48
submitted 1 year ago by [email protected] to c/[email protected]

I'm looking for a wiki solution (either remotely hosted or self-hosted is fine) that takes Markdown input.

Thanks.

top 42 comments
sorted by: hot top controversial new old
[-] [email protected] 13 points 1 year ago

Looks like wiki.js and BookStack both support Markdown.

[-] [email protected] 11 points 1 year ago

I'm a big fan of Bookstack. The Docker images work great, also in Kubernetes. SSO is easy to set up as well, so if you're using something like Authentik for SSO, you can integrate it pretty easily.

[-] [email protected] 3 points 1 year ago

I love Bookstack!

The diagram tool can be used to markup anything. Besides the obvious, I've also put pictures as the background and then marked up those to diagram out some work I was doing around the house.

I hope the dev makes his way over here, he was very active on Reddit.

[-] [email protected] 3 points 1 year ago

I researched using Bookstack but you can access the pictures even if you do not have an account and have the right URL, anybody can see the picture/attachment file in any browser.

Not having well-implemented access control was a big No No for us.

[-] [email protected] 8 points 1 year ago

Dokuwiki has a plugin that lets you use markdown instead of their proprietary markup.

[-] [email protected] 4 points 1 year ago

+1 Dokuwiki. It is a little complicated than most to configure the first time, but once you have everything running, it will work without complaints. Also, the whole wiki is stored as plain text files, which is awesome for backups.

[-] [email protected] 2 points 1 year ago

piling on for Dokuwiki. Have been running it personally and for an org (2 different wikis) for like 7 or 8 years. No problems, and it's own syntax is pretty easy too. I've migrated a few times too and love that it's just plain text files

[-] [email protected] 8 points 1 year ago

I'm currently hosting a wiki.js
you can either use markdown or a visual editor

[-] [email protected] 2 points 1 year ago

My only gripe with wiki.js was the use of SQL for local storage. My wiki must be future proof and locking myself in an obscure SQL database was the deal breaker. I know that you can sync with a Git repo, but it felt like an overkill.

[-] [email protected] 6 points 1 year ago

Obsidian is a fantastic note taking app that focuses on cross-linked notes, so is effectively a personal wiki.

It has a paid add on that lets you publish it to a website, or you can just do it yourself since the files are all Markdown.

[-] [email protected] 1 points 1 year ago
[-] [email protected] 6 points 1 year ago* (last edited 1 year ago)

Not sure if it's the kind of thing you had in mind, but I like TiddlyWiki for certain things like note-taking. (See here for saving/hosting options).

[-] [email protected] 6 points 1 year ago

You could always just use a github repo as a wiki. It would render markdown pages in your browser, and it comes with built in version control!

[-] [email protected] 1 points 1 year ago

You can also use Gitea/Forgejo, since it's selfhostable and FOSS, or GitLab CE.

[-] [email protected] 5 points 1 year ago
[-] [email protected] 0 points 1 year ago

I switched from Tiddlywiki to Logseq 3-4 months ago and LOVE Logseq.

Part of the reason I didn't like Tiddlywiki was it kept everything in a single html file (including embedded images -- eww) which made it annoying to move information around. (Note there is an option to run your own server which gives you extra flexibility, but I wasn't interested in doing that.)

With Logseq, it's separate markdown file per journal entry / wiki page. I like the addons that are available as well as the queries, e.g., {{query (todo doing)}} displays my do now tasks on my journal page.

Here's a Beginner's Guide on how to use LogSeq: YouTube video by Keep Productive

[-] [email protected] 0 points 1 year ago

Aren't you worried that Logseq doesn't use "pure" Markdown?

[-] [email protected] 1 points 1 year ago

Good that you mentioned that. Personally, I think it's a fair trade off for Logseq's functionality.

Here are some links that discuss this including some scripts

[-] [email protected] 5 points 1 year ago

wikijs comes to mind, it's deploy-able with a single docker command:

docker run -d \
--name=wikijs \
--restart=unless-stopped \
--publish 8080:3000 \
--env "DB_TYPE=sqlite" \
--env "DB_FILEPATH=/wiki/db.sqlite" \
--volume wikijs:/wiki \
--volume wikijs:/wiki/data/content \
ghcr.io/requarks/wiki:2
[-] [email protected] 2 points 1 year ago

@Smash @firebreathingbunny I'm also quiet happy with wikijs, it has some nice features like git integration and oidc support that I'm using.

[-] [email protected] 2 points 1 year ago* (last edited 1 year ago)

I also self-host WikiJS and am quite happy with it. FYI though if you're setting it up I'd instead configure it to use Postgres as the database, as I recall reading that they're planning on removing SQLite support at some point. Unfortunately though that does mean you lose a one-liner like this.

[-] [email protected] 1 points 1 year ago

Okay, thanks for the heads up! I don't actively use wikijs yet, I'll setup a stack using postgres when I do

[-] [email protected] 4 points 1 year ago* (last edited 1 year ago)

I use Silicon Notes; While it has 'Notes' in the title, it's just a lightweight markdown based wiki

[-] [email protected] 2 points 1 year ago

Can recommend this one: like it very much

[-] [email protected] 4 points 1 year ago

I'll piggyback on this post in that I'm looking for a good ObsidianMD -> self-hosted wiki solution.

[-] [email protected] 1 points 1 year ago
[-] [email protected] 4 points 1 year ago

gollum is self-hosted and uses markdown by default

[-] [email protected] 3 points 1 year ago
[-] [email protected] 2 points 1 year ago

It’s not selfhosted.

[-] [email protected] 2 points 1 year ago* (last edited 4 months ago)

Try mdBook if you’re a rust person!

https://rust-lang.github.io/mdBook/

[-] [email protected] 2 points 1 year ago

I personally use Grav. It's fully markdown bases and store the content in markdown files as well, instead of a database.
The Learn2 theme is the one for a documentation-style look. Check out the official documentation for how it looks and here's my own customized version.

[-] [email protected] 2 points 1 year ago

I think you should specify whether you're looking for a wiki for personal use or shared use.

If you're looking for personal use, something like standard notes can be a great option.

If you're looking for shared use, and don't care about encryption, wiki.js is IMO your best bet.

There's currently no option that does both. Skiff exists as an encrypted collaborative notes option but it doesn't (to my knowledge) allow any kind of self hosting.

[-] [email protected] 2 points 1 year ago
[-] [email protected] 1 points 1 year ago

Oh cool, I thought Raneto was dead.

[-] [email protected] 1 points 1 year ago

I'm really liking mkdocs-material. Crazy lightweight. Very safe. And it looks nice.
https://squidfunk.github.io/mkdocs-material/

[-] [email protected] 1 points 1 year ago

I stopped using it because it wasn't the best for the use case I was looking for but I'll plug SilverBullet. It is a well made program and seems very powerful from what I've seen

[-] [email protected] 1 points 1 year ago

We use wiki.js at work and it is great. A nice benefit is you can track your articles in a git repository for granular change tracking.

[-] [email protected] 1 points 1 year ago

Not sure about your use case, but check out HackMD.

[-] [email protected] 1 points 1 year ago

nb is a command line and local web note‑taking, bookmarking, archiving, and knowledge base application.

load more comments
view more: next ›
this post was submitted on 17 Jun 2023
48 points (98.0% liked)

Selfhosted

37923 readers
443 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.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS