# Configure build and start for Echo

Build and start for an Echo app on Ample. Verified on Echo: the app built and started with the documented commands and answered on its public HTTPS URL. Build and start: `CGO_ENABLED=0 go build -o app ./...` then `./app` on the ubuntu-24.04 template (go.sum committed for a reproducible build).

---

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

---

## You need

- An Echo project (`CGO_ENABLED=0 go build -o app ./...` then `./app` on the ubuntu-24.04 template (go.sum committed for a reproducible build))
- An Ample account token with `servers:write`

---

## Exact tested configuration

- `build CGO_ENABLED=0 go build -o app ./...`
- `runtime go`
- `sizes - 1vcpu - 1gb`
- `start ./app`
- `template ubuntu-24.04`

---

## Steps

1.  **Build and start.** `CGO_ENABLED=0 go build -o app ./...` then `./app` on the ubuntu-24.04 template (go.sum committed for a reproducible build); the server must bind 0.0.0.0 on PORT.

2.  **Deploy.** Run the synchronous deploy once and read the result.
   
   ```
   $ ample deploy . --name <app-name> --public
   ```

3.  **Verify.** Fetch the live URL on the example; on failure read the build and runtime logs.
   
   ```
   $ ample logs <deployment_id> --kind build
   ```

---

## How it was checked

✓ app responds on its public URL· `http get/` → “ample canary echo patterns”

---

## Evidence

1. November 6, 2026 · canary run  
  Echo pattern fixture deployed on Ample (`CGO_ENABLED=0 go build -o app ./...` then `./app` on the ubuntu-24.04 template (go.sum committed for a reproducible build)); for this guide: the app built and started with the documented commands and answered on its public HTTPS URL.

---

## Tested examples

- **Echo pattern fixture.** Verified build and start on Echo.

---

## What it doesn’t cover

- Verified on the ubuntu-24.04 template at s-1vcpu-1gb.
