GeneralBots/gb
1
0
Fork 0
Code Activity Actions 1

docs: Add rule to never write internal IPs to logs

Browse source
This commit is contained in:
Rodrigo Rodriguez (Pragmatismo) 2026-03-31 11:12:57 -03:00
parent c79ab35409
commit 52aac0af21
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
AGENTS.md
View file

@ -10,6 +10,9 @@ test login here http://localhost:3000/suite/auth/login.html
I AM IN DEV ENV, but sometimes, pasting from PROD, do not treat my env as prod! Just fix, to me and push to CI. So I can test in PROD, for a while. I AM IN DEV ENV, but sometimes, pasting from PROD, do not treat my env as prod! Just fix, to me and push to CI. So I can test in PROD, for a while.
>Use Playwrigth MCP to start localhost:3000/<bot> now. >Use Playwrigth MCP to start localhost:3000/<bot> now.
> **NEVER CREATE FILES WITH SECRETS IN THE REPOSITORY ROOT** > **NEVER CREATE FILES WITH SECRETS IN THE REPOSITORY ROOT**
> - ❌ **NEVER** write internal IPs to logs or output
> - When debugging network issues, mask IPs (e.g., "10.x.x.x" instead of "10.16.164.222")
> - Use hostnames instead of IPs in configs and documentation
See botserver/src/drive/local_file_monitor.rs to see how to load from /opt/gbo/data the list of development bots. See botserver/src/drive/local_file_monitor.rs to see how to load from /opt/gbo/data the list of development bots.
- ❌ **NEVER** use `cargo clean` - causes 30min rebuilds, use `./reset.sh` for database issues - ❌ **NEVER** use `cargo clean` - causes 30min rebuilds, use `./reset.sh` for database issues