Now the blog is written on Hugo. This article is the first post from the old blog, which, just like that, was on Ghost.

• Notes

First article. Reminded me of Isaac Asimov’s “The Last Question”, listened to on the way to work one of those ordinary days. A good thing - recommend it. Writing a good article, which will be a worthwhile read, is not as easy as it seemed at first. There are two reasons for this:

1. Thoughts must be useful.
2. The text should be systematized.

The system is launched on Ghost - the server is good, fast, and started easily, there’s enough tooling for such a pseudo-blogger like me. There’s a built-in plugin for choosing images from Unsplash - images that can be published without fear of being sued for copyright infringement. docker-compose.yml file, which makes this whole thing easy to set up, is presented below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17

version: '3.7'

services:
  ghost:
    image: ghost:3.9.0-alpine
    container_name: ghost
    restart: unless-stopped
    port:
      - '80:2368'
    volumes:
      - /data/ghost:/var/lib/ghost/content:rw
    environment:
      - url=http://example.com
    logging:
      driver: json-file
      options:
        max-size: 100m

Notes ¶

1. Always keep the version of the image, from which the container will be started. This helps avoid problems with the stack restarting later on. If you use latest, it’s possible that when you recreate the stack, up -> down might start again a newer version, which won’t be compatible with the current data and settings etc. Moreover, it’s impossible to quickly and easily remember which version was exactly launched at the moment of startup?
2. Always control the logging process. If using the standard Docker logging driver - json-file, then by default, the Docker daemon will receive logs and write them to a file for this container until the disk runs out. By default, the file is always one, but its location can be limited by setting the max-size: 100m option (I just took 100 MB, it’s unlikely that anyone would read more than that). More information about the json-file Docker logging driver.
3. I recommend always specifying container_name - it’s easier to read docker ps.