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 and durable storage for uploaded files if enabled. 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 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 DATABASE_URL to the writer. Check the pinned release for required PostgreSQL extensions, a Redis-compatible cache, and any extra database or service such as the authorization store. Give each migration and runtime process access to its own configured database. Put secret values in runtime configuration or the migration process’s secret store.
  4. Run Formbricks migrations first. If the release includes Hub, run Hub migrations next, then start the required services and workers in the release’s documented dependency order.

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 the Formbricks image and runtime settings from the pinned self-hosted release.
  3. Configure DATABASE_URL, WEBAPP_URL, NEXTAUTH_URL and the authentication and encryption secrets required in its deployment template.
  4. Configure HTTPS callbacks, email if required and the supported storage adapter for uploads.
  5. Check whether your release includes Hub and Cube in its baseline deployment.
  6. If it does, provide reachable services for both and use the release’s documented connection settings.
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 and publish a test survey, submit a response and confirm it appears in results.