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 durable application storage. Check the upstream deployment instructions and pin a release before you deploy. Source repository.

Data dependencies

The SQLite setup uses its own database file. Provide persistent local storage before starting it. Follow the selected release’s database instructions if you choose another backend.

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 louislam/uptime-kuma on port 3001.
  3. The standard SQLite setup stores state in /app/data and expects local disk with compatible locking.
  4. Use a persistent host for that setup.
  5. Check the selected release’s database and filesystem requirements before choosing any alternative.
  6. Allow WebSocket traffic through your proxy.
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. Create a monitor for an endpoint you control. Open its live view and confirm history survives a restart.