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 files if you enable message caching, users or attachments. Check the upstream deployment instructions and pin a release before you deploy. Source repository.

Data dependencies

The standard setup needs no Spring Winter SQL resource. Configure persistent local files first if you enable authentication, message caching or attachments.

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 binwiederhier/ntfy on port 80 with the documented serve command.
  3. Configure the public base URL and access rules in server configuration.
  4. Use /v1/health for a health check.
  5. Start with authenticated access for private topics.
  6. Plan persistent storage for the cache, authentication database and attachments where enabled.
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 and publish to a test topic. Verify receipt and check that an anonymous request cannot use a private topic.