mirror of
https://github.com/qdrant/landing_page.git
synced 2026-10-05 19:08:32 +02:00
fix: linkchecker include filter port mismatch (#2242)
* 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:
co-authored by
Claude Opus 4.6
kanungle
Abdon Pijpelink
parent
dc0080fffa
commit
1a40961d62
@@ -25,7 +25,7 @@ set up your cluster, as described in the following sections:
|
||||
|
||||
- [Create a cluster](/documentation/cloud/create-cluster/)
|
||||
- Set up [Authentication](/documentation/cloud/authentication/)
|
||||
- Configure one or more [Collections](/documentation/concepts/collections/)
|
||||
- Configure one or more [Collections](/documentation/manage-data/collections/)
|
||||
|
||||
## Automatic Backups
|
||||
|
||||
@@ -71,7 +71,7 @@ Or you can restore the backup into a new cluster.
|
||||
|
||||
Qdrant also offers a snapshot API which allows you to create a snapshot
|
||||
of a specific collection or your entire cluster. For more information, see our
|
||||
[snapshot documentation](/documentation/concepts/snapshots/).
|
||||
[snapshot documentation](/documentation/operations/snapshots/).
|
||||
|
||||
Here is how you can take a snapshot and recover a collection:
|
||||
|
||||
@@ -79,11 +79,11 @@ Here is how you can take a snapshot and recover a collection:
|
||||
- For a single node cluster, call the snapshot endpoint on the exposed URL.
|
||||
- For a multi node cluster call a snapshot on each node of the collection.
|
||||
Specifically, prepend `node-{num}-` to your cluster URL.
|
||||
Then call the [snapshot endpoint](/documentation/concepts/snapshots/#create-snapshot) on the individual hosts. Start with node 0.
|
||||
Then call the [snapshot endpoint](/documentation/operations/snapshots/#create-snapshot) on the individual hosts. Start with node 0.
|
||||
- In the response, you'll see the name of the snapshot.
|
||||
2. Delete and recreate the collection.
|
||||
3. Recover the snapshot:
|
||||
- Call the [recover endpoint](/documentation/concepts/snapshots/#recover-in-cluster-deployment). Set a location which points to the snapshot file (`file:///qdrant/snapshots/{collection_name}/{snapshot_file_name}`) for each host.
|
||||
- Call the [recover endpoint](/documentation/operations/snapshots/#recover-in-cluster-deployment). Set a location which points to the snapshot file (`file:///qdrant/snapshots/{collection_name}/{snapshot_file_name}`) for each host.
|
||||
|
||||
## Backup Considerations
|
||||
|
||||
|
||||
Reference in New Issue
Block a user