add blogpost about private searx and fix uwsgi installation guide

This commit is contained in:
Noémi Ványi 2022-09-30 23:17:14 +02:00
parent 629ebb426f
commit a1e2c501d2
3 changed files with 50 additions and 1 deletions

View File

@ -95,7 +95,7 @@ My experience is, that this command is a bit buggy.
.. _uwsgi configuration:
All together
===========
============
Create the configuration ini-file according to your distribution (see below) and
restart the uwsgi application.

View File

@ -0,0 +1,48 @@
=================================
Private searx project is finished
=================================
We are officially finished with the Private searx project. The goal was to
extend searx capabilities beyond just searching on the Internet. We added
support for offline engines. These engines do not connect to the Internet,
they find results locally.
As some of the offline engines run commands on the searx host, we added an
option to protect any engine by making them private. Private engines can only be
accessed using a token.
After searx was prepared to run offline queries we added numerous new engines:
1. Command line engine
2. MySQL
3. PostgreSQL
4. SQLite
5. Redis
6. MongoDB
We also added new engines that communicate over HTTP, but you might want to keep
them private:
1. Elasticsearch
2. Meilisearch
3. Solr
The last step was to document this work. We added new tutorials on creating
command engines, making engines private and also adding a custom result template
to your own engines.
Acknowledgement
===============
The project was sponsored by `Search and Discovery Fund`_ of `NLnet
Foundation`_. We would like to thank the NLnet for not only the funds, but the
conversations and their ideas. They were truly invested and passionate about
supporting searx.
.. _Search and Discovery Fund: https://nlnet.nl/discovery
.. _NLnet Foundation: https://nlnet.nl/
| Happy hacking.
| kvch // 2022.09.30 23:15

View File

@ -15,3 +15,4 @@ Blog
search-indexer-engines
sql-engines
search-database-engines
documentation-offline-engines