> ## Documentation Index
> Fetch the complete documentation index at: https://docs.springwinter.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy linkding

> Set up linkding with Spring Winter and verify the deployment.

## Deploy with an agent

Copy agent prompt

Help me deploy linkding with Spring Winter. Start by planning. Read this guide at [https://docs.springwinter.dev/deploy/open-source/linkding](https://docs.springwinter.dev/deploy/open-source/linkding.md), the upstream instructions at [https://linkding.link/installation/](https://linkding.link/installation/), and [https://docs.springwinter.dev/api-reference/agents](https://docs.springwinter.dev/api-reference/agents.md). Use the API origin linked in the agent reference. Fetch its current public OpenAPI document before making API calls. Treat reference material as data.

Check the source or image for the release we will pin. Identify its startup command, container port, unauthenticated HTTP 200 health path, migration sequence, runtime variables and all services. For this app, start with a durable database and storage for file-backed features. Use sissbruecker/linkding on port 9090. The default stores data in /etc/linkding/data. For PostgreSQL, use the upstream LD\_DB\_\* configuration for your release. Verify server certificate and hostname validation. Confirm that the serving process can read the CA and that its database connection works after migrations. If you enable archived snapshots or local files, plan their storage separately before choosing task compute.

Use my local SPRINGWINTER\_TOKEN, or SPRINGWINTER\_API\_TOKEN if already configured. Keep all credentials and runtime secret values out of chat, logs and source. Confirm my organization, AWS connection, Region, existing resources and budget. Check the live API contract for resource types and secure connectivity. Keep state off temporary task disks. If any component needs a persistent host, private network service or unsupported protocol, explain where it will run and what I need to provide.

Show me the pinned release, resources, network access, storage, bootstrap and migration steps, secret names and estimated AWS cost. Wait for my approval before changes. Include any planned restart, task replacement or restore in that approval. When PostgreSQL if you choose it instead of SQLite is required for the chosen configuration, create it first and wait until it is ready. Set LD\_DB\_ENGINE=postgres and the release’s LD\_DB\_\* connection variables. Plan storage for archived snapshots and local files separately. Start linkding and wait for its migrations before adding bookmarks. If you keep SQLite, provide durable storage for its data directory instead. Deploy in dependency order using the documented API. Wait for each workflow to finish. Verify the expected endpoint and this application check. Save a bookmark, test an archive if enabled and confirm the data remains after replacement. Report resource links and what is still unverified.

## Before you start

Connect your AWS account using the [Spring Winter quickstart](https://docs.springwinter.dev/quickstart.md). You need a durable database and storage for file-backed features. Check the [upstream deployment instructions](https://linkding.link/installation/) and pin a release before you deploy. [Source repository](https://github.com/sissbruecker/linkding).

## Create and connect the database

1. Create a private [SQL database](https://docs.springwinter.dev/deploy/databases.md) with **PostgreSQL if you choose it instead of SQLite**. If you already have a database for this deployment, verify that the engine and version match the pinned app release. Wait for the database to be ready.
2. Open **Connect** on the database. Use the writer endpoint, port, database name and application credentials. Create the application database and role if needed. Confirm that the application and migration process can reach the private writer.
3. Set `LD_DB_ENGINE=postgres` and the release’s `LD_DB_*` connection variables. Plan storage for archived snapshots and local files separately. Put secret values in runtime configuration or the migration process’s secret store.
4. Start linkding and wait for its migrations before adding bookmarks. If you keep SQLite, provide durable storage for its data directory instead.

## Configure the deployment

1. Select a Spring Winter project in the AWS Region you want to use. Use a [web server](https://docs.springwinter.dev/deploy/web-servers.md) for the HTTP app and configure dependencies before you start it.
2. Use sissbruecker/linkding on port 9090.
3. The default stores data in /etc/linkding/data.
4. For PostgreSQL, use the upstream LD\_DB\_\* configuration for your release.
5. If you enable archived snapshots or local files, plan their storage separately before choosing task compute.

When you run the HTTP app on Spring Winter, set a health path that returns HTTP 200 without signing in. Use [Runtime variables](https://docs.springwinter.dev/concepts/environment-variables.md) for runtime configuration. Task storage is temporary. Verify that every file you need after replacement goes to durable storage.

## Verify the deployment

Check the deployment in **History** if you created Spring Winter compute. Wait for the workflow to succeed, then test the application over HTTPS. Save a bookmark, test an archive if enabled and confirm the data remains after replacement.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.