chore: hardcode registry URL and clean up readme

docker-compose no longer needs REGISTRY_URL env var.
README now uses the actual registry host throughout.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

README.md

@@ -74,10 +74,10 @@ The app uses Next.js standalone output. The SQLite database is stored in a Docke
 docker compose up --build
 ```
 
-Or pull from the registry:
+Or pull from the registry and run:
 
 ```bash
-REGISTRY_URL=your.registry.host docker compose up
+docker compose up
 ```
 
 #### Seed the database inside the container
@@ -96,11 +96,11 @@ Or as one-off containers against the named volume:
 
 ```bash
 docker run --rm -v sixflagssupercalendar_park_data:/app/data \
-  your.registry.host/josh/sixflagssupercalendar:latest \
+  gitea.thewrightserver.net/josh/sixflagssupercalendar:latest \
   npm run discover
 
 docker run --rm -v sixflagssupercalendar_park_data:/app/data \
-  your.registry.host/josh/sixflagssupercalendar:latest \
+  gitea.thewrightserver.net/josh/sixflagssupercalendar:latest \
   npm run scrape
 ```
 
@@ -132,7 +132,7 @@ The registry host is derived automatically from `gitea.server_url` — no `REGIS
 
 ```bash
 git remote add origin https://gitea.thewrightserver.net/josh/SixFlagsSuperCalendar.git
-git push -u origin master
+git push -u origin main
 ```
 
 ---

docker-compose.yml

@@ -1,6 +1,6 @@
 services:
   web:
-    image: ${REGISTRY_URL:-gitea.thewrightserver.net}/josh/sixflagssupercalendar:latest
+    image: gitea.thewrightserver.net/josh/sixflagssupercalendar:latest
     build:
       context: .
       dockerfile: Dockerfile