Package Details: searx 1.1.0-1

Git Clone URL: https://aur.archlinux.org/searx.git (read-only, click to copy)
Package Base: searx
Description: A privacy-respecting, hackable metasearch engine (python(3) based)
Upstream URL: https://searx.github.io/searx/
Licenses: AGPL
Conflicts: searx-git
Replaces: searx-py3
Submitter: Jake
Maintainer: Jake
Last Packager: Jake
Votes: 37
Popularity: 0.40
First Submitted: 2016-09-07 11:42 (UTC)
Last Updated: 2022-08-09 18:55 (UTC)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

tbh commented on 2021-12-09 13:06 (UTC)

If you use use_default_settings: True in /etc/searx/settings.yml (so that file can be much shorter) then searx will merge defaults from /usr/lib/python3.9/site-packages/searx/settings.yml.

Jake commented on 2021-12-09 12:39 (UTC)

The package already includes default settings and does setup the secret key, so you don't really have to do anything. Still you can adjust it in /etc/searx/settings.yml. This symlink is not needed if it is started from uwsgi, so the env var SEARX_SETTINGS_PATH is properly set, just as a fallback if it gets started from somewhere else. I don't understand though, how does it cause issues?

tbh commented on 2021-12-09 12:18 (UTC)

Trying to setup searx using default settings per https://searx.github.io/searx/admin/installation-searx.html#configuration I'm having issues I believe due to the symlink created on https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=searx#n55. Is the symlink needed?

bestfriend commented on 2021-11-02 04:47 (UTC)

@Bogdanov You can change it in the settings.yml. See https://searx.github.io/searx/admin/settings.html

Bogdanov commented on 2021-10-19 05:59 (UTC)

It may seem like a dumb question, but is there a way to change the name of the instance? Or I have to necessairly use "http://127.0.0.1:8888/"?

Jake commented on 2021-05-12 19:43 (UTC)

@stef204: Yes, I get this too and have added the cache config now to searx.ini (pkgrel=2).

stef204 commented on 2021-05-12 16:05 (UTC) (edited on 2021-05-12 16:13 (UTC) by stef204)

@Jake. thanks for your helpful feedback. my mistake: i was running it via systemctl start emperor.uwsgi.service probably causing the warning.

i've now used systemctl start uwsgi@searx.service and am getting this now, namely:

ERROR:searx.shared:uwsgi.ini configuration error, add this line to your uwsgi.in cache2 = name=searxcache,items=2000,blocks=2000,blocksize=4096,bitmap=1

Edit: if I add the whole line: cache2 = name=searxcache,items=2000,blocks=2000,blocksize=4096,bitmap=1 to /etc/uwsgi/emperor.ini the error/warning disappears.

Jake commented on 2021-05-12 15:01 (UTC)

@stef204: searx.ini contains uid = searx and gid = searx in both packages. In my testing this switches the user/group as expected. The journal then contains:

Mai 12 16:32:40 pc-arch uwsgi[144997]: setgid() to 982
Mai 12 16:32:40 pc-arch uwsgi[144997]: setuid() to 982

and no warnings. 982 is the ID of the searx user on my system. All 5 processes (1 master + 4 workers) run under searx not root.

Did you run it with systemctl start uwsgi@searx.service? Have you possibly edited searx.ini (removed the uid/gid lines)?

btw: The flask update issue is now solved by: https://github.com/archlinux/svntogit-community/commit/a2f7409ea6fee371a5a09988fc4a5e28876f22dc#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a

stef204 commented on 2021-05-12 14:27 (UTC) (edited on 2021-05-12 14:30 (UTC) by stef204)

@Jake

curious to know what your take is on the comment I posted on the git version regarding upstream install instructions which applies to this package as well:

https://aur.archlinux.org/packages/searx-git#comment-807155

basically, this warning