sphinxsearch | Sphinx Search for Laravel | Autocomplete library

With sphinx the 'sphinx.conf' file can be 'executable'. Ie it can actully be a 'shell script' (or PHP, perl etc!)

Assuming your .env file makes real (runtime!) environment variables within the container (not overly familiar with Docker), then your sphinx.conf file could be ...

Well as such a:foo isnt a valid JSON value AFAIK. LOoks like it meant to be object? So would need {...} surrounding it.

But even {foo:bar} is not valid either. At the very least the 'value' shoud be quoted {foo:"bar"}. But really the keys quoting too {"foo":"bar"}

Javascript Objects technically allow unquoted key names, but JSON requires the quoting.

... but also remember it CSV. Quotes are typically used for quoting (eg when columns contain commas), so the quotes need double encoding! Ends up a bit messy...

@barryhunter solved it in the comments.

I needed --all on the indexer to make it actually index.

Alright, I solved the problem by remving sphinix and then install it again:

Before running the searchd daemon you firstly need to build indexes. For this purpose run the first indexer job through the container:

Well on the case of Extended Query Syntax. You are almost certainly using it anyway. Its the only mode sphinx has (for while anyway, early versions did have mulitple query modes) ... so in itself shouldnt be scary.

Possibly the bigger issue with index_sp, its it implemented by the HTML Stripper, so need to enable html_strip=1 as well. Which might well change behaviour of queries. (if have HTML anyway!)

The only other place aware that index_sp might affect things is 'cross sentence phrase matches'.

Without index_sp, a query like "one two" would match text [one. two], but with index_sp it wouldnt. Ie the . has split into sentances, so no longer match "phrase" wise. This can be a good thing, but is a change. This can in some cases affect things that are not really sentance seperators. Eg the . can break up sentances, when its not really a full stop. Sphinx as a relatively good algorithm for braking sentances, but not perfect.

I've seen that happen, it comes from the Sphinx install 'package'. Whoever setup that package, created a cron task that does that indexer --all command, that just tries to reindex every index (once a day IIRC). The package maintainer thought they being helpful :)

From https://packages.ubuntu.com/bionic/ppc64el/sphinxsearch/filelist

looks like it might be in

Assuming you have this in MySQL: