Maxim Dolgolyov
1a347650f4
A. textbook-tracker.js: первый клик по .para-pill теперь автоматически
помечает параграф как прочитанный. «Прочитано» = «открыто». Сразу
даёт осмысленный счётчик для chemistry-9 и physics-9 в каталоге.
Slug fallback: physics8_* → physics-8-* (корректный слаг).
B. Физика 8 — миграция 015:
- 3 children: physics-8-thermal / electro / optics с parent_slug
- parent физики-8 обновлён: para_count=40, описание трёх разделов
- sub-файлы получили textbook-tracker.js + правильный слаг
- physics_8.html переписана в стиле algebra_8_hub: 3 цветные
карточки, агрегированный прогресс, ачивка «Эксперт физики 8»
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Versioned migrations
Each schema change is a separate .sql file, applied in alphabetical order.
Applied files are tracked in the _migrations table.
Applying migrations
npm run migrate # apply pending migrations (safe to re-run)
npm run migrate:bootstrap # mark 000_baseline.sql as applied on existing DB (run ONCE per env)
npm run migrate:legacy # run legacy migrate.js (kept for reference, do not use)
Naming convention
NNN_short_description.sql
Examples: 001_add_user_avatar.sql, 002_drop_unused_columns.sql
To find the next number:
ls backend/src/db/migrations/*.sql | sort -r | head -1
Rules
- Never edit a migration file after it has been committed and deployed.
- To revert: write a new migration that undoes the change.
- Each file must be valid SQLite SQL (not PostgreSQL — no SERIAL, no EXTENSION).
- Use
IF NOT EXISTS/IF EXISTSwhere possible for safety. - Test on a copy of the prod DB before deploying.
Deploy order (first time on a new environment)
npm run migrate:legacy # initialize full schema (existing init script)
npm run seed:permissions # seed default permissions and achievements
npm run migrate:bootstrap # mark 000_baseline.sql as applied
npm run migrate # apply any newer migrations (should say "nothing to apply")
npm start
Adding a new migration
# 1. Create the file
echo "ALTER TABLE users ADD COLUMN avatar_url TEXT;" > backend/src/db/migrations/001_add_avatar_url.sql
# 2. Apply and verify
npm run migrate
# 3. Commit
git add backend/src/db/migrations/001_add_avatar_url.sql
git commit -m "db: add avatar_url column to users"
Files
| File | Description |
|---|---|
000_baseline.sql |
Snapshot of full schema as of 2026-05-06. Never runs on existing DBs. |