diff options
| -rw-r--r-- | content/blog/web-search-homepage.md | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/content/blog/web-search-homepage.md b/content/blog/web-search-homepage.md index d060a0a..a3a1cc3 100644 --- a/content/blog/web-search-homepage.md +++ b/content/blog/web-search-homepage.md @@ -121,7 +121,7 @@ how Strus should analyze and index the documents: post = /posts/post; ``` -which means split on the XPath expession `/posts/post`. +which means split on the XPath expression `/posts/post`. ``` [Content] @@ -173,7 +173,7 @@ we can present a selection of them (usually a sentence containing the matches) in the rank list. Finally, we need to count the number of words per document, -this is needed or the retrieval function: +this is needed for the retrieval function: ``` [Aggregator] @@ -218,12 +218,13 @@ strusWebService (with JSON on HTTP). This leads to the problem of CORS (Cross-Origin-Requests) which have to be configured in the strusWebService (which must allow requests originating from the server which -delivered the static HTML page generated with Hugo. +delivered the static HTML page generated with Hugo). Also I had to stem and lowercase the query terms with a [Snowball Javascript library](https://github.com/fortnightlabs/snowball-js) as the strusWebService doens't support query analysis right now. + ## Workflow So, when I change or add a page in to my website I have to run: @@ -257,6 +258,10 @@ The upload to the remote webserver can be done more elegantly. One idea is to use the backup/replication API of strus for this: build an index locally and sync it to the strusWebService. +Update March 2018: currently the ARM version of strus is completely broken +and the strusWebService is being rewritten. So there will be an updated +blog entry when those things are fixed. + # Sources As always you can find the sources of the project on my github (also hosted |