Uses the pre built container

README.md

@@ -20,13 +20,12 @@ The server is maintained separately. This repo contains only the egg client.
 
 ## Run an Egg
 
-One Docker command is all it takes:
+Clone the repo and use Docker Compose — it pulls the pre-built image from the registry automatically:
 
 ```bash
-docker run -d --restart unless-stopped \
-  -e SERVER_URL=https://your-domain.com \
-  -v gcp_egg_data:/data \
-  git.hexadual.io/rocobo/gcp-dot-egg:latest
+git clone https://git.hexadual.io/rocobo/GCP-Dot.git
+cd GCP-Dot
+SERVER_URL=https://your-domain.com docker compose up -d
 ```
 
 The egg will immediately start sending one trial per second and persist its ID across restarts.
@@ -40,25 +39,16 @@ The egg will immediately start sending one trial per second and persist its ID a
 
 The auto-generated ID is derived from a SHA-256 hash stored at `/data/egg_id` — mount a volume there to keep it stable across restarts.
 
-## Build from Source
-
-```bash
-docker build -t gcp-egg .
-docker run -d --restart unless-stopped \
-  -e SERVER_URL=https://your-domain.com \
-  -v gcp_egg_data:/data \
-  gcp-egg
-```
-
 ## Project Structure
 
 ```
 GCP/
-├── egg.py             # Egg client — all logic (~70 lines)
-├── requirements.txt   # requests==2.31.0
+├── egg.py               # Egg client — all logic (~70 lines)
+├── requirements.txt     # requests==2.31.0
 ├── Dockerfile
+├── docker-compose.yml
 └── .gitea/workflows/
-    └── docker.yml     # CI: builds and pushes egg image on every push to main
+    └── docker.yml       # CI: builds and pushes egg image on every push to main
 ```
 
 ## Published Images
@@ -68,7 +58,6 @@ Every push to `main` builds and publishes to the Gitea container registry via Gi
 | Image | Pull |
 |---|---|
 | Egg | `docker pull git.hexadual.io/rocobo/gcp-dot-egg:latest` |
-| Server | `docker pull git.hexadual.io/rocobo/gcp-dot-server:latest` |
 
 ## How the Analysis Works