mmmWiki - Wiki Engine/Software (and online filesystem)
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 (requires more RAM) or Mysql
- Mediawiki-style syntax. See also: What wiki syntax to use
Features also found on MediaWiki
"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 (open and close the editView (click then backing) 3 times within 10 seconds and the adminButton () appears. This button will open the adminView):
- Elaborate File manager (Page/image lists)
- Backing up: Upload/download all pages/images to your local computer as files packed in zip-folders.
- Embed monitoring with iframes on your favorite page: Monitor multiple wikis
- Read/write access can be set on each page.
- When renaming a page or image, the wiki texts of the parents are scanned for links / image-urls and renamed.
"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.
- Admin/View passwords are SHA1-hashed.
- CSRF-codes are used.
- TLS (SSL):
- I'm currently using TLS with nginx
- Chrome OK
- Firefox OK
- Opera OK
- Safari: OK
- UC Browser: Read only (last tested 2017)
The app itself usually requires between 50-100 MB after running for a while.
The database and operating system (linux) also requires some memory of course.
The mysql version can run on 512MB if you tweak the mysql a bit (google how to run mysql with little ram)
The neo4j version runs fine on 1GB ram (but probably not 512MB)
- 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
- Image gallery (with slide show).
- Templates: HELLO WORLD
- The iframe-tag can be used if the "Allow others to edit this page"-checkbox is unclicked;
- nowiki - tag (no wikitranslation + encoding of html special characters (
- The video-tag can be used. Ex: Video
- Two trailing spaces (before a newline) inserts a
<p/>-tag (similar to GFM)