write ouput in searx/data/engine_descriptions.json instead of stdout
use the wikipedia engine to fetch the wikipedia descriptions
(for example use tl.wikipedia.org for the Filipino language)
* [fix] searx_extra/update scripts: set_loggers(wikidata, 'wikidata')
To test use::
./manage pyenv.cmd searx_extra/update/update_currencies.py
./manage pyenv.cmd searx_extra/update/update_osm_keys_tags.py
./manage pyenv.cmd searx_extra/update/update_wikidata_units.py
The script `update_engine_descriptions.py` seems to have some issues not related
to this patch.
./manage pyenv.cmd python -m pip install -U pycld3
./manage pyenv.cmd searx_extra/update/update_engine_descriptions.py
Closes: https://github.com/searxng/searxng/issues/328
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
In ./manage implement babel.*:
- extract : extract messages from source files and generate POT file
- update : update existing message catalogs from POT file
- compile : compile translation catalogs into binary MO files
Replace searx_extra/update/update_translations.sh by command:
- ci.babel.update
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
the script expects searx/translations/messages.pot to be commited
it calls "pybabel extract", and if there is a meaningful change,
it calls "pybabel update"
exit code 0 when there is a change in messages.pot
In commit 4d3f2f48d common used languages has been droped. By reducing the
number of `min_engines_per_lang` from 15 to 13 we get theses languages back.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
settings.yml:
* outgoing.networks:
* can contains network definition
* propertiers: enable_http, verify, http2, max_connections, max_keepalive_connections,
keepalive_expiry, local_addresses, support_ipv4, support_ipv6, proxies, max_redirects, retries
* retries: 0 by default, number of times searx retries to send the HTTP request (using different IP & proxy each time)
* local_addresses can be "192.168.0.1/24" (it supports IPv6)
* support_ipv4 & support_ipv6: both True by default
see https://github.com/searx/searx/pull/1034
* each engine can define a "network" section:
* either a full network description
* either reference an existing network
* all HTTP requests of engine use the same HTTP configuration (it was not the case before, see proxy configuration in master)
