From b083a1ab4f97e0d864e5fdb59e109f5d0514114c Mon Sep 17 00:00:00 2001 From: Nick Sweeting Date: Fri, 10 May 2024 15:29:46 -0700 Subject: [PATCH] Updated Setting up Search (markdown) --- Setting-up-Search.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Setting-up-Search.md b/Setting-up-Search.md index 1eb2d99..e8ee920 100644 --- a/Setting-up-Search.md +++ b/Setting-up-Search.md @@ -39,7 +39,7 @@ archivebox config --get SEARCH_BACKEND_ENGINE By default out-of-the-box, the selected engine is a simple but efficient tool similar to `grep -r` called [`ripgrep`](https://github.com/BurntSushi/ripgrep). -Ripgrep is currently the [fastest available](https://blog.burntsushi.net/ripgrep/) *filesystem search* tool that scans over the raw disk bytes on every search. We chose it as the default so that beginners and 95% of users with small collections can have an experience that "just works", without needing to install and maintain complex additional dependencies or background workers. +Ripgrep is [currently the fastest](https://blog.burntsushi.net/ripgrep/) available *filesystem search* tool that scans over the raw disk bytes on every search. We chose it as the default so that beginners and 95% of users with small collections can have an experience that "just works", without needing to install and maintain complex additional dependencies or background workers. However, there are some fundamental limitations of scanning through every file on disk each time a search is done, so ArchiveBox provides a number of additional search backend options for when users outgrow `ripgrep`.