mirror of
https://github.com/searxng/searxng.git
synced 2025-03-12 15:41:15 +00:00
[doc] minor improvements to the favicon docs (cache.db_url)
Related: - https://github.com/searxng/searxng/issues/4405 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
This commit is contained in:
parent
a51416c7c3
commit
0c2076ca5b
1 changed files with 10 additions and 8 deletions
|
@ -93,15 +93,13 @@ TOML_ configuration is created in the file ``/etc/searxng/favicons.toml``.
|
|||
:py:obj:`cache.db_url <.FaviconCacheConfig.db_url>`:
|
||||
The path to the (SQLite_) database file. The default path is in the `/tmp`_
|
||||
folder, which is deleted on every reboot and is therefore unsuitable for a
|
||||
production environment. The FHS_ provides the folder for the
|
||||
application cache
|
||||
production environment. The FHS_ provides the folder `/var/cache`_ for the
|
||||
cache of applications, so a suitable storage location of SearXNG's caches is
|
||||
folder ``/var/cache/searxng``.
|
||||
|
||||
The FHS_ provides the folder `/var/cache`_ for the cache of applications, so a
|
||||
suitable storage location of SearXNG's caches is folder ``/var/cache/searxng``.
|
||||
In container systems, a volume should be mounted for this folder and in a
|
||||
standard installation (compare :ref:`create searxng user`), the folder must be
|
||||
created and the user under which the SearXNG process is running must be given
|
||||
write permission to this folder.
|
||||
In a standard installation (compare :ref:`create searxng user`), the folder
|
||||
must be created and the user under which the SearXNG process is running must
|
||||
be given write permission to this folder.
|
||||
|
||||
.. code:: bash
|
||||
|
||||
|
@ -109,6 +107,10 @@ TOML_ configuration is created in the file ``/etc/searxng/favicons.toml``.
|
|||
$ sudo chown root:searxng /var/cache/searxng/
|
||||
$ sudo chmod g+w /var/cache/searxng/
|
||||
|
||||
In container systems, a volume should be mounted for this folder. Check
|
||||
whether the process in the container has read/write access to the mounted
|
||||
folder.
|
||||
|
||||
:py:obj:`cache.LIMIT_TOTAL_BYTES <.FaviconCacheConfig.LIMIT_TOTAL_BYTES>`:
|
||||
Maximum of bytes stored in the cache of all blobs. The limit is only reached
|
||||
at each maintenance interval after which the oldest BLOBs are deleted; the
|
||||
|
|
Loading…
Reference in a new issue