Search Criteria
Package Details: searx 1.1.0-2
Package Actions
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 »
Jake commented on 2020-02-13 19:36 (UTC)
@MagicTheRipper: Post the log output from
journalctl -u uwsgi@searx.service
, please. Otherwise it is impossible to debug.MagicTheRipper commented on 2020-02-13 19:03 (UTC) (edited on 2020-02-13 19:12 (UTC) by MagicTheRipper)
Im having an error when I connect to localhost:8888,it shows this "Internal Server Error" as a result on my browser
Any fix
Jake commented on 2020-02-13 11:58 (UTC) (edited on 2020-02-13 11:59 (UTC) by Jake)
@noctux: Thanks a lot for the patch, i have applied it now (pkgrel=2).
noctux commented on 2020-02-13 08:55 (UTC)
Breaks with recent releases of werkzeug 1.0.0. Upstream has a patch: https://github.com/asciimoo/searx/commit/b8b13372c8fd3bfe978a1c724ab98b05348df054
Update for the pkgbuild:
bjo commented on 2019-12-03 07:00 (UTC) (edited on 2019-12-03 07:00 (UTC) by bjo)
@GI_Jack run
systemctl start uwsgi@searx
GI_Jack commented on 2019-12-03 02:18 (UTC)
add systemd package for running this as a daemon.
bjo commented on 2019-11-25 10:01 (UTC)
Could you add the patch from https://github.com/asciimoo/searx/pull/1749 ? It would make google working again.
kseistrup commented on 2019-11-18 19:04 (UTC)
@Jake, that's great – thanks for letting us know.
Re: problems: I didn't cause problems as such, but it did create warnings from systemd in syslog.
Jake commented on 2019-11-18 18:50 (UTC)
@kseistrup: I deleted the user and reinstalled the package (sysusers does not touch existing users) for the test. It works fine and shows no warnings. Most official packages have system users without homedir, so in general it should be okay. We could even drop the extra user and use the uwsgi user, that has also no homedir set... Also i am pretty sure many users still had the user created with an older python version (even 2.x) in the homedir and that causes no issues, otherwise they surely would have surfaced by now.
« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »