krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-07 11:58:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix: linkchecker include filter port mismatch (#2242)

Browse Source 
* initial commit; fixed anchor links on internal docs pages

* add back in absolute paths for links in code comments

* fix: update linkchecker include filter to match server port 1314

PR #1629 changed the Hugo server to port 1314 but forgot to update
the --include filter, which still matched port 1313. This caused all
links to be excluded, making the checker a no-op (0 checked, 82277 excluded).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Fix url rewrite regex so images are not impacted

* Fix links from non-documentation pages

* Fix broken links

* more broken links

* more broken links

* broken link

* Add srcset width descriptor to .lycheeignore

* Ignore URLs that contain a % character

* Anchor regex so it matches the entire URL

---------

Co-authored-by: kanungle <neil.kanungo@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
This commit is contained in:
Andrey Vasnetsov
2026-03-30 17:21:32 +02:00
committed by GitHub
co-authored by Claude Opus 4.6 kanungle Abdon Pijpelink
parent dc0080fffa
commit 1a40961d62
272 changed files with 872 additions and 879 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/migration-guidance/_index.md
+5 -5
View File
@@ -28,10 +28,10 @@ Before starting verification, you need:
This guide proposes four distinct stages of verification, each building on the next to ensure a successful migration:
1. **[Pre-Migration Baseline](/documentation/migration-verification/pre-migration-baseline/):** Before starting the migration, capture what "correct" looks like in your source system. This includes vector counts, metadata samples, collection configuration, and baseline search results. Without this, post-migration comparison is impossible. *Budget 15 to 30 minutes*.
2. **[Data Integrity](/documentation/migration-verification/data-integrity/):** After migration, verify that the data arrived intact. This layer catches missing vectors, dropped metadata fields, type coercion errors, and misconfigured collections. These checks take only minutes to run and catch the most common migration failures.
3. **[Search Quality](/documentation/migration-verification/search-quality/):** This layer catches result ranking changes, recall degradation, and relevance shifts caused by differences in indexing, quantization, or scoring between systems. *Depending on the tier you choose, this takes anywhere from 15 minutes to several hours.*
4. **[Diagnosing Discrepancies](/documentation/migration-verification/diagnosing-discrepancies/):** When any of the previous layers catches a problem, this section provides a decision tree for root-causing it: is the issue in the data or the configuration? Which vendor-specific gotcha is responsible? What's the fastest path to resolution?
1. **[Pre-Migration Baseline](/documentation/migration-guidance/pre-migration-baseline/):** Before starting the migration, capture what "correct" looks like in your source system. This includes vector counts, metadata samples, collection configuration, and baseline search results. Without this, post-migration comparison is impossible. *Budget 15 to 30 minutes*.
2. **[Data Integrity](/documentation/migration-guidance/data-integrity/):** After migration, verify that the data arrived intact. This layer catches missing vectors, dropped metadata fields, type coercion errors, and misconfigured collections. These checks take only minutes to run and catch the most common migration failures.
3. **[Search Quality](/documentation/migration-guidance/search-quality/):** This layer catches result ranking changes, recall degradation, and relevance shifts caused by differences in indexing, quantization, or scoring between systems. *Depending on the tier you choose, this takes anywhere from 15 minutes to several hours.*
4. **[Diagnosing Discrepancies](/documentation/migration-guidance/diagnosing-discrepancies/):** When any of the previous layers catches a problem, this section provides a decision tree for root-causing it: is the issue in the data or the configuration? Which vendor-specific gotcha is responsible? What's the fastest path to resolution?
## Quick Reference: Verification Checklist
@@ -65,4 +65,4 @@ DISCREPANCY DIAGNOSIS (if checks fail)
---
**Next:** [Pre-Migration Baseline](/documentation/migration-verification/pre-migration-baseline/)
**Next:** [Pre-Migration Baseline](/documentation/migration-guidance/pre-migration-baseline/)