Synology

Container Manager on DSM 7.2 or later runs Mnema Talk as a project. The DSM reverse proxy gets the certificate, and one-click updates work too.

1. Make the files

In File Station, create docker/mnema-talk (the path is /volume1/docker/mnema-talk). Enable SSH (Control Panel > Terminal & SNMP), sign in as an administrator and run the assistant there:

cd /volume1/docker/mnema-talksudo docker run --rm -it --user "$(id -u):$(id -g)" \
  -v "$PWD:/out" ghcr.io/mnema-xyz/mnema-talk setup

$(id -u) is evaluated before sudo, so the files belong to you, not to root. No SSH? Run the assistant on any computer with Docker and copy the two files into that folder.

2. Create the project

Container Manager > Project > Create: name mnema-talk, path /volume1/docker/mnema-talk, "Use existing docker-compose.yml", next until done. It pulls the images and starts the stack. A project pulls by the full name, so ghcr.io needs no registry entry.

If your NAS reaches Docker Hub more easily than ghcr.io, set MNEMA_IMAGE=mnemaxyz/mnema-talk:latest (or a tag such as mnemaxyz/mnema-talk:3.3, the minor line you run) in the .env and rebuild the project. It is the same image with the same signature.

3. HTTPS with the DSM reverse proxy

Create a reverse-proxy entry from https://chat.example.com:443 to http://localhost:8080, add the WebSocket custom header and assign a Let's Encrypt certificate: step by step. The compose file needs no edit for it.

To use another app port, set PORT= in the .env in the project folder and rebuild the project. If the proxy runs on another machine, set PUBLISH_ADDR= to the NAS's LAN address (not 0.0.0.0 on a NAS that faces the internet) and keep that port closed on the router.

4. Router and firewall

Forward the three ports to the NAS. If the DSM firewall is on (Control Panel > Security > Firewall), allow the same ports there.

One-click updates

Answer yes to the updater question in the assistant, or add two lines to the .env in the project folder:

COMPOSE_PROFILES=autoupdate
UPDATER_TOKEN=<output of: openssl rand -hex 32>

Rebuild the project once (Container Manager > Project > mnema-talk > Action > Stop, then Build). Container Manager reads the profile from that .env and starts mnema-updater and mnema-recreator next to the app. From then on use Admin > System > Update now. Read what the button can do first.

Good to know

  • Logs without a shell: Container Manager > Container > mnema-talk > Log.
  • <none> as the tag of the postgres, seaweedfs and watchtower images is expected: they are pinned by digest.
  • Container Manager's own update view only tracks registries in its list, so it will not flag a new Mnema Talk image; the admin update check and the Update now button do.
  • Web Station lists only literal ports. If you prefer it to the reverse proxy, change the app's port line in docker-compose.yml to a literal such as "127.0.0.1:8080:8080", and repeat that after each compose update.

Something wrong on this page? Tell us.