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 mySQL and durable wp-content. 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 MySQL. 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 WORDPRESS_DB_HOST, WORDPRESS_DB_NAME, WORDPRESS_DB_USER and WORDPRESS_DB_PASSWORD. Configure durable wp-content storage for the chosen hosting layout. Put secret values in runtime configuration or the migration process’s secret store.
  4. Start WordPress, then complete the browser installer to initialize the tables.

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 the official wordpress Apache image on port 80.
  3. Set WORDPRESS_DB_HOST, WORDPRESS_DB_USER, WORDPRESS_DB_PASSWORD and WORDPRESS_DB_NAME.
  4. Choose durable storage for uploads, themes and plugins.
  5. The standard writable installation needs a persistent filesystem.
  6. An immutable image also needs an explicitly configured and tested strategy for offloading uploads and managing updates.
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. Publish a test post with media and verify the post and media after replacing the container.