Update examples

Signed-off-by: Michael Yuan <michael@secondstate.io>

Author: juntao

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "echokit_server"
-version = "0.3.0"
+version = "0.3.2"
 edition = "2024"
 
 [dependencies]

Cargo.toml

@@ -7,9 +7,6 @@ url = "https://api.openai.com/v1/audio/transcriptions"
 api_key = "sk_ABCD"
 model = "gpt-4o-mini-transcribe"
 lang = "en"
-# Optional: requires a local Silero VAD server: https://github.com/second-state/silero_vad_server
-vad_url = "http://localhost:9093/v1/audio/vad"
-# vad_realtime_url = "ws://localhost:9093/v1/audio/realtime_vad"
 
 [tts]
 platform = "openai"
@@ -34,4 +31,4 @@ You are a helpful assistant. Answer truthfully and concisely. Always answer in E
 - NEVER use tables
 - Answer in complete English sentences as if you are in a conversation.
 
-"""
+"""

config.toml

@@ -1,39 +1,49 @@
 This doc guides you through building and deploying the echokit_server container to Fly.io.
 
 ## Prerequisites
+
 - flyctl installed: see https://github.com/superfly/flyctl
 - Docker installed and running locally
 - A unique Fly app name (Fly app names are globally unique)
 
 ## 1) Create the Fly app
+
 ```bash
 fly app create --name echokit-server-[something-unique]
 ```
 
 ## 2) Build the Docker image
-From the server-vad directory, ensure `config.toml` is valid, then build:
+
+From the `server` directory, ensure `config.toml` is valid, then build:
+
 ```bash
-cd server-vad
+cd ../server
 docker build -t registry.fly.io/[your_app_name]:tag .
 ```
 
 ## 3) Push the image to Fly
+
 Authenticate to the Fly registry and push the image:
+
 ```bash
 fly auth docker
 docker push registry.fly.io/[your_app_name]:tag
 ```
 
 ## 4) Configure Fly to use the image
+
 Update `fly.toml` to point to `registry.fly.io/[your_app_name]:tag`.
 
 ## 5) Deploy
-From the `docker` directory:
+
+From the `docker/fly` directory:
+
 ```bash
 fly deploy
 ```
 
 ## Managing machines
+
 - Deploy creates two machines in the same region by default. Remove one if you only need a single instance:
   ```bash
   fly machine list           # get machine IDs

docker/README.md docker/fly/README.mddocker/README.md renamed to docker/fly/README.md

@@ -13,28 +13,20 @@ docker run --rm \
   -p 8080:8080 \
   -v $(pwd)/config.toml:/app/config.toml \
   -v $(pwd)/record:/app/record \
-  secondstate/echokit:latest-server
+  secondstate/echokit:latest
 ```
 
 Mount your `config.toml` directly into `/app/config.toml`. If you need to override additional assets such as `hello.wav`, mount them individually alongside the config file. The server writes any generated artifacts to `/app/record`, so ensure the `record` directory exists locally and is writable. The container executes `echokit_server config.toml` by default, reading logs at the `info` level.
 
 ## Build
 
-```sh
-docker build -t secondstate/echokit:latest-server .
-```
-
-The build automatically selects the correct release artifact for your build architecture using the BuildKit-provided `TARGETPLATFORM`/`TARGETARCH` arguments. Override the downloaded release by supplying `--build-arg ECHOKIT_VERSION=<version>` (for example `0.1.1`) if you want a different tag.
-
-## Multi-platform build
-
 Use Buildx to produce and publish a multi-arch manifest in one command. BuildKit injects `TARGETPLATFORM` (`linux/amd64`, `linux/arm64`, etc.), so you do not need to set them manually.
 
 ```sh
 docker buildx build \
   --platform linux/amd64,linux/arm64 \
-  --build-arg ECHOKIT_VERSION=0.1.1 \
-  --tag secondstate/echokit:latest-server \
+  --build-arg ECHOKIT_VERSION=0.3.1 \
+  --tag secondstate/echokit:latest \
   .
 ```
 
@@ -44,5 +36,5 @@ Adjust `ECHOKIT_VERSION` as needed; omit the flag to fall back to the default ve
 
 ```sh
 docker login
-docker push secondstate/echokit:latest-server
+docker push secondstate/echokit:latest
 ```