diff options
| author | Markus Heiser <markus.heiser@darmarit.de> | 2021-10-11 21:20:22 +0200 |
|---|---|---|
| committer | Markus Heiser <markus.heiser@darmarit.de> | 2021-10-30 16:11:01 +0200 |
| commit | 2b1252148d083eb47382733980ec069ef20dcfb6 (patch) | |
| tree | c9df5b4a7afec05421197e437ab38ea81e9cc926 /docs/admin/installation-uwsgi.rst | |
| parent | a9fc4885f2d4ab3fba8fd9fbaa0386090250bd11 (diff) | |
| download | searxng-2b1252148d083eb47382733980ec069ef20dcfb6.tar.gz searxng-2b1252148d083eb47382733980ec069ef20dcfb6.zip | |
[brand] SearXNG - nginx & apache searxng.conf, uwsgi searxng.conf
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Diffstat (limited to 'docs/admin/installation-uwsgi.rst')
| -rw-r--r-- | docs/admin/installation-uwsgi.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/admin/installation-uwsgi.rst b/docs/admin/installation-uwsgi.rst index e4b35dfc2..1fb24ca8f 100644 --- a/docs/admin/installation-uwsgi.rst +++ b/docs/admin/installation-uwsgi.rst @@ -35,10 +35,10 @@ recommend two methods `systemd.unit`_ template files as described here `One service per app in systemd`_. There is one `systemd unit template`_ and one `uwsgi ini file`_ per uWSGI-app - placed at dedicated locations. Take archlinux and a searx.ini as example:: + placed at dedicated locations. Take archlinux and a searxng.ini as example:: unit template --> /usr/lib/systemd/system/uwsgi@.service - uwsgi ini files --> /etc/uwsgi/searx.ini + uwsgi ini files --> /etc/uwsgi/searxng.ini The SearXNG app can be maintained as know from common systemd units:: @@ -54,12 +54,12 @@ The `uWSGI Emperor`_ mode which fits for maintaining a large range of uwsgi apps systemd unit. The Emperor service will scan specific directories for `uwsgi ini file`_\s (also know as *vassals*). If a *vassal* is added, removed or the timestamp is modified, a corresponding action takes place: a new uWSGI - instance is started, reload or stopped. Take Fedora and a searx.ini as + instance is started, reload or stopped. Take Fedora and a searxng.ini as example:: - to start a new SearXNG instance create --> /etc/uwsgi.d/searx.ini - to reload the instance edit timestamp --> touch /etc/uwsgi.d/searx.ini - to stop instance remove ini --> rm /etc/uwsgi.d/searx.ini + to start a new SearXNG instance create --> /etc/uwsgi.d/searxng.ini + to reload the instance edit timestamp --> touch /etc/uwsgi.d/searxng.ini + to stop instance remove ini --> rm /etc/uwsgi.d/searxng.ini Distributors ============ @@ -80,7 +80,7 @@ do similar for the uWSGI infrastructure (with less comfort), the folders are:: The `uwsgi ini file`_ is enabled by a symbolic link:: - ln -s /etc/uwsgi/apps-available/searx.ini /etc/uwsgi/apps-enabled/ + ln -s /etc/uwsgi/apps-available/searxng.ini /etc/uwsgi/apps-enabled/ From debian's documentation (``/usr/share/doc/uwsgi/README.Debian.gz``): You could control specific instance(s) by issuing:: |