Skip to content

Commit 1ee8859

Browse files
authored
Fix incorrect Argon2 config key and unclear wording (#173)
1 parent 6b78be2 commit 1ee8859

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/self-hosting/config.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ plugins_default=pretix.plugins.sendmail,pretix.plugins.statistics,pretix.plugins
133133

134134
`allow_http_to_private_networks`
135135

136-
: If this is off, pretix connections to private networks, for instance, IP addresses such as `127.0.0.1` or `10.0.0.0` for all outgoing HTTP connections, such as webhooks and payment gateways.
136+
: If this is off, pretix blocks connections to private networks, for instance, IP addresses such as `127.0.0.1` or `10.0.0.0`, for all outgoing HTTP connections, such as webhooks and payment gateways.
137137
If you are using a local `http_proxy`/`https_proxy` for outgoing requests, set this to `off`.
138138
In that case, the proxy is responsible for filtering valid destinations.
139139

@@ -209,7 +209,7 @@ sslkey=/etc/pretix/postgresql-client-key.key
209209
## Database replica settings
210210

211211
If you use a replicated database setup, pretix expects that the default database connection always points to the primary database node.
212-
Routing read queries to a replica on database layer is **strongly** discouraged since this can lead to inaccurate such as more tickets being sold than are actually available.
212+
Routing read queries to a replica on database layer is **strongly** discouraged since this can lead to inaccurate results, such as more tickets being sold than are actually available.
213213

214214
However, pretix can still make use of a database replica to keep some expensive queries with that can tolerate some latency from your primary database, such as backend search queries.
215215
The `replica` configuration section can have the same settings as the `database` section (except for the `backend` setting) and will default back to the `database` settings for all values that are not given.
@@ -330,7 +330,7 @@ passwords_argon2=on
330330

331331
Never set this to `True` in production!
332332

333-
`passwords_argon`
333+
`passwords_argon2`
334334

335335
: Use the `argon2` algorithm for password hashing. Disable on systems with a small number of CPU cores (currently less than 8).
336336

0 commit comments

Comments
 (0)