这是indexloc提供的服务,不要输入任何密码
Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ There are two ways to host SearXNG. The first one doesn't require any prior know
3. Edit the [.env](https://github.com/searxng/searxng-docker/blob/master/.env) file to set the hostname and an email
4. Generate the secret key `sed -i "s|ultrasecretkey|$(openssl rand -hex 32)|g" searxng/settings.yml`
On a Mac: `sed -i '' "s|ultrasecretkey|$(openssl rand -hex 32)|g" searxng/settings.yml`
5. Edit [searxng/settings.yml](https://github.com/searxng/searxng-docker/blob/master/searxng/settings.yml) according to your needs
5. Edit [searxng/settings.yml](https://github.com/searxng/searxng-docker/blob/master/searxng/settings.yml) according to your needs. An example of configurable settings can be reviewed here: [searxng/searx/settings.yml](https://github.com/searxng/searxng/blob/master/searx/settings.yml)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, a link to searxng/searx/settings.yml has been added to give users an idea of the config options that are available.
..
An example of configurable settings can be reviewed here: searxng/searx/settings.yml
Comment

That is not 100% correct .. the /etc/searxng/settings.yml file is a use_default_settings=True

# see https://docs.searxng.org/admin/settings/settings.html#settings-use-default-settings
use_default_settings: true

What this means is documented at https://docs.searxng.org/admin/settings/settings.html#settings-use-default-settings

And all other settings are documented here: https://docs.searxng.org/admin/settings/index.html

We should encourage the instance admins to read the docs, too often we have tickets just because someone hasn't read the doc.


> [!NOTE]
> On the first run, you must remove `cap_drop: - ALL` from the `docker-compose.yaml` file for the `searxng` service to successfully create `/etc/searxng/uwsgi.ini`. This is necessary because the `cap_drop: - ALL` directive removes all capabilities, including those required for the creation of the `uwsgi.ini` file. After the first run, you should re-add `cap_drop: - ALL` to the `docker-compose.yaml` file for security reasons.
Expand Down