There are a number of anti-abuse measures that rely on having knowledge of the client IP address in order to function. Also, the client IP is logged in a number of places, including at least two different log files (nginx access log and rails log), so you’ll need to modify some pretty deep config in order to get rid of those, too. And yes, I’d say you’re likely going to need to fork to eradicate all those.
mpalmer
(Matt Palmer)
2
Temas relacionados
| Tema | Respuestas | Vistas | Actividad | |
|---|---|---|---|---|
| IP logging on my site | 5 | 1217 | 16 Noviembre 2020 | |
| How to disable logging IP address? | 3 | 2087 | 12 Febrero 2023 | |
| Privacy feature request: disabling or hashing logs (using cryptolog or similar) | 4 | 2333 | 14 Enero 2017 | |
| 429 Too Many Requests - IP logs disabled - discourse can see 127.0.0.1 only | 1 | 683 | 9 Marzo 2022 | |
| Using Discourse without IP logins | 0 | 99 | 8 Junio 2025 |