docs: fix volume name to root_park_data
All checks were successful
Build and Deploy / Build & Push (push) Successful in 56s
All checks were successful
Build and Deploy / Build & Push (push) Successful in 56s
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -120,7 +120,7 @@ docker pull gitea.thewrightserver.net/josh/sixflagssupercalendar:scraper
|
||||
This one-time step opens a headless browser for each park to find its internal Six Flags API ID. Run it against the scraper image so Playwright is available:
|
||||
|
||||
```bash
|
||||
docker run --rm -v thoosie_park_data:/app/data \
|
||||
docker run --rm -v root_park_data:/app/data \
|
||||
gitea.thewrightserver.net/josh/sixflagssupercalendar:scraper \
|
||||
npm run discover
|
||||
```
|
||||
@@ -130,14 +130,14 @@ docker run --rm -v thoosie_park_data:/app/data \
|
||||
Open `data/park-meta.json` in the Docker volume and set `rcdb_id` for each park to the numeric ID from the RCDB URL (e.g. `https://rcdb.com/4529.htm` → `4529`). You can curl it directly from the repo:
|
||||
|
||||
```bash
|
||||
curl -o /var/lib/docker/volumes/thoosie_park_data/_data/park-meta.json \
|
||||
curl -o /var/lib/docker/volumes/root_park_data/_data/park-meta.json \
|
||||
https://gitea.thewrightserver.net/josh/SixFlagsSuperCalendar/raw/branch/main/data/park-meta.json
|
||||
```
|
||||
|
||||
**4. Run the initial scrape**
|
||||
|
||||
```bash
|
||||
docker run --rm -v thoosie_park_data:/app/data \
|
||||
docker run --rm -v root_park_data:/app/data \
|
||||
gitea.thewrightserver.net/josh/sixflagssupercalendar:scraper \
|
||||
npm run scrape
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user