added docker support to `make release`

Updated Dockerfile

Add code highlighting

Avoids loading render.tmpl where it isn't needed.

* upstream/master:
  Work as a standalone server, including TLS
  Include About/Privacy page content in page description
  Show instance stats on About page
  Change default database name to writefreely
  Use and validate database type before connecting
  Mention Contributing Guide in README
  Add AUTHORS.md
  Fix About page link in Admin dash
  Include version in archives made by `make release`
  Remove keys.sh from make release
  Add make release

Crux was the load event for the script tag inserted.

This supports running the server on port 443, serving secure pages, with
automatic redirects from the insecure site. It also modifies the
configuration process to better guide users through configuring for
running behind a reverse proxy or as a standalone server.

This closes T537

This also moves the stats database logic out of nodeinfo.go and into
database.go.

(not writeas)

Just the start of changes needed for T529.

We load it always, no need for a user config UI

Might as well do this right away, we're here anyway.

It now loads unconditionally and highlights all code blocks.

TODO: optimize to not load when there are no blocks

* master:
  Don't automatically include "v"  from git
  Get versioninfo from the git repository

Get versioninfo from the git repository

- "v" should not be part of the version (softwareVer variable is used
  in other places)
- formatting

Sets value of softwareVer during build

This is a first stab at having a configurable code highlighting option,
similar to the MathJax rendering option. This change makes a checkbox
in the settings for code highlighting using the highlightjs.org
library.
What works: code highlighting in multi-user env is like I would
expect. single and anon(?) needs work

Things to resolve/consider:
- does the .IsCode test for code highlighting need to stay? At least
this and that should use the same version of the highlight.js lib.
- can the common templating part be 'included' somehow?
- the anon vs single-user vs multi-user code is not completely
clear (to me)
- bring js to local instead of cloudfare cdn (perhaps combine with
MathJax)

This allows admin to edit these pages from the web, using Markdown. It
also dynamically loads information on those pages now, and makes loading
`pages` templates a little easier to find in the code / more explicit.

It requires this new schema change:

CREATE TABLE IF NOT EXISTS `appcontent` (
  `id` varchar(36) NOT NULL,
  `content` mediumtext CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
  `updated` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

This closes T533

Start of T538

This helps with post importing and clients that want to support post
scheduling. It also changes how Collection.ForPublic() works, no longer
resetting the ID.

Closes T532

This fixes things like em-dashes and adds new glyphs.

Previously the logic was mixed up -- multi-user blogs would always load
collection number 1.

Improved the Docker dev workflow slightly.