linkding

​

Towbar manifest

id: linkding
name: linkding
file: deploy/linkding/compose.yml
strategy: maintenance
services:
  linkding:
    port: 9090
    domains:
      - linkding.example.com
    ingress:
      type: proxy
environments:
  production:
    server: 192.0.2.10
secrets:
  runtime:
    - LD_SUPERUSER_NAME
    - LD_SUPERUSER_PASSWORD
    - LD_CSRF_TRUSTED_ORIGINS

​

Compose project

services:
  linkding:
    image: sissbruecker/linkding:1.42.0@sha256:12ffd6f3b48c5d46543d2f38030de1f476d8dcff5f486eb75c9c7cb5941e7127
    environment:
      LD_SUPERUSER_NAME: ${LD_SUPERUSER_NAME}
      LD_SUPERUSER_PASSWORD: ${LD_SUPERUSER_PASSWORD}
      LD_CSRF_TRUSTED_ORIGINS: ${LD_CSRF_TRUSTED_ORIGINS}
    volumes:
      - data:/etc/linkding/data
volumes:
  data: {}

​

Configure

1. Prepare the example server, connect the repository, and map production to the branch containing these files. Replace the example server IP and domain.
2. Commit every file shown below under deploy/linkding/. The Towbar manifest points to the Compose file; it does not create it for you.
3. Sync the repository and inspect the resolved Compose project. Save the runtime values below if this example declares any.
4. Save the three runtime values before deploying. The initial administrator variables create a user only if that username does not already exist.
5. Back up the data volume; it holds bookmarks, archived pages, and the signing key.
6. Deploy it manually and run the verification below before enabling auto-deploy.

​

Runtime values

​

Verify