There are a ton of options listed on the Awesome Selfhosted list. I’m on the search for a FOSS option that I can use to document my homelab and personal tech projects.

Right now, I’m leaning towards wiki.js

  • Matt@lemdro.id
    link
    fedilink
    English
    arrow-up
    18
    ·
    10 months ago

    DokuWiki for simplicity. Everything is a text file that can just be copied to a web server. It doesn’t even require a database. And since all the wiki pages are plaintext markdown files, they can still be easily accessed and read even when the server is down. This is great and why I use DokuWiki for my server documentation as well.

    • nimmo@lem.nimmog.uk
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months ago

      I was going to say that the big downside to that would be a lack of any kind of version control, but I guess if you need that you can always use git and just commit changes there and (optionally) push them to a repository somewhere.

  • m_randall@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    10 months ago

    I just spent a week evaluating all the popular choices to document an overlay network I’m standing up. All I want is a simple markdown interface to write notes in. My goal was something with a very simple UI, markdown, and very light weight.

    MediaWiki, Bookstack, and WikiJS (or JSWiki) were good but they were too much for what I needed. I ended up with stumbling on gollum and really like it. It’s very very simple, fast, and clean. I wrote a one line cronjob and now I’m backed up to gitlab.

    https://github.com/gollum/gollum

  • words_number@programming.dev
    link
    fedilink
    English
    arrow-up
    4
    ·
    10 months ago

    I’m administering a wiki.js instance. Despite it being written in node, it’s a pretty nice wiki with a lot of modern features builtin. The only other wiki I’ve ever setup and used was mediawiki, which is obviously a complete legacy php clusterfuck where you need add-ons (which are terrible to install and configure) for everything.

  • Morethanevil@lemmy.fedifriends.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    10 months ago

    I really like WikiJS but its development is stuck for a long time now. No v3 in sight… Sadly

    I am using latest v2 for now, but I am looking for alternatives. Pro for WikiJS: S3 Backend, easy to use, WYSIWYG-Editor

    Outline is a hell to selfhost, even if it starts, login via Email / Password is not enabled by default. You need to login with Github or similar… Never again

    This is my experience with wikis so far.

  • paddirn@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    10 months ago

    I’m probably the biggest simpleton in this thread, but I was just looking at this earlier and TiddlyWiki still seems like the easiest of the easiest. It’s literally just an html file that requires pretty minimal setup to get going. Nothing else seems to even come close. I’ve been using it for a couple of years as a sort of internal departmental job aid, just basic information for our group and it’s pretty straight-forward.

  • johntash@eviltoast.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    10 months ago

    Bookstack is really nice and user friendly. It’s probably one of my favorites.

    Dokuwiki is simple and stores files in plaintext.

    I haven’t used wiki.js much but I’ve heard good things about it too.

    Another option if you don’t need to share the wiki with anyone would be a note tool like Trilium. It has built in support for stuff like mermaid or excalidraw diagrams.

    Don’t forget to setup backups for whatever wiki you do go with, and make sure you can restore them when your wiki is broken ;)

    • 𝘋𝘪𝘳𝘬@lemmy.ml
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      2
      ·
      10 months ago

      You should switch to Forgejo, though. Gitea is owned and maintained by a for-profit corporation that recently decided that all non-Gitea copyright notices from all files have to be removed (which in the end allows relicensing it to a more restrictive license and even making it nonfree).

      The corporation taking over Gitea from the community was also a hostile takeover.

      https://forgejo.org/compare