20231216

Notable changes

• data-poster can now be used on the embed script - https://docs.asciinema.org/manual/server/embedding/#poster
• easier SMTP configuration, without namshi/smtp container - https://docs.asciinema.org/manual/server/self-hosting/configuration/#email
• added admin console endpoint in port 4002, with Phoenix LiveDashboard at http://localhost:4002/dashboard
• setting URL_SCHEME=https now automatically infers URL_PORT=443 - https://docs.asciinema.org/manual/server/self-hosting/configuration/#base-url
• default PostgreSQL connection pool size has been decreased from 20 to 10
• using object store (S3, R2, MinIO) for file storage is easier now - https://docs.asciinema.org/manual/server/self-hosting/configuration/#file-store
• added About page at /about

Breaking changes

• the data (uploads) directory inside the container changed - see below

Upgrading

Bump the container image version number in docker-compose.yml:

 services:
   asciinema:
-    image: ghcr.io/asciinema/asciinema-server:20231120
+    image: ghcr.io/asciinema/asciinema-server:20231216
     # ...

Next, update the volume mapping:

In previous versions, when local file store was used (default), the uploads were stored in /opt/app/uploads. Starting with this release, all persistent data is written to /var/opt/asciinema. Uploads in particular are stored in /var/opt/asciinema/uploads.

Right now, asciinema server writes to /var/opt/asciinema/uploads only, but in the future we may use other directories in /var/opt/asciinema/ to store other files.

The quick fix, is to make the following change to the volume mapping section:

 services:
   asciinema:
     volumes:
-      - ./path/to/asciinema/uploads:/opt/app/uploads
+      - ./path/to/asciinema/uploads:/var/opt/asciinema/uploads
     # ...

A more future proof solution is to change the mapping like this:

 services:
   asciinema:
     volumes:
-      - ./path/to/asciinema/uploads:/opt/app/uploads
+      - ./path/to/asciinema:/var/opt/asciinema
     # ...

Note the change also on the host side - we now map the parent directory of the uploads directory, which will let the server create other sub-directories next to uploads.

Finally, execute docker compose up -d.