tiennm99/thptqg2017

0 Fork 0

mirror of https://github.com/tiennm99/thptqg2017.git synced 2026-10-03 09:13:53 +00:00

Files

T

tiennm99 ceb694a747 refactor: split into web/crawler/go-parser and drop the 2017 archives

Move the frontend into web/, the repo's only npm workspace, and replace the
JS crawler with a Go module covering both remaining datasets. The crawler
writes to a .part file and renames on completion: writing straight to the
destination left truncated files that the skip-if-present check would then
skip forever.

Remove the 2017-old and 2017-old2 datasets. They were successive publications
of the same exam, kept side by side so the disagreement stayed inspectable;
the current 2017 supersedes them and they remain in git history.

Recover the 2016 crawler source from the Internet Archive's copy of the
aggregator article, whose original host no longer resolves. All 119 filenames
are verified against data/2016 in both directions, but no archive captured the
spreadsheets themselves, so the host still serving them is unconfirmed and
data/2016 remains the only confirmed copy.

Filenames are load-bearing throughout: go-parser sorts inputs bytewise and
inserts last-wins, so they decide which row survives a duplicate exam number.

2026-08-13 21:45:05 +07:00

4.0 KiB

Raw Blame History

Deployment Guide

Deploys to GitHub Pages via .github/workflows/deploy-pages.yml. Every push to main rebuilds both datasets and redeploys the whole site.

One-time setup: Settings → Pages → Source: GitHub Actions.

What the workflow does

Checkout, Go toolchain, Node 24, npm ci
npm run build:go — one parser binary
npm run build:db — builds and gzips both databases into .build/public/db/
npm run build:site — one Vite build, then web/scripts/assemble-site.js
actions/upload-pages-artifact + actions/deploy-pages

The database build dominates the runtime: roughly 419 MB of Excel is parsed on every deploy.

Resulting URLs

https://<user>.github.io/thptqg/
https://<user>.github.io/thptqg/2016/
https://<user>.github.io/thptqg/2017/

/thptqg/2017/old/ and /thptqg/2017/old2/ were the pre-flattening URLs for the two removed 2017 archives. They are no longer served; like any unknown path they now render the hub via 404.html.

Local reproduction

npm ci
npm run build:go
npm run build:db      # both; pass an id to build just one
npm run build:site    # vite build + assemble into _site/
npx serve _site

To rebuild a single dataset:

npm run build:db 2017

Base path

vite.config.js sets base: "/thptqg/". If you fork under a different repo name, update it to match — assets are referenced absolutely, so a mismatch shows up as a blank page with 404s on /assets/....

Adding a dataset

Put the Excel files in data/<id>/
Add go-parser/configs/<id>.yml with the parse rules — sheet mode, column indices, SBD validation, header tokens, blank-row stripping. No SQL: the schema is canonical and lives in go-parser/internal/schema/schema.go
Add an entry to DATASETS in web/src/datasets.js

Nothing else. The build script, the site assembly and the router all read that one list, and the frontend adapts to whichever columns the dataset populates.

Why no uncompressed database can ship

build-db.js runs gzip -9 without -k, so the raw file does not survive the build. assemble-site.js then fails the job if any .db, .db-journal, .db-wal or .db-shm reached the output.

Both guards exist because the previous pipeline wrote a 100+ MB uncompressed database into the source tree and relied on an rm step to keep it out of the artifact — one missing line away from publishing it.

Notes

The gzipped database is not cacheable across deploys. Every rebuild produces a different .db.gz, because SQLite does not lay pages out deterministically. First-visit users pay the full download; later visits hit browser cache until the next deploy.
GitHub Pages caps individual files at 100 MB. The largest gzipped database is about 48 MB. Uncompressed they run 135–234 MB and would not fit — which is why the browser decompresses via DecompressionStream.
No server-side compression is assumed. The app fetches the .gz bytes directly rather than relying on Content-Encoding: gzip; Pages does not reliably compress arbitrary paths on the fly.
Total artifact is about 177 MB, well inside the 1 GB site limit.

Rollback

Deploys are stateless snapshots. Revert the commit on main and push; the next run rebuilds the older state. There is no data to migrate.

Troubleshooting

Symptom	Typical cause
Blank page, 404 on assets	`base` in `vite.config.js` does not match the repo name
`Failed to fetch database: 404`	Dataset id in `web/src/datasets.js` does not match the file in `db/`
A route 404s	`assemble-site.js` did not run, or the id is missing from `DATASETS`
WASM fails to load	`sql.js.org` unreachable — self-host `sql-wasm.wasm` and update `SQL_WASM_URL` in `use-sqlite.js`
Deploy fails on assembly	An uncompressed database artefact reached the output; the error names the files
Missing rows after a data update	Unknown Excel header — check the per-file row counts the parser prints

4.0 KiB Raw Blame History Unescape Escape