Code: Select all
Sphinx 2.2.11-id64-release (95ae9a6)
Copyright (c) 2001-2016, Andrew Aksyonoff
Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
using config file '/etc/sphinx/sphinx.conf'...
WARNING: key 'sql_query_info' was permanently removed from Sphinx configuration. Refer to documentation for details.
WARNING: key 'stopwords' is not multi-value; value in /etc/sphinx/sphinx.conf line 73 will be ignored.
WARNING: key 'charset_type' was permanently removed from Sphinx configuration. Refer to documentation for details.
ERROR: unknown key name 'compat_sphinxql_magics' in /etc/sphinx/sphinx.conf line 91 col 24.
FATAL: failed to parse config file '/etc/sphinx/sphinx.conf'
Indeed. Bumping this. I had a go at switching to Sphinx on a board for 2 million posts on a localhost test bed running Windows 10 and IIS10.thecoalman wrote: ↑Sun Aug 13, 2017 10:05 am With that said this is extremely fast compared to the regular search.
Sphinx needs to be installed outside of the webroot ( a non public directory), the directions in the sphinx documentation assumes root access. How or if you can install on shared hosting I do not know. It's constantly running and consumes RAM, how much depends on size of search index. It's not much for regular operation but is quite a bit when it rebuilds the index. This is typically something that is not going to be supported with shared hosting.
Thanks for that confirmation. There might be merit in putting the data directory within the webroot (but without web user acccess) so that the Sphinx configuration and indexes get saved as part of the website backup, but it looks to be working with those files saved in the same directory as the Sphinx executables sitting outside the webroot.thecoalman wrote: ↑Wed Nov 27, 2019 1:14 amSphinx needs to be installed outside of the webroot ( a non public directory), the directions in the sphinx documentation assumes root access. How or if you can install on shared hosting I do not know. It's constantly running and consumes RAM, how much depends on size of search index. It's not much for regular operation but is quite a bit when it rebuilds the index. This is typically something that is not going to be supported with shared hosting.
cron
every five minutes... but, in truth, it's so fast that it can very well run every second that it wouldn't make a difference in terms of server load...