A web blog and personal website server.
Go to file
2019-08-19 17:46:44 -07:00
cmd Add a -v flag to print version information 2019-06-05 16:28:59 -07:00
jsondb Shuffle around package directories 2018-02-09 18:46:58 -08:00
models Extract Blog Thumbnails for Archive Page 2019-06-05 16:18:38 -07:00
root Extract Blog Thumbnails for Archive Page 2019-06-05 16:18:38 -07:00
src Fix up RSS/Atom feeds 2019-08-19 17:46:44 -07:00
.editorconfig Initial static file router 2017-10-07 21:48:58 -07:00
.gitignore Various small nice fixes 2018-04-10 19:07:25 -07:00
blog.go Feature: Ask Me Anything 2018-12-24 11:50:29 -08:00
Dockerfile Rebase Dockerfile on golang:1.10 2018-09-18 11:21:11 -07:00
errors.go Move package from internal to src 2018-12-23 16:21:50 -08:00
go-reload Initial static file router 2017-10-07 21:48:58 -07:00
go.mod Make it a Go module 2019-06-20 13:36:42 -07:00
go.sum Make it a Go module 2019-06-20 13:36:42 -07:00
LICENSE.txt Initial commit 2017-10-07 20:13:31 -07:00
Makefile Rebase Dockerfile on golang:1.10 2018-09-18 11:21:11 -07:00
pages.go Move package from internal to src 2018-12-23 16:21:50 -08:00
README.md Rebase Dockerfile on golang:1.10 2018-09-18 11:21:11 -07:00
TODO.md Blog post creation, viewing, index listing, editing, deleting 2017-11-24 11:56:32 -08:00

Blog

This is a web blog and personal homepage engine written in Go. It includes a full-featured web blog (with tags, archive views, etc.) and can serve static web assets, Go HTML templates and Markdown pages.

Features

Zero Configuration

Blog is designed to be extremely easy to run: just give it a path to your website's document root. It doesn't have to exist: it can be created as needed!

blog $HOME/www

See blog -h for command line arguments, for example to make it listen on a different port number.

The blog database is kept on disk as JSON files under the document root.

Dual Template System

Whenever a web request is handled by the Blog program, it checks your user-defined Document Root to serve the file before falling back on its built-in store of "Core Files."

This way, you can copy and override files from the Core Root by creating files with the same names in your Document Root. If you override .layout.gohtml, you can customize the overall web design of your site. You can also override individual templates to customize the look of built-in pages, such as how blog entries are formatted.

The Blog has a built-in page editor that makes it easy to copy and override the core template files.

Render Go HTML and Markdown Files

You can write pages in the Go html/template format (.gohtml) or in GitHub Flavored Markdown (.md). Markdown pages will be rendered to HTML and inserted into your web design layout like normal pages.

Built-in Page Editor

A built-in editor lists all of the pages in your Document Root and the Core Root. You can click on a page to edit it, with the ACE Code Editor offering a rich code editing experience, with syntax highlighting for HTML, Markdown, JavaScript and CSS.

Editing a Core Page and saving it will save an override version in your Document Root.

In the default Blog theme, every page includes a link to edit the page in the Page Editor for logged-in users. The 404 Error handler also provides shortcuts to create a new page at that path.

Setup

# If you're new to Go, set your GOPATH.
export GOPATH="${HOME}/go"

# Clone this repository to your go src folder.
git clone https://github.com/kirsle/blog ~/go/src/github.com/kirsle/blog
cd ~/go/src/github.com/kirsle/blog

# Run the server
make run

# Or to run it manually with go-reload to provide custom options:
./go-reload cmd/blog/main.go [options] [/path/to/document/root]

Docker

This app includes a Dockerfile. Type make docker.build to build the Docker image.

The Docker container uses the user document root at /data/www

docker build -t blog .
docker run --rm --name blog_debug -p 8000:80 -v $(CURDIR)/user-root:/data/www blog

Quick Start

make docker.build
make docker.run

Docker Image

  • Exposes port 80 for the web server
  • User document root is mounted at /data/www

So to run the Docker image and have it listen on localhost:8000 on the host and bind the user document root to /home/user/www:

docker run -p 8000:80 -v /home/user/www:/data/www blog

You may also run make docker.run to run the Docker image on port 8000 using the ./user-root directory

Recommendation: Redis

It is recommended to use the Redis caching server in conjunction with Blog. Redis helps boost the performance in two main areas:

The JSON database system will cache the JSON documents in Redis, speeding up access time because the filesystem doesn't need to be read each time. If you manually modify a JSON file on disk, it will notice and re-read it next time it's requested.

If you make use of source code blocks in GitHub Flavored Markdown, the Python pygmentize command can render syntax-highlighted HTML from it. Calling this program takes ~0.6s, and a page with many source blocks would take a long time to load. I alleviate this by MD5-hashing and Redis-caching the rendered HTML code to minimize calls to pygmentize.

After you initialize the site, go to the admin settings to enable Redis.

Syntax Highlighting with Pygments

To enable syntax highlighting within Markdown files (like with GitHub Flavored Markdown), install pygments on your system. For example:

# Fedora/RHEL
sudo dnf install python3-pygments python3-pygments-markdown-lexer

# Debian
sudo apt install python3-pygments

Blog will automatically use the pygmentize command if it's available on its $PATH.

License

MIT.