Linkding

Organize bookmarks with tags, notes, and search.

Choose your deployment and the way you want to use Selfhost. The instructions below follow that choice.

Deployment Use Selfhost with

Set up Linkding

Editable Compose files in your own directory.

Start the app and sign in as the configured administrator using the generated password.
Set trusted public origins when introducing a domain.

selfhost app --directory ./linkding init linkding

Initialization writes portable files and does not start the app. Review compose.yaml, the private .env and any files in files/, then start it:

selfhost app --directory ./linkding start

No Selfhost dashboard or background service is needed. You can also start these files directly:

cd linkding
docker compose -f compose.yaml up -d

Connect an existing installation

Use Existing apps → Link an app in the dashboard, or the CLI’s existing-app commands. Choose Linkding, its URL and, optionally, its exact Docker container on a connected server.

Save existing.json with your app URL. Add server_id and container for container inspection and actions.

{
  "profile": "linkding",
  "name": "Linkding",
  "url": "https://app.example.com"
}

selfhost existing link --file existing.json
selfhost existing list
selfhost existing inspect EXISTING_ID

Linking enables the existing-app profile’s supported inspection and actions. It does not import Compose or attach the new-deployment settings and onboarding profiles described below.

Existing app commands, permissions and unlinking

Before configuring integrations

OIDC retains the local login form. Django system checks are available as an action.
The generated superuser password bootstraps the account; editing it later is not an account password reset.

Linkding integrations

Compose service: linkding. These operations use the profile saved when this deployment is created.

Native settings

Changes use the app’s Compose environment. Unrelated settings are preserved.

Supported fields (5)

Trusted public origins trusted-origins: Comma-separated exact http(s) origins. Do not use wildcards. string
Allowed internal bookmark hosts internal-hosts: Allow specific internal hostnames or CIDRs for metadata fetching. Avoid wildcard access. string · advanced
OpenID Connect oidc-enabled: stringChoices: True, False
Hide local login form local-login: string · advancedChoices: True, False
OIDC client secret oidc-secret: secret · advanced

Save a JSON map of the field IDs you want to change as changes.json. Replace FIELD_ID with an ID from the supported fields above, and use its declared value type. Review the plan and replace REVIEWED_REVISION with the revision it returns.

{
  "FIELD_ID": "YOUR_VALUE"
}

selfhost app --directory ./linkding config linkding
selfhost app --directory ./linkding plan linkding changes.json
selfhost app --directory ./linkding apply linkding changes.json --revision REVIEWED_REVISION

Saved changes need service recreation to become active. Existing interpolated environment values stay under your control in .env or Compose.

Identity provider login

Selfhost can register a client with a supported provider and configure this app. Callback path: /oidc/callback/.

No administrator role is assigned by Selfhost. Check the app’s first-login policy and retain a local recovery account.

Save connection.json and replace the URLs. Supply SELFHOST_IDP_TOKEN privately in your shell.

{
  "provider": "zitadel",
  "issuer": "https://identity.example.com",
  "app_url": "https://app.example.com",
  "name": "Linkding"
}

selfhost app --directory ./linkding connect-account linkding connection.json
selfhost app --directory ./linkding connect-plan linkding connection.json
selfhost app --directory ./linkding connect linkding connection.json --revision REVIEWED_REVISION

Test sign-in in a separate browser session. HTTPS domains and HTTP loopback development origins are supported by Selfhost; the chosen app and provider must also accept the resulting callback. Provider permissions, localhost and recovery.

Database placement

This recipe supports postgres. Workspace projects can choose a dedicated database, a shared source with a separate database and account, or an existing external database before their first start.

Standalone directories use the generated Compose and environment files directly. Configure the database there before first start. Selfhost’s source provisioning commands belong to workspace projects and are optional.

Database setup, CLI commands and backups

App actions

Check application configuration · schedulable

Run Django system checks.

selfhost app --directory ./linkding action linkding check

A workspace can schedule this workflow while Selfhost runs. A standalone user can invoke it through an external scheduler. Scheduling guide.

App configuration reference

Versions and updates

This deployment uses the following images. Existing projects retain their saved recipe and images. A new catalogue version does not silently update them.

linkding: sissbruecker/linkding:1.47.0

Review compatibility and back up app data before an update. Choose an image version and review the change.

Keep control of your setup

Selfhost remains optional. Your app runs using ordinary Compose files, its own settings and persistent data. Keep the Compose project name and volumes to preserve storage. Configuration exports and setting backups do not include application data.

Standalone CLI guide · Backups and removal · Linkding documentation