17 ms·

Wiki.js

381 points by akandiah 6y ago

amq 6y ago
I was looking into open source knowledge / wiki base solutions recently, and I found https://www.getoutline.com/ https://www.getoutline.com/ to be the most usable.
- Vaslo 6y ago
  10 bucks a month though...
  - vladvasiliu 6y ago
    For the hosted version. You can host your own for free: https://github.com/outline/outline https://github.com/outline/outline
    - FalconSensei 6y ago
      then you have to pay your host
captn3m0 6y ago
I've used the 1.x release, and the Mongo requirement was always a bit of a pin. I think v2 fixes that, but I haven't yet upgraded. Anyone has feedback on v1 vs v2?
- progval 6y ago
  Looks like they stopped using MongoDB: https://blog.requarks.io/the-switch-to-rdbms/ https://blog.requarks.io/the-switch-to-rdbms/
load 6y ago
If it doesn't run on MediaWiki, I'm not into it.
- wutwutwutwut 6y ago
  Why?
  - load 6y ago
    I mean, I appreciate the effort put into building this, but external tools like AWB, and userscripts/gadgets (plus a host of other goodies) can't be accessed over globally if it's on a completely different software. Almost every wiki on the net uses MediaWiki for good reason. I will be happy if this Wiki.js platform does have compatibility with these features, though.
    - eitland 6y ago
      > Almost every wiki on the net uses MediaWiki for good reason. It is unclear to ne if you refer to statistics or gut feeling here. Would you mind clarifying?
      - iamacyborg 6y ago
        Stats, clearly.
      - load 6y ago
        By 'MediaWiki' I'm referring to the wikis and wiki farms that use MediaWiki or a variant of it. This includes: - Wikimedia - FANDOM - Gamepedia - Miraheze FANDOM is the most massive wiki farm with over 360,000+ (as of 2016) wikis[1], which I'd give at lowest an estimate of 60% of the total number of wikis on the net, and is 88th on the Alexa rankings.[2] FANDOM is a wiki powerhouse, and you bet it uses MediaWiki. Excluding WikiHow, I have never seen a wiki not use MediaWiki. As one of the guys that hops across many different wikis and wiki farms doing automated work, I cannot stress this enough. [1] Brandon Rhea, FANDOM VP of Growth https://community.fandom.com/wiki/Choosing_Fandom?diff=next&oldid=1742190 https://community.fandom.com/wiki/Choosing_Fandom?diff=next&... (dated June 14, 2016) [2] Alexa.com https://www.alexa.com/siteinfo/fandom.com#section_traffic https://www.alexa.com/siteinfo/fandom.com#section_traffic (dated ~21 July 2020)
w-ll 6y ago
I'd atleast expect a demo, and the homepage to be running on said wiki.
- bauerd 6y ago
  There's a link to a demo in their README: https://docs.requarks.io/demo https://docs.requarks.io/demo
  - edaemon 6y ago
    Their demo link there didn't work when I tried it, it's looking for the non-existent master branch. The docs site itself (https://docs.requarks.io/ https://docs.requarks.io/) is running on Wiki.js, though.
- deleted 6y ago
  [deleted]
dvno42 6y ago
I've been using 2.x since Jan and have really liked it. I'm using it in docker with postgres iirc for a small team for infrastructure documentation. Very markdown friendly and gets the job done while looking nice.
Hamcha 6y ago
docs.requarks.io, which is said to be using Wiki.js, straight up doesn't load without Javascript, and even with Javascript enabled it's a multi-page application that just feels slower browsing page to page than your average 10-year-old mediawiki install (probably also heavier on the backend). Who exactly is asking for slower software?
- mainframed 6y ago
  Was excited about seeing an open alternative to Gitbook. But yes, not loading without Javascript is a showstopper.
- midasz 6y ago
  > Wiki.js, straight up doesn't load without Javascript I'm sorry but it's right there in the name
  - Hamcha 6y ago
    Because it uses Node.js in the backend. MediaWiki is written in PHP, but it does not require you to have PHP running in the client to work. As much as we could argue about whether no-js support really matters or not in 2020, the fact remains that having to having to load Vue.js and have it parse and render the frontend on the client is not really "lightweight", especially when the most popular competing products pre-render on the backend. It wouldn't honestly be that much of an issue if it was a SPA (and it must do SPA-ish things already if it uses Apollo) so you just load the frontend once and it'd load other pages asynchronously, but nope. Every link is a full page reload, with Vue having to re-do everything every time. It just reeks of modern tech used in an old fashioned way, which ends up with the performance penalties from both. Go browse any other wiki, see how much faster and smoother the experience is.
    - merb 6y ago
      well sometimes not being a spa and using vuejs/"any spa tech" might be a good idea. if it would be scoped correctly. sometimes you need MORE interaction on a specific page. unfortunatly the whole wiki feels sluggish as you already said, because they make so much dumb stuff. I would say using js without having a no-js version is ok, if done correctly.
jadia 6y ago
I started using Wiki.js over a year ago to maintain documentation related to system admin duties. We run this in a docker container with SQLite database and backup the database daily to another server. The private and public pages feature fits perfectly to our use case. We show system information, how-to guides and rules on the public pages and manage sysadmin documentation with restricted access.
schoolornot 6y ago
This is exciting. A compelling FOSS alternative to Atlassian Confluence was sorely needed. Mediawiki has some UX and RBAC challenges that makes it difficult to scale to large organizations.
- oneplane 6y ago
  Since it's AGPL it will probably never end up in the same commercial use cases as Confluence does. Google has some motivations written down from their lawyer department: https://opensource.google/docs/using/agpl-policy/ https://opensource.google/docs/using/agpl-policy/ It boils down to 'not worth the risk, do not use'.
  - bachmeier 6y ago
    That's not relevant for using wiki.js.
  - edp 6y ago
    OT, as the sole copyright owner of a web application I wrote, can I license it under the AGPL for the general public, and license it under different terms for clients who would prefer not to use AGPL software (and possibly pay for it) ? is dual licensing allowed by the AGPL ?
    - tkfu 6y ago
      If you're the sole copyright owner, you can offer as many different licenses as you want, and no copyleft license can interfere with that.
    - dualscyther 6y ago
      Yes, you can licence it however you want because you are the copyright holder. See mongodb. IANAL. Licences are to restrict those who do not hold copyright.
      - teddyh 6y ago
        > Licences are to restrict those who do not hold copyright. On the contrary, licenses gives permission to those who do not hold copyright. Without any license, only the copyright holder has any rights to copy or modify the work in any way (except for fair use). A license gives permissions to non-copyright holders to do things which would otherwise be illegal under copyright law. A license can never restrict what anyone would otherwise be allowed to do, since it is not a contract.
gwbrooks 6y ago
I keep a v2 instance running on my Windows laptop solely for taking notes and keeping need-it-eventually information organized. It's just enough added structure and functionality to make the whole body of notes more useful, without having to learn a formal system or adopt someone else's idea of what my note hierarchy should look like.
Keyframe 6y ago
I need one function in a wiki platform that I haven't seen so far. When I write text, in its WYSIWYG editor, I need an ability to paste in an image (a screenshot that I just grabbed, let's say) and for it to automatically upload it and embed it into text. Does this support something like that?
- reacharavindh 6y ago
  This. Thousand times this. I have been waiting for an online wiki with the usability of Apple Notes that I use locally on all my Apple devices. It works like a charm except that I cannot make it public. This is why I often take notes rather than write blog posts on my website. If the wiki software was as easy drag and drop as Apple Notes, I’d just take notes and they turn into publicly available wikis! I am yet to find that tool. I would happily pay for such a tool with one braking condition that it must be self-hostable. I will not write my content into something like Medium or Notion where I don’t own my content.
  - snickmy 6y ago
    This is technically feasible. The latest html5 api (quite well adopted) allow copy paste from the OS and drag and drop. There is quite a bit of server side / javascript to implement, but it is feasible.
  - jve 6y ago
    This seems like it: ImgPaste plugin for DokuWiki https://www.dokuwiki.org/plugin:imgpaste https://www.dokuwiki.org/plugin:imgpaste https://github.com/cosmocode/dokuwiki-plugin-imgpaste https://github.com/cosmocode/dokuwiki-plugin-imgpaste
  - motiejus 6y ago
    I will announce something like this soon: - ui: joplin. - agpl, fully self-hostable. - you own your content (because joplin). - choose among free templates, or create your own. - templates will be similar or compatible to hugo, still tbd. Optional for paying customers: - sync via webdav to my service. - custom domain. - backups, etc. Once this starts generating money, I am planning to spend some of it to fund e2e per-folder encryption in joplin.
oneplane 6y ago
I wonder why it's AGPL and not dual-licensed or some different GPL. As it is right now it's dead in the water for any commercial usage unless you're manually installing the thing on a manually installed server somewhere (which you probably aren't). With automation you'd build images based on their images but run via your own CI/CD with your own security scans and any additions you might need (like additional logging infrastructure). Doing that is not possible with AGPL.
- deleted 6y ago
  [deleted]
- normalnorm 6y ago
  > As it is right now it's dead in the water for any commercial usage So what? If companies need a certain software, they can pay for it. I remember a time when FOSS was not about providing companies with free work, quite the opposite indeed.
  - oneplane 6y ago
    It is presented as being enterprise-ish, for organisations (of which a lot are commercial) and presents features usually useful for large companies. That's what. This isn't about good/bad or something like that, just an odd presentation that doesn't seem to be in line with the license. There is nobody to pay here to use this stuff because you still won't be able to integrate it without also sharing internal IP. There are plenty of organisations that would happily pay what they'd normally pay Atlassian to use Wiki.js but they can't because they don't want to share any of their own code. This is also why license guides like the one from google explicitly bans all AGPL software because it's not worth the risk.
    - fungos 6y ago
      These company make changes to Atlassian code? You're conflating internal or public use with derivative work or service offering. You clearly misunderstand licensing.
    - 6y ago
hombre_fatal 6y ago
Slightly related PSA: Everyone should consider running a wiki locally just for yourself. It's like being able to organize your brain. I just got into it two days ago and basically spent the whole weekend dumping things into it in a way I can actually browse and revisit, like the short stories I'd written, spread out across Notes.app and random folders. You don't need to run WAMP, MySQL, Apache, phpmyadmin or anything. Here are the steps for someone, like me, who hadn't checked in a while: 0. `$ brew install php` (or equiv for your OS) 1. Download the wiki folder and `cd` into it 2. `$ php -S localhost:3000` 3. Visit http://localhost:3000/install.php http://localhost:3000/install.php in your browser I tried DokuWiki at first (has flat file db which is cool). It's simpler, but I ended up going with MediaWiki which is more powerful, and aside from Wikipedia using it, I noticed most big wikis I use also use it (https://en.uesp.net/wiki/Main_Page https://en.uesp.net/wiki/Main_Page). MediaWiki lets you choose Sqlite as an option, so I have one big wiki/ folder sitting in my Dropbox folder symlinked into my iCloud folder and local fs. Really changing my life right now. The problem with most apps is that they just become append-only dumping grounds where your only organizational power is to, what, create yet another tag? My advice is to just look for the text files scattered around your computer and note-taking apps and move them into wiki pages. As you make progress, you will notice natural categories/namespaces emerging. I just wish I started 10 years ago.
- jcelerier 6y ago
  > I tried DokuWiki at first (has flat file db which is cool). It's simpler, but I ended up going with MediaWiki which is more powerful, and aside from Wikipedia using it, I noticed most big wikis I use also use it (https://en.uesp.net/wiki/Main_Page https://en.uesp.net/wiki/Main_Page). MediaWiki lets you choose Sqlite as an option, so I have one big wiki/ folder sitting in my Dropbox folder symlinked into my iCloud folder and local fs. or you can just use Zim which is a cross-platform desktop app which does not need any setup and simply save files as text files in markdown : https://zim-wiki.org https://zim-wiki.org
  - hombre_fatal 6y ago
    There definitely are a lot of options to check out (one of the reasons I went with MediaWiki). I recommend playing with them to get a feel for where they diverge from one another. You may find features in some that you decide are necessary for you that a marketing list of bullet points can't get across.
tweetle_beetle 6y ago
I'm looking to launch an internal wiki and Wiki.js came out on top for my requirements: - easy to use for technical and non-technical staff alike: multiple editing options - third party authentication: really comprehensive offering - quality search: comprehensive internal and third party search offering - ease of maintenance: largely everything is built-in, so no module/dependency maintenance headaches - user management: solid user/group management system With internal tools you need things to stick, and fast. As much as I am fond of mediawiki, the editing experience is a barrier to usage for many. And the extension ecosystem, while rich and diverse, is just more of a liability than a single installation. A quality search is also really important to adoption, so having options there is great. I'd been using Docsify on a small scale with authentication through GitLab to edit, GitLab CD to build and Cloudflare Access to secure the front end. It works really well, but the lack of user management and the editing experience mean that it's time to move on. It would be great to hear if this is a case of the grass always being greener on the other side.
mard 6y ago
I'm not impressed. Wiki.js is supposedly "built with performance in mind", but its documentation wiki [1] is much slower than any DokuWiki site I could find [2]. It also requires JavaScript to be enabled in the web browser. [1]: https://docs.requarks.io/ https://docs.requarks.io/ [2]: https://www.dokuwiki.org/ https://www.dokuwiki.org/
- a012 6y ago
  I also don't like their theme choice, especially the "Table of Contents" is fixed and wasteful, and combined with navigation column they used 40% of the screen wide. I can't concentrate to the content because the other half is distracting.
- Rotten194 6y ago
  I find it really frustrating that every piece of software nowadays claims to be "blazing fast" or "built for performance", usually with no benchmarks to back it up. Makes it really hard to tell at a glance what the strengths of a project actually are. I honestly would be very grateful if a project up and said "we're not the fastest, but we trade performance for a simpler codebase and easier extensibility. If you need to do some-performance-intensive-task, try other-package instead".
techaddict009 6y ago
Can I know what exactly this numbers are "15M+ Installations" On your home page. I mean thats too large number. Is this of all open source software or I am misunderstanding something else?
- jjice 6y ago
  I'm assuming that's for every single download, including testing. I know that when I use a service for the first time, I do a few installs while getting used to the software and its configuration. I'd assume they'd have no other way to verify installs (assuming there is no telemetry).
favadi 6y ago
For personal wiki, nothing beats the simplicity of tiddlywiki.
yreg 6y ago
Wikis are also useful for note-taking, I'm using Wiki.js to document a D&D campaign to have some canonical reference of what actually happened in past sessions.
- pspeter3 6y ago
  Why did you pick Wiki.js for campaign management as opposed to something like Notion?
  - jdironman 6y ago
    Big fan of Notion here for both documentation, task management, and general brain dumps. Only worry I have is one day they go away and I have to migrate off how much of a pain that would probably be. It feels locked in, maybe i am wrong
- zcdziura 6y ago
  Same here, it's been a great asset to have available to document stuff in my homebrew world and have it reference other stuff. Being able to link my wiki out to my players for their own use is very handy.
aerojoe23 6y ago
We needed a documentation solution at work. MY coworker had some experience with Wiki.js. What sold me on it was that you can use markdown and it can keep itself synced with a git repo. This gives us plan text files that are tracked in a repo. It uses the user as the author, so now I can "code review" edit's to our wiki. The content of the wiki is easily cloned by cloning the git repo. It is markdown in folders so if wiki.js dies at some point I could write a pandoc script to turn it into web pages again, you do loose all of the cool UI features.
lukaszkups 6y ago
Is it possible to output static-file-based wiki? (so some static HTML/CSS/js ?)
ddevault 6y ago
Can we please not have SPA's eat wikis, too? Text-only content does not need... (checking...) 6.3 MB of JavaScript to display (checking...) 3.3 KB of text. Blank pages with JavaScript disabled or in non-mainstream browsers is a really terrible experience for content so plainly simple to display.
- cxr 6y ago
  Wikis also don't need (or indeed, even permit) cumbersome Git and PR-based workflows just to get changes into the "wiki". Better for it to be a single-page app that actually implements a wiki, than to provide a service that doesn't actually support wikis but has no qualms about throwing the word around anyway.
heresie-dabord 6y ago
I used a Wiki for a long time. But I try to minimise maintenance ("foist it upon others"). I also try to resist the enthusiasm for Rube Goldberg machines and for installing bad tooling (such as PHP). Now that git has become ubiquitous, I prefer git with a self-hosted git-daemon instance. git , grep , awk , and sqlite make a strong set of tools for knowledge curation. edit: minor grammar fix
- ArtDev 6y ago
  Unnecessarily bashing PHP is soo 2005. Like javascript, it can be written poorly due to its loose roots. Also just like javascript, it is a very different language now. That said, DocuWiki is pretty decent to get up and running quickly.
  - john-shaffer 6y ago
    I use PHP in my day job. It is by far the worst language I've ever used. Nothing else even comes close. The language and ecosystem are so full of footguns that you are bound to shoot yourself eventually. The OpenSSL implementation will silently truncate the key [1][2] without even giving a warning. The cURL lib, in 2020, still hasn't implemented a get_curl_opt function. Sure you could wrap it if you're writing everything, but the reality is I have to work in this nightmare ecosystem that just uses raw curl. Every == comparison is still a potential security hole due to PHP's insane (and inconsistent) typecasting behaviors. Sometimes a number gets cast to a string, but a string gets cast to a number if you use it as an array key. WTF? Do I have to wait another 15 years for PHP to become a halfway decent language? [1] https://github.com/WP2Static/wp2static/pull/506 https://github.com/WP2Static/wp2static/pull/506 [2] https://stackoverflow.com/questions/55062897/decrypt-aes256-on-python-vs-php/55063033#55063033 https://stackoverflow.com/questions/55062897/decrypt-aes256-...
    - heresie-dabord 6y ago
      > The language and ecosystem are so full of footguns "footgun" is an excellent term. Here's an earlier use on HN, 2010: https://news.ycombinator.com/item?id=1904960 https://news.ycombinator.com/item?id=1904960
amelius 6y ago
Why is there a Linux Tux logo next to macOS?
- mbrd 6y ago
  They are separate items in the horizontal list: https://wiki.js.org/img/linux.3297c180.svg https://wiki.js.org/img/linux.3297c180.svg https://wiki.js.org/img/macos.96f6d85a.svg https://wiki.js.org/img/macos.96f6d85a.svg
Nuzzerino 6y ago
I've been using Wiki.js for several months now on a production project (self hosted). It has worked nearly flawlessly for me so far. No complaints. Setup was a piece of cake too.
dheera 6y ago
Just a minor nitpick. If there isn't an actual file called "wiki.js" that is self-contained, I would prefer it be called WikiJS instead of "Wiki.js" to avoid confusion. In general when I see ".js" I expect to see a single file I can import that does something useful to my code.
Marioheld 6y ago
Does anyone has a comparison to Bookstack?www.bookstackapp.com
amelius 6y ago
In case anyone was wondering, the dependencies are: Node.js 10.12 or later MySQL, MariaDB, PostgreSQL, MSSQL or SQLite3 Is it possible to install and run all of these as a non-root user?
- xcambar 6y ago
  Absolutely. For Node, check nvm : https://github.com/nvm-sh/nvm https://github.com/nvm-sh/nvm And choose SQLite.
- acoard 6y ago
  Even better, you can run these in Docker as non-root. Security wise, while this wouldn't make your app itself more secure, it would insulate your host OS from getting infected. I just checked and they even have one-liner Docker commands that do just this: docker run -d -p 8080:3000 --name wiki --restart unless-stopped -e "DB_TYPE=postgres" -e "DB_HOST=db" -e "DB_PORT=5432" -e "DB_USER=wikijs" -e "DB_PASS=wikijsrocks" -e "DB_NAME=wiki" requarks/wiki:2
- Reubend 6y ago
  I think you only need 1 DB, not all of them.
deleted 6y ago
[deleted]
kontxt 6y ago
Kontxt (https://kontxt.io https://kontxt.io) could be a perfect inline communication and engagement layer to enhance wikis and docs with inline highlights, comments, polls, @mentions, page navigation, shareable deep links, and permission-based sharing.
- emiliovesprini 6y ago
  Did... did kontxt.io write this? Oh wait yeah.
  - kontxt 6y ago
    Hello emiliovesprini! You are correct. That's actually why the username "kontxt" was specifically selected. Decided to share here because people exploring the wiki and documentation space might find it useful. Best regards fellow code creator.
cptskippy 6y ago
I like the way the documentation is laid out, does that conform to a standard?
kinganurag 6y ago
i love this platform, i will suggest this to all my friends and clients :)
bobbydreamer 6y ago
Like the common theme all this wiki and outline are having 3 pane window any for Bootstrap it.

381 points by akandiah 6y ago

amq 6y ago

I was looking into open source knowledge / wiki base solutions recently, and I found https://www.getoutline.com/ https://www.getoutline.com/ to be the most usable.

Vaslo 6y ago
10 bucks a month though...
- vladvasiliu 6y ago
  For the hosted version. You can host your own for free: https://github.com/outline/outline https://github.com/outline/outline
  - FalconSensei 6y ago
    then you have to pay your host

captn3m0 6y ago

I've used the 1.x release, and the Mongo requirement was always a bit of a pin. I think v2 fixes that, but I haven't yet upgraded. Anyone has feedback on v1 vs v2?

progval 6y ago
Looks like they stopped using MongoDB: https://blog.requarks.io/the-switch-to-rdbms/ https://blog.requarks.io/the-switch-to-rdbms/

load 6y ago

If it doesn't run on MediaWiki, I'm not into it.

wutwutwutwut 6y ago
Why?
- load 6y ago
  I mean, I appreciate the effort put into building this, but external tools like AWB, and userscripts/gadgets (plus a host of other goodies) can't be accessed over globally if it's on a completely different software. Almost every wiki on the net uses MediaWiki for good reason. I will be happy if this Wiki.js platform does have compatibility with these features, though.
  - eitland 6y ago
    > Almost every wiki on the net uses MediaWiki for good reason. It is unclear to ne if you refer to statistics or gut feeling here. Would you mind clarifying?
    - iamacyborg 6y ago
      Stats, clearly.
    - load 6y ago
      By 'MediaWiki' I'm referring to the wikis and wiki farms that use MediaWiki or a variant of it. This includes: - Wikimedia - FANDOM - Gamepedia - Miraheze FANDOM is the most massive wiki farm with over 360,000+ (as of 2016) wikis[1], which I'd give at lowest an estimate of 60% of the total number of wikis on the net, and is 88th on the Alexa rankings.[2] FANDOM is a wiki powerhouse, and you bet it uses MediaWiki. Excluding WikiHow, I have never seen a wiki not use MediaWiki. As one of the guys that hops across many different wikis and wiki farms doing automated work, I cannot stress this enough. [1] Brandon Rhea, FANDOM VP of Growth https://community.fandom.com/wiki/Choosing_Fandom?diff=next&oldid=1742190 https://community.fandom.com/wiki/Choosing_Fandom?diff=next&... (dated June 14, 2016) [2] Alexa.com https://www.alexa.com/siteinfo/fandom.com#section_traffic https://www.alexa.com/siteinfo/fandom.com#section_traffic (dated ~21 July 2020)

w-ll 6y ago

I'd atleast expect a demo, and the homepage to be running on said wiki.

bauerd 6y ago
There's a link to a demo in their README: https://docs.requarks.io/demo https://docs.requarks.io/demo
- edaemon 6y ago
  Their demo link there didn't work when I tried it, it's looking for the non-existent master branch. The docs site itself (https://docs.requarks.io/ https://docs.requarks.io/) is running on Wiki.js, though.
deleted 6y ago
[deleted]

dvno42 6y ago

I've been using 2.x since Jan and have really liked it. I'm using it in docker with postgres iirc for a small team for infrastructure documentation. Very markdown friendly and gets the job done while looking nice.

Hamcha 6y ago

docs.requarks.io, which is said to be using Wiki.js, straight up doesn't load without Javascript, and even with Javascript enabled it's a multi-page application that just feels slower browsing page to page than your average 10-year-old mediawiki install (probably also heavier on the backend). Who exactly is asking for slower software?

mainframed 6y ago
Was excited about seeing an open alternative to Gitbook. But yes, not loading without Javascript is a showstopper.
midasz 6y ago
> Wiki.js, straight up doesn't load without Javascript I'm sorry but it's right there in the name
- Hamcha 6y ago
  Because it uses Node.js in the backend. MediaWiki is written in PHP, but it does not require you to have PHP running in the client to work. As much as we could argue about whether no-js support really matters or not in 2020, the fact remains that having to having to load Vue.js and have it parse and render the frontend on the client is not really "lightweight", especially when the most popular competing products pre-render on the backend. It wouldn't honestly be that much of an issue if it was a SPA (and it must do SPA-ish things already if it uses Apollo) so you just load the frontend once and it'd load other pages asynchronously, but nope. Every link is a full page reload, with Vue having to re-do everything every time. It just reeks of modern tech used in an old fashioned way, which ends up with the performance penalties from both. Go browse any other wiki, see how much faster and smoother the experience is.
  - merb 6y ago
    well sometimes not being a spa and using vuejs/"any spa tech" might be a good idea. if it would be scoped correctly. sometimes you need MORE interaction on a specific page. unfortunatly the whole wiki feels sluggish as you already said, because they make so much dumb stuff. I would say using js without having a no-js version is ok, if done correctly.

jadia 6y ago

I started using Wiki.js over a year ago to maintain documentation related to system admin duties. We run this in a docker container with SQLite database and backup the database daily to another server. The private and public pages feature fits perfectly to our use case. We show system information, how-to guides and rules on the public pages and manage sysadmin documentation with restricted access.

schoolornot 6y ago

This is exciting. A compelling FOSS alternative to Atlassian Confluence was sorely needed. Mediawiki has some UX and RBAC challenges that makes it difficult to scale to large organizations.

oneplane 6y ago
Since it's AGPL it will probably never end up in the same commercial use cases as Confluence does. Google has some motivations written down from their lawyer department: https://opensource.google/docs/using/agpl-policy/ https://opensource.google/docs/using/agpl-policy/ It boils down to 'not worth the risk, do not use'.
- bachmeier 6y ago
  That's not relevant for using wiki.js.
- edp 6y ago
  OT, as the sole copyright owner of a web application I wrote, can I license it under the AGPL for the general public, and license it under different terms for clients who would prefer not to use AGPL software (and possibly pay for it) ? is dual licensing allowed by the AGPL ?
  - tkfu 6y ago
    If you're the sole copyright owner, you can offer as many different licenses as you want, and no copyleft license can interfere with that.
  - dualscyther 6y ago
    Yes, you can licence it however you want because you are the copyright holder. See mongodb. IANAL. Licences are to restrict those who do not hold copyright.
    - teddyh 6y ago
      > Licences are to restrict those who do not hold copyright. On the contrary, licenses gives permission to those who do not hold copyright. Without any license, only the copyright holder has any rights to copy or modify the work in any way (except for fair use). A license gives permissions to non-copyright holders to do things which would otherwise be illegal under copyright law. A license can never restrict what anyone would otherwise be allowed to do, since it is not a contract.

gwbrooks 6y ago

I keep a v2 instance running on my Windows laptop solely for taking notes and keeping need-it-eventually information organized. It's just enough added structure and functionality to make the whole body of notes more useful, without having to learn a formal system or adopt someone else's idea of what my note hierarchy should look like.

Keyframe 6y ago

I need one function in a wiki platform that I haven't seen so far. When I write text, in its WYSIWYG editor, I need an ability to paste in an image (a screenshot that I just grabbed, let's say) and for it to automatically upload it and embed it into text. Does this support something like that?

reacharavindh 6y ago
This. Thousand times this. I have been waiting for an online wiki with the usability of Apple Notes that I use locally on all my Apple devices. It works like a charm except that I cannot make it public. This is why I often take notes rather than write blog posts on my website. If the wiki software was as easy drag and drop as Apple Notes, I’d just take notes and they turn into publicly available wikis! I am yet to find that tool. I would happily pay for such a tool with one braking condition that it must be self-hostable. I will not write my content into something like Medium or Notion where I don’t own my content.
- snickmy 6y ago
  This is technically feasible. The latest html5 api (quite well adopted) allow copy paste from the OS and drag and drop. There is quite a bit of server side / javascript to implement, but it is feasible.
- jve 6y ago
  This seems like it: ImgPaste plugin for DokuWiki https://www.dokuwiki.org/plugin:imgpaste https://www.dokuwiki.org/plugin:imgpaste https://github.com/cosmocode/dokuwiki-plugin-imgpaste https://github.com/cosmocode/dokuwiki-plugin-imgpaste
- motiejus 6y ago
  I will announce something like this soon: - ui: joplin. - agpl, fully self-hostable. - you own your content (because joplin). - choose among free templates, or create your own. - templates will be similar or compatible to hugo, still tbd. Optional for paying customers: - sync via webdav to my service. - custom domain. - backups, etc. Once this starts generating money, I am planning to spend some of it to fund e2e per-folder encryption in joplin.

oneplane 6y ago

I wonder why it's AGPL and not dual-licensed or some different GPL. As it is right now it's dead in the water for any commercial usage unless you're manually installing the thing on a manually installed server somewhere (which you probably aren't). With automation you'd build images based on their images but run via your own CI/CD with your own security scans and any additions you might need (like additional logging infrastructure). Doing that is not possible with AGPL.

deleted 6y ago
[deleted]
normalnorm 6y ago
> As it is right now it's dead in the water for any commercial usage So what? If companies need a certain software, they can pay for it. I remember a time when FOSS was not about providing companies with free work, quite the opposite indeed.
- oneplane 6y ago
  It is presented as being enterprise-ish, for organisations (of which a lot are commercial) and presents features usually useful for large companies. That's what. This isn't about good/bad or something like that, just an odd presentation that doesn't seem to be in line with the license. There is nobody to pay here to use this stuff because you still won't be able to integrate it without also sharing internal IP. There are plenty of organisations that would happily pay what they'd normally pay Atlassian to use Wiki.js but they can't because they don't want to share any of their own code. This is also why license guides like the one from google explicitly bans all AGPL software because it's not worth the risk.
  - fungos 6y ago
    These company make changes to Atlassian code? You're conflating internal or public use with derivative work or service offering. You clearly misunderstand licensing.
  - 6y ago

hombre_fatal 6y ago

Slightly related PSA: Everyone should consider running a wiki locally just for yourself. It's like being able to organize your brain. I just got into it two days ago and basically spent the whole weekend dumping things into it in a way I can actually browse and revisit, like the short stories I'd written, spread out across Notes.app and random folders. You don't need to run WAMP, MySQL, Apache, phpmyadmin or anything. Here are the steps for someone, like me, who hadn't checked in a while: 0. `$ brew install php` (or equiv for your OS) 1. Download the wiki folder and `cd` into it 2. `$ php -S localhost:3000` 3. Visit http://localhost:3000/install.php http://localhost:3000/install.php in your browser I tried DokuWiki at first (has flat file db which is cool). It's simpler, but I ended up going with MediaWiki which is more powerful, and aside from Wikipedia using it, I noticed most big wikis I use also use it (https://en.uesp.net/wiki/Main_Page https://en.uesp.net/wiki/Main_Page). MediaWiki lets you choose Sqlite as an option, so I have one big wiki/ folder sitting in my Dropbox folder symlinked into my iCloud folder and local fs. Really changing my life right now. The problem with most apps is that they just become append-only dumping grounds where your only organizational power is to, what, create yet another tag? My advice is to just look for the text files scattered around your computer and note-taking apps and move them into wiki pages. As you make progress, you will notice natural categories/namespaces emerging. I just wish I started 10 years ago.

jcelerier 6y ago
> I tried DokuWiki at first (has flat file db which is cool). It's simpler, but I ended up going with MediaWiki which is more powerful, and aside from Wikipedia using it, I noticed most big wikis I use also use it (https://en.uesp.net/wiki/Main_Page https://en.uesp.net/wiki/Main_Page). MediaWiki lets you choose Sqlite as an option, so I have one big wiki/ folder sitting in my Dropbox folder symlinked into my iCloud folder and local fs. or you can just use Zim which is a cross-platform desktop app which does not need any setup and simply save files as text files in markdown : https://zim-wiki.org https://zim-wiki.org
- hombre_fatal 6y ago
  There definitely are a lot of options to check out (one of the reasons I went with MediaWiki). I recommend playing with them to get a feel for where they diverge from one another. You may find features in some that you decide are necessary for you that a marketing list of bullet points can't get across.

tweetle_beetle 6y ago

I'm looking to launch an internal wiki and Wiki.js came out on top for my requirements: - easy to use for technical and non-technical staff alike: multiple editing options - third party authentication: really comprehensive offering - quality search: comprehensive internal and third party search offering - ease of maintenance: largely everything is built-in, so no module/dependency maintenance headaches - user management: solid user/group management system With internal tools you need things to stick, and fast. As much as I am fond of mediawiki, the editing experience is a barrier to usage for many. And the extension ecosystem, while rich and diverse, is just more of a liability than a single installation. A quality search is also really important to adoption, so having options there is great. I'd been using Docsify on a small scale with authentication through GitLab to edit, GitLab CD to build and Cloudflare Access to secure the front end. It works really well, but the lack of user management and the editing experience mean that it's time to move on. It would be great to hear if this is a case of the grass always being greener on the other side.

mard 6y ago

I'm not impressed. Wiki.js is supposedly "built with performance in mind", but its documentation wiki [1] is much slower than any DokuWiki site I could find [2]. It also requires JavaScript to be enabled in the web browser. [1]: https://docs.requarks.io/ https://docs.requarks.io/ [2]: https://www.dokuwiki.org/ https://www.dokuwiki.org/

a012 6y ago
I also don't like their theme choice, especially the "Table of Contents" is fixed and wasteful, and combined with navigation column they used 40% of the screen wide. I can't concentrate to the content because the other half is distracting.
Rotten194 6y ago
I find it really frustrating that every piece of software nowadays claims to be "blazing fast" or "built for performance", usually with no benchmarks to back it up. Makes it really hard to tell at a glance what the strengths of a project actually are. I honestly would be very grateful if a project up and said "we're not the fastest, but we trade performance for a simpler codebase and easier extensibility. If you need to do some-performance-intensive-task, try other-package instead".

techaddict009 6y ago

Can I know what exactly this numbers are "15M+ Installations" On your home page. I mean thats too large number. Is this of all open source software or I am misunderstanding something else?

jjice 6y ago
I'm assuming that's for every single download, including testing. I know that when I use a service for the first time, I do a few installs while getting used to the software and its configuration. I'd assume they'd have no other way to verify installs (assuming there is no telemetry).

favadi 6y ago

For personal wiki, nothing beats the simplicity of tiddlywiki.

yreg 6y ago

Wikis are also useful for note-taking, I'm using Wiki.js to document a D&D campaign to have some canonical reference of what actually happened in past sessions.

pspeter3 6y ago
Why did you pick Wiki.js for campaign management as opposed to something like Notion?
- jdironman 6y ago
  Big fan of Notion here for both documentation, task management, and general brain dumps. Only worry I have is one day they go away and I have to migrate off how much of a pain that would probably be. It feels locked in, maybe i am wrong
zcdziura 6y ago
Same here, it's been a great asset to have available to document stuff in my homebrew world and have it reference other stuff. Being able to link my wiki out to my players for their own use is very handy.

aerojoe23 6y ago

We needed a documentation solution at work. MY coworker had some experience with Wiki.js. What sold me on it was that you can use markdown and it can keep itself synced with a git repo. This gives us plan text files that are tracked in a repo. It uses the user as the author, so now I can "code review" edit's to our wiki. The content of the wiki is easily cloned by cloning the git repo. It is markdown in folders so if wiki.js dies at some point I could write a pandoc script to turn it into web pages again, you do loose all of the cool UI features.

lukaszkups 6y ago

Is it possible to output static-file-based wiki? (so some static HTML/CSS/js ?)

ddevault 6y ago

Can we please not have SPA's eat wikis, too? Text-only content does not need... (checking...) 6.3 MB of JavaScript to display (checking...) 3.3 KB of text. Blank pages with JavaScript disabled or in non-mainstream browsers is a really terrible experience for content so plainly simple to display.

cxr 6y ago
Wikis also don't need (or indeed, even permit) cumbersome Git and PR-based workflows just to get changes into the "wiki". Better for it to be a single-page app that actually implements a wiki, than to provide a service that doesn't actually support wikis but has no qualms about throwing the word around anyway.

heresie-dabord 6y ago

I used a Wiki for a long time. But I try to minimise maintenance ("foist it upon others"). I also try to resist the enthusiasm for Rube Goldberg machines and for installing bad tooling (such as PHP). Now that git has become ubiquitous, I prefer git with a self-hosted git-daemon instance. git , grep , awk , and sqlite make a strong set of tools for knowledge curation. edit: minor grammar fix

ArtDev 6y ago
Unnecessarily bashing PHP is soo 2005. Like javascript, it can be written poorly due to its loose roots. Also just like javascript, it is a very different language now. That said, DocuWiki is pretty decent to get up and running quickly.
- john-shaffer 6y ago
  I use PHP in my day job. It is by far the worst language I've ever used. Nothing else even comes close. The language and ecosystem are so full of footguns that you are bound to shoot yourself eventually. The OpenSSL implementation will silently truncate the key [1][2] without even giving a warning. The cURL lib, in 2020, still hasn't implemented a get_curl_opt function. Sure you could wrap it if you're writing everything, but the reality is I have to work in this nightmare ecosystem that just uses raw curl. Every == comparison is still a potential security hole due to PHP's insane (and inconsistent) typecasting behaviors. Sometimes a number gets cast to a string, but a string gets cast to a number if you use it as an array key. WTF? Do I have to wait another 15 years for PHP to become a halfway decent language? [1] https://github.com/WP2Static/wp2static/pull/506 https://github.com/WP2Static/wp2static/pull/506 [2] https://stackoverflow.com/questions/55062897/decrypt-aes256-on-python-vs-php/55063033#55063033 https://stackoverflow.com/questions/55062897/decrypt-aes256-...
  - heresie-dabord 6y ago
    > The language and ecosystem are so full of footguns "footgun" is an excellent term. Here's an earlier use on HN, 2010: https://news.ycombinator.com/item?id=1904960 https://news.ycombinator.com/item?id=1904960

amelius 6y ago

Why is there a Linux Tux logo next to macOS?

mbrd 6y ago
They are separate items in the horizontal list: https://wiki.js.org/img/linux.3297c180.svg https://wiki.js.org/img/linux.3297c180.svg https://wiki.js.org/img/macos.96f6d85a.svg https://wiki.js.org/img/macos.96f6d85a.svg

Nuzzerino 6y ago

I've been using Wiki.js for several months now on a production project (self hosted). It has worked nearly flawlessly for me so far. No complaints. Setup was a piece of cake too.

dheera 6y ago

Just a minor nitpick. If there isn't an actual file called "wiki.js" that is self-contained, I would prefer it be called WikiJS instead of "Wiki.js" to avoid confusion. In general when I see ".js" I expect to see a single file I can import that does something useful to my code.

Marioheld 6y ago

Does anyone has a comparison to Bookstack?www.bookstackapp.com

amelius 6y ago

In case anyone was wondering, the dependencies are: Node.js 10.12 or later MySQL, MariaDB, PostgreSQL, MSSQL or SQLite3 Is it possible to install and run all of these as a non-root user?

xcambar 6y ago
Absolutely. For Node, check nvm : https://github.com/nvm-sh/nvm https://github.com/nvm-sh/nvm And choose SQLite.
acoard 6y ago
Even better, you can run these in Docker as non-root. Security wise, while this wouldn't make your app itself more secure, it would insulate your host OS from getting infected. I just checked and they even have one-liner Docker commands that do just this: docker run -d -p 8080:3000 --name wiki --restart unless-stopped -e "DB_TYPE=postgres" -e "DB_HOST=db" -e "DB_PORT=5432" -e "DB_USER=wikijs" -e "DB_PASS=wikijsrocks" -e "DB_NAME=wiki" requarks/wiki:2
Reubend 6y ago
I think you only need 1 DB, not all of them.

deleted 6y ago

[deleted]

kontxt 6y ago

Kontxt (https://kontxt.io https://kontxt.io) could be a perfect inline communication and engagement layer to enhance wikis and docs with inline highlights, comments, polls, @mentions, page navigation, shareable deep links, and permission-based sharing.

emiliovesprini 6y ago
Did... did kontxt.io write this? Oh wait yeah.
- kontxt 6y ago
  Hello emiliovesprini! You are correct. That's actually why the username "kontxt" was specifically selected. Decided to share here because people exploring the wiki and documentation space might find it useful. Best regards fellow code creator.

cptskippy 6y ago

I like the way the documentation is laid out, does that conform to a standard?

kinganurag 6y ago

i love this platform, i will suggest this to all my friends and clients :)

bobbydreamer 6y ago

Like the common theme all this wiki and outline are having 3 pane window any for Bootstrap it.