Markiki

IMPORTANT NOTICE

The project is currently unmaintained - the world is getting better at wikis I think. So the project might or might not see many new commits from me. However, I'll have very quick response time of PRs.

Rationale

Have you ever woke up sweating in the middle of the night trying to recall the deploy procedure of an application you started two years ago on your server only to find out that you irreparably forgot it?

Have you ever been tired of having to fire up an instance of MediaWiki to document all your personal deploys/drafts/thoughts/recipes/< put-something-here >?

Have you ever cried while googling for some obscure MediaWiki syntax rule?

---

Yeah, we all atleast once did the things listed up there.

But here comes Markiki, a static markdown personal wiki!

Installation

Easy as:

• Install Java on your box. (openjdk7 is ok)
• Grab the latest release and put the markiki executable somewhere in your path. (e.g. ~/bin)

Usage

$ markiki [options] /path/to/source/markdown/files/

Then serve the folder /path/to/source/markdown/files/_output/ with your favourite webserver!

Important things to know

• The source path you provide as a parameter will have to be structured as follows:

.
+-- _config.yml                         // this is optional
+-- _posts
|   +-- some-random-file.md
|   +-- a-category
|   |   +-- this-is-ignored.jpg
|   |   +-- a-categorized-file.md
|   |   +-- a-subcategory               // you can nest categories as needed
|   |   |   +-- subcategorized-text.md
+-- _output                             // here there will be your html to serve
+-- _static
    +-- an-image-you-will-link.jpg

• Your webserver should serve the /path/to/source/markdown/files/_output/ folder
• Into the source folder, any directory called _static will be ignored, as the name is reserved for hosting static assets.
• Your markdown files in the source folder will have .md extension, a big title (single #) that will become the article title, and their filesystem name will become the article path into the wiki.

Command line options

-h, --help : print out the help text

-w, --watch : watch the source folder for changes

Markdown infos

• Internal links can be made with linking like [Link description](#/internal/path)
• Static resources should be put into the _static folder, and can be linked like [Link description](_static/static-image.jpg)

_config.yml options

• title: the title of the webpage
• description: a brief description (markdown enabled) that will appear before your article list

Sample config:

title: My fancy Wiki
description: *Wow, markdown works also here*

Hacking

• Clone this repo somewhere, then cd markiki
• Install java, install lein
• ./scripts/watch to start the cljs autobuilding (or ./scripts/build for a one-time build)
• ...Make your changes...
• (Tests coming soon!)
• In another terminal, run lein run -- /path/to/source/markdown/files/ everytime you want an updated version, and point your browser to file:///path/to/source/markdown/files/_output/index.html (or refresh the page)
• Alternatively, you can build also with lein bin && target/markiki /path/to/source/markdown/files/ etc.

Bugs

For bugs, questions, comments, anything really, please open an issue!

Docker image

docker run --name $CONTAINER_NAME -v $SOURCE_PATH:/home/markiki -p $HOST_BIND_IP_PORT:80 -d nilrecurring/markiki

In this case the variable $HOST_BIND_IP_PORT should be in the form IP:PORT (e.g. 0.0.0.0:80)

To build from the local Dockerfile just docker build -t nilrecurring/markiki ., to get it from the Docker Hub instead type docker pull nilrecurring/markiki

Contributors

See: https://github.com/ff-/markiki/graphs/contributors