Skip to main content

Deploy with an agent

Copy agent prompt

Before you start

Connect your AWS account using the Spring Winter quickstart. You need a durable database and storage for file-backed features. Check the upstream deployment instructions and pin a release before you deploy. Source repository.

Create and connect the database

  1. Create a private SQL database 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 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 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.