RugMunchMedia/pryscraper
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(db): add Alembic migrations #6

Merged
cryptorugmunch merged 4 commits from feat/sql-migration-top3 into main 2026-07-03 02:22:34 +02:00
Conversation 0 Commits 4 Files changed 25 +2077 -408
cryptorugmunch commented 2026-07-03 02:10:26 +02:00
Owner
Copy link

Add Alembic for versioned database migrations.

  • Add alembic to dev deps and requirements.txt
  • Initialize alembic/ config with SQLite + Postgres support
  • Create 0001_initial_schema migration covering all 26 models
  • Add db.run_migrations() helper and CLI command
  • Add docker-entrypoint.sh to run FAILED: No 'script_location' key found in configuration. before start
  • Keep Base.metadata.create_all() for backward compatibility
  • Add tests verifying alembic current and upgrade head work

CI: lint, typecheck, test, gitleaks, bandit expected to pass.

Add Alembic for versioned database migrations. - Add alembic to dev deps and requirements.txt - Initialize alembic/ config with SQLite + Postgres support - Create 0001_initial_schema migration covering all 26 models - Add db.run_migrations() helper and CLI command - Add docker-entrypoint.sh to run FAILED: No 'script_location' key found in configuration. before start - Keep Base.metadata.create_all() for backward compatibility - Add tests verifying alembic current and upgrade head work CI: lint, typecheck, test, gitleaks, bandit expected to pass.
cryptorugmunch added 3 commits 2026-07-03 02:10:26 +02:00 
- Split scraping endpoints from api.py into routers/scraping.py
- Split template endpoints into routers/templates.py with POST /v1/templates/batch
- Introduce deps.py for shared singleton instances
- Add e2e tests for scraping, templates, auth, and Apify schema (23 new tests)
- Add reusable Apify actor input/output schema builder (apify_schema.py)
- Add PRY_API_KEY startup warning and deploy key to Talos /srv/pry/.env
- Register /v1/templates/batch as paid x402 operation
feat(db): add Alembic migrations for versioned schema changes
Some checks failed
CI / Secret scan (gitleaks) (pull_request) Successful in 1m4s
Details
CI / test (pull_request) Successful in 1m10s
Details
CI / Security audit (bandit) (pull_request) Successful in 33s
Details
CI / typecheck (pull_request) Failing after 1m41s
Details
CI / lint (pull_request) Failing after 1m48s
Details
8731fee018
cryptorugmunch added 1 commit 2026-07-03 02:17:40 +02:00
style: format phase0 router split and fix mypy fixture types
All checks were successful
CI / test (pull_request) Successful in 1m13s
Details
CI / Security audit (bandit) (pull_request) Successful in 34s
Details
CI / lint (pull_request) Successful in 49s
Details
CI / typecheck (pull_request) Successful in 54s
Details
CI / Secret scan (gitleaks) (pull_request) Successful in 31s
Details
250f6041b3
cryptorugmunch merged commit 07288a01d7 into main 2026-07-03 02:22:34 +02:00
cryptorugmunch deleted branch feat/sql-migration-top3 2026-07-03 02:22:34 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: RugMunchMedia/pryscraper#6
No description provided.
Delete branch "feat/sql-migration-top3"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?