# Self-host Linkding Plus

> Linkding's extended image with full-page snapshot archiving bundled in, for bookmarks that must survive link rot.

- Page: https://levelrail.com/templates/linkding-plus/
- JSON: https://levelrail.com/templates/linkding-plus.json
- Category: Productivity
- Licence: MIT (Permissive license)
- Source: https://github.com/sissbruecker/linkding
- Upstream docs: https://linkding.link

## Requirements
- Memory: about 256 MiB
- amd64: published, arm64: published
- Needs configuration before start: no
- Pinned image tag: 1.47.0-plus

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| linkding-plus | sissbruecker/linkding | 1.47.0-plus | 9090 | linkding_plus_data -> /etc/linkding/data |

## Environment

| Service | Variable | Kind |
| --- | --- | --- |
| linkding-plus | LD_SUPERUSER_NAME | generated |
| linkding-plus | LD_SUPERUSER_PASSWORD | generated |

## Deploy

### CLI

```bash
levelrail-cli templates deploy linkding-plus --name my-linkding-plus
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/linkding-plus/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## Questions

### Can I deploy Linkding Plus on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Linkding Plus, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image sissbruecker/linkding:1.47.0-plus is what you deploy there.

Self-host Linkding Plus, Linkding Plus docker compose file, deploy Linkding Plus on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
