Conversation
Resolves #61 Previously there was a single global "use hardlinks" toggle. Now ebooks and audiobooks each have their own setting, allowing e.g. copying ebooks (so metadata can be written before sending to an eReader) while still hardlinking audiobooks. - Backend: add use_hardlinks_ebook / use_hardlinks_audiobook to DownloadPathsResponse and DownloadPathsUpdate in settings.py - Backend: orchestrator checks format-specific key first (use_hardlinks_ebook or use_hardlinks_audiobook), falling back to the global use_hardlinks for existing deployments - Frontend: replace single toggle with two per-format toggles in Settings - Frontend: api.ts types updated accordingly
Users can now link their own Hardcover API token and configure which sources to watch (to-read status and/or custom lists). A background job (every 6h) auto-requests any new books found for all enabled users. - Add UserHardcoverSync model and migration (036) - Add /api/hardcover-sync router (GET/PUT config, GET lists, POST run) - Add sync_hardcover_lists and sync_hardcover_lists_for_user tasks - Register sync_hardcover_lists as a scheduled job (6h default) - Respects per-user permissions and auto-approve settings - Frontend: Hardcover Sync card on Profile page with token input, toggles for to-read/lists, format preference, and manual sync button
Users no longer need to re-enter the app-wide Hardcover API token on their profile. The sync feature uses the global token automatically and shows 'Using app-wide Hardcover token' in the UI. A personal token is still accepted as an optional override for multi-user setups where different users have different Hardcover accounts.
feat: Per-user Hardcover list/status sync (issue #60)
feat: Per-format hardlink settings for ebooks and audiobooks
… migration
Two pairs of migration files shared the same revision ID ('031' and '032').
Alembic fails with a duplicate-revision error when it loads the versions
directory, causing `alembic upgrade heads` to exit early. The entrypoint's
`|| echo WARNING` catch silently swallowed this failure, so migration 035
(which adds the `users.oidc_subject` column) never ran — producing the
`UndefinedColumn: users.oidc_subject` crash in production.
Fixes:
- 031_add_direct_download_settings: revision '031' → '031b'
- 032_add_library_mapping_to_booklore_servers: revision '032' → '032b'
- 032_add_flaresolverr_url: down_revision '031' → '031b'
- 034_merge_heads: down_revision includes all four branch heads
('031', '031b', '032b', '033')
- 035_add_oidc_fields: made idempotent (checks column/index existence)
- entrypoint.sh: detect legacy untracked databases and stamp at the
correct revision; fail loudly on migration errors instead of masking them
fix: resolve duplicate Alembic revision IDs causing missing oidc_subject column
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.