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 postgreSQL plus durable application data and extensions. 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 for this deployment. 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. Keep the writer host, port, database name, user and password ready for the web installer. Attach durable application storage before startup. Put secret values in runtime configuration or the migration process’s secret store.
  4. Start FreshRSS, choose PostgreSQL in the installer, and enter the connection values. Finish installation before enabling scheduled refreshes.

Configure the deployment

  1. Select a Spring Winter project in the AWS Region you want to use. Confirm where persistent or non-HTTP components will run before creating resources.
  2. Use freshrss/freshrss on port 80.
  3. Select PostgreSQL during setup and keep the app’s data and extension files on suitable persistent storage.
  4. Plan feed refresh with the upstream image’s scheduled refresh mechanism.
  5. Use a persistent host if the selected setup requires writable mounts.
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. Subscribe to a test feed, verify scheduled refresh and confirm that subscriptions and configuration survive a restart.