Oddµ: A minimal wiki

This program runs a wiki. It serves all the Markdown files (ending in .md) into web pages and allows you to edit them.

This is a minimal wiki. There is no version history. It probably makes sense to only use it as one person or in very small groups.

It's very minimal and only uses Markdown. No wiki extras, so double square brackets are not a link. If you're used to that, it'll be strange as you need to repeat the name: [like this](like this).

Building

go build

Test

mkdir wiki
cd wiki
go run ..

The program serves the local directory as a wiki on port 8080. Point your browser to http://localhost:8080/ to get started. This is equivalent to http://localhost:8080/view/index – the first page you'll create, most likely.

If you ran it in the source directory, try http://localhost:8080/view/README – this serves the README file you're currently reading.

Deploying it using systemd

As root:

# on your server
adduser --system --home /home/oddmu oddmu

Copy all the files into /home/oddmu on your server: oddmu, oddmu.service, view.html and edit.html.

Set the ODDMU_PORT environment variable in the oddmu.service file (or accept the default, 8080).

Install the service file and enable it:

ln -s /home/oddmu/oddmu.service /etc/systemd/system/
systemctl enable --now oddmu

Check the log:

journalctl --unit oddmu

Follow the log:

journalctl --follow --unit oddmu

Edit the first page using lynx:

lynx http://localhost:8080/view/index

Web Server Setup

HTTPS is not part of the wiki. You probably want to configure this in your webserver. If you're using Apache, you might have set up a site like the following. In my case, that'd be /etc/apache2/sites-enabled/500-transjovian.conf:

MDomain transjovian.org
MDCertificateAgreement accepted

<VirtualHost *:80>
    ServerName transjovian.org
    RewriteEngine on
    RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [redirect]
</VirtualHost>
<VirtualHost *:443>
    ServerAdmin alex@alexschroeder.ch
    ServerName transjovian.org
    SSLEngine on

    RewriteEngine on
    RewriteRule ^/$ http://%{HTTP_HOST}:8080/view/index [redirect]
    RewriteRule ^/(view|edit|save)/(.*) http://%{HTTP_HOST}:8080/$1/$2 [proxy]
</VirtualHost>

First, it manages the domain, getting the necessary certificates. It redirects regular HTTP traffic from port 80 to port 443. It turns on the SSL engine for port 443. It redirects / to /view/index and any path that starts with /view/, /edit/ or /save/ is proxied to port 8080 where the Oddmu program can handle it.

Thus, this is what happens:

• The user tells the browser to visit http://transjovian.org (on port 80)
• Apache redirects this to http://transjovian.org/ by default (still on port 80)
• Our first virtual host redirects this to https://transjovian.org/ (encrypted, on port 443)
• Our second virtual host redirects this to https://transjovian.org/wiki/view/index (still on port 443)
• This is proxied to http://transjovian.org:8080/view/index (no on port 8080, without encryption)
• The wiki converts index.md to HTML, adds it to the template, and serves it.

Access

Access control is not part of the wiki. By default, the wiki is editable by all. This is most likely not what you want unless you're running it stand-alone, unconnected to the Internet.

You probably want to configure this in your webserver. If you're using Apache, you might have set up a site like the following.

Create a new password file called .htpasswd and add the user "alex":

cd /home/oddmu
htpasswd -c .htpasswd alex

To add more users, don't use the -c option or you will overwrite it!

To add another user:

htpasswd .htpasswd berta

To delete remove a user:

htpasswd -D .htpasswd berta

Modify your site configuration and protect the /edit/ and /save/ URLs with a password by adding the following to your <VirtualHost *:443> section:

<LocationMatch "^/(edit|save)/">
  AuthType Basic
  AuthName "Password Required"
  AuthUserFile /home/oddmu/.htpasswd
  Require valid-user
</LocationMatch>

Configuration

Feel free to change the templates view.html and edit.html and restart the server. Modifying the styles in the templates would be a good start.

You can remove the auto-generated titles from the files, for example. If your Markdown files start with a level 1 title, then edit view.html and remove the line that says <h1>{{.Title}}</h1> (this is what people see when reading the page). Optionally also remove the line that says <title>{{.Title}}</title> (this is what gets used for tabs and bookmarks).

If you want to serve static files as well, add a document root to your webserver configuration. Using Apache, for example:

DocumentRoot /home/oddmu/static
<Directory /home/oddmu/static>
    Require all granted
</Directory>

Create this directory, making sure to give it a permission that your webserver can read (world readable file, world readable and executable directory). Populate it with files. For example, create a file called robots.txt containing the following, tellin all robots that they're not welcome.

User-agent: *
Disallow: /

You site now serves /robots.txt without interfering with the wiki, and without needing a wiki page.

Wikipedia has more information.

Customization (with recompilation)

The Markdown parser can be customized and extensions can be added. There's an example in the usage section. You'll need to make changes to the viewHandler yourself.

Limitations

Page titles are filenames with .md appended. If your filesystem cannot handle it, it can't be a page title. Specifically, no slashes in filenames.

References

Writing Web Applications provided the initial code for this wiki.

For the proxy stuff, see Apache: mod_proxy.

For the usernames and password stuff, see Apache: Authentication and Authorization.