How to redeploy after changing an AI-built app · Ample Computer

How to redeploy after changing an AI-built app

Release source or configuration changes with Ample, understand unchanged no-op deploys, and inspect failures before retrying.

the short version

After changing an AI-built app, run the same Ample deploy workflow again. Ample hashes the packaged files, build configuration, and environment, then compares them with the live release. A real change creates a new release. No change returns unchanged: true and the current live URL without rebuilding.

Who this is for

This guide is for builders shipping a second or later version of an app that is already live on Ample.

How to do it

  1. Make and verify the change. Ask the coding agent to run the smallest relevant local check before deployment. Commit the change if that is part of your repo workflow.

  2. Reuse the recorded plan. If the repo has ample.toml, keep it aligned with any service, database, volume, domain, or environment changes.

  3. Deploy once. For a single service, run ample deploy. For a planned multi-service topology, run ample up so dependencies are applied in order.

   $ ample deploy
  1. Read unchanged correctly. An unchanged result is a successful no-op. It means the live release already matches the packaged content and deployment configuration.

  2. Force only for intentional reactivation. Use force when unchanged source must be rebuilt and reactivated, such as recovering a live release that is misbehaving at runtime.

   $ ample deploy --force

What this supports

Know the limits

Common failure modes