mmmWiki - Wiki Engine/Software (and online filesystem)

Screenshots

Download/Setup

neo4j version

mysql version

Features

Most characteristic features (whether good or bad)

• No distributed management (like mediawiki). More like: one (1) "dictatorial" administrator can decide whether a page should be visible resp editable by others. The admin has total control and can detect any edit on multiple sites and can easily revert any edit.
  • Is this non-democratic? No I don't think so, since it is supposed to be easy to set up a new wiki, visitors (editors) who feels misunderstood or rebuffed should be able to set up their own wiki or blog or whatever.
  • One might say that this software is a bigger threat (competitor) to blogs/blog-software than to mediaWiki.
• Running on Node.js
• Database: Either Neo4j/MongoDB (faster but requires more RAM) or Mysql
• Mediawiki-style syntax. See also: What wiki syntax to use

Features also found on MediaWiki

• Image slide shows
• Version table and version-comparing
• (Automatic) creation and caching of image thumbs (jpg, png, gif and svg).
• Caching and what is done to speed up pageloading
• Relatively touch device friendly.

"Selling points" (The good stuff)

• Smooth fast editing/updating. (Especially for the admin)
• Multiple wikis (domains, (namespaces)) on a single implementation.
• Pretty much all the page is left to the designer of the page, no forced left-column etc. If you really want a left-column then see more at Multicolumn wiki
• Admin tools (click three times on the "Donate"-button within 10 seconds and the admin-button appears. This button will open the admin-tools):
  • Elaborate File manager (Page/image lists)
  • Backing up: Upload/download all pages/images to your local computer as files packed in zip-folders.
    • Differential backup of images
  • Embed monitoring with iframes on your favorite page: Monitor multiple wikis
  • Read/write access can be set on each page.

"Drawbacks" (The bad stuff)

• No user accounts, only two hardcoded passwords:
  • "viewing password" for reading read-protected pages.
  • "admin password" for doing administrative things (like writing to write protected pages).
• No nested templates (No templates in the templates)
• No text search.
  • My workaround is to use Google (see also FAQ)
• When renaming a page, all the links to it are not automatically renamed.
  • My workaround: Before renameing you can see the parents of a page/image in the page/image lists where you manually can visit the parent pages and rename the links.

• See also Todo (bugs) and Unimplemented stuff

Security features

• Admin/View passwords are SHA1-hashed.
• CSRF-codes are used.
• TLS (SSL):
  • I'm currently using TLS with nginx

Tested on:

• Tested Servers: Developed primarily to work on linux/localhost.
• Tested Clients:
  • Chrome OK
  • Firefox OK
  • Opera OK
    • Opera mini: No editing
  • IE
    • IE 11, Edge 12: No editing
    • Edge 13 OK
  • Safari:
    • 9: No editing
    • 10: Untested, hopefully OK (Since "generators" are working (ref), it should work)
  • Android Browser: No editing
  • UC Browser: No editing

Other

• When backing up (creating zip-file), Make sure to use the right zip-program to read the zip-file: Some zip programs doesn't handle utf-8 characters in filenames correctly

Syntax examples

• External links of different kinds: http://example.com, mylink.
• Internal links: blabla
• Interwiki links. Ex: oak,  oak 
• Tables. See also: tables in nested lists
• Image examples
• lists
• Image gallery (with slide show).
• Templates: HELLO WORLD
• Some of the usual tags: div, span, font, code, small, sub, sup, u, h1, h2, h3, h4, h5, h6 can be used. Although their attributes are "sanitized" to prevent javascript-insertion.
• The iframe-tag can be used if the "Allow others to edit this page"-checkbox is unclicked;
• The style-tag can be used althoug it is "sanitized" to prevent javascript-insertion.
• nowiki - tag (no wikitranslation + encoding of html special characters (<>&'"))
• The video-tag can be used. Ex: Video