Package Details: searx 1.1.0-2

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: 38
Popularity: 0.000018
First Submitted: 2016-09-07 11:42 (UTC)
Last Updated: 2023-06-03 10:47 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

kseistrup commented on 2019-11-18 18:23 (UTC)

@Jake, are you sure that will continue to work? I ask because I had a very old installation of searx that had /usr/lib/python3.4 (or similar) as its homedir, and there's a systemd process roaming about every now and then to check if directories and permissions are ok, and that process complained that the homedir for searx was non-existent.

If you take a look at your /etc/passwd file, what is the homedir of the searx user now that you have edited the sysusers file?

Jake commented on 2019-11-18 17:41 (UTC)

@kseistrup: Actually that home dir is not used by searx anyway, it works fine without it, so i pushed that change now.

kseistrup commented on 2019-11-18 05:10 (UTC)

The sysusers file is still referring to Python 3.7:

u searx - "Searx server user" /usr/lib/python3.7/site-packages

which is definitely wrong now that Arch has switched to Python 3.8.

I still believe that it's an incredibly bad idea to have a sysuser's homedir in a directory that holds files that are completely unrelated to the searx user. Imagine if an ArchLinux userrs decides to uninstall searx and the invokes userdel(8) with the -r switch (“Files in the user's home directory will be removed along with the home directory itself and the user's mail spool.”).

kseistrup commented on 2019-11-10 12:37 (UTC) (edited on 2019-11-10 12:38 (UTC) by kseistrup)

Using /usr/lib/python3.7/site-packages as the homedir for the searx user seems like a really bad idea to me: not only should no user have a homedir in that dir, but when ArchLinux goes from Python 3.7 to 3.8, that dir will become obsolete.

Please create a separate dir for the searx user – e.g. /usr/lib/searx – and make it the homedir of the searx user [and group].

Jake commented on 2019-08-25 13:14 (UTC) (edited on 2019-08-25 13:14 (UTC) by Jake)

Since searx seems stable with python(3) now, i have updated this package and drop the python2 version. Also i changed it from the internal server to uWSGI. The server config is now in /etc/uwsgi/searx.ini and uwsgi@searx.service should be started, the old searx.service got removed.

danieltetraquark commented on 2019-07-21 12:29 (UTC)

Btw: searx is intended to be run with uwsgi or similar, the integrated webserver literally logs that you shouldn't use it in production.

danieltetraquark commented on 2019-07-19 14:30 (UTC)

@Jake Maybe you can add Provides=searx ?

bjo commented on 2019-04-25 21:16 (UTC)

Wouldn't it be better to use uwsgi instead of the flask-server?

Jake commented on 2018-08-21 20:41 (UTC)

Thanks for the hint gdkags, changed and using sysusers in pkrel=3.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »