tinkle-community b2ce123df1 fix(auth): single-user deployment by default, no open registration ...

Registration logic redesigned:
- Empty DB (first-time setup): registration always open, no config needed
- After first user exists: registration closed by default
- Multi-user opt-in: set REGISTRATION_ENABLED=true + MAX_USERS=N in .env

Config defaults changed:
- RegistrationEnabled: true → false (closed after first user)
- MaxUsers: 10 → 1 (single-user deployment default)

This eliminates the confusion of multiple users appearing in a personal
deployment where Telegram is bound to a single admin account.

2026-03-08 18:32:50 +08:00

..

backtest.go

feat: unify NofxOS data provider and fix language consistency

2026-01-04 00:59:07 +08:00

crypto_handler.go

feat: add TRANSPORT_ENCRYPTION toggle for easier deployment

2025-12-09 18:04:42 +08:00

debate.go

feat: unify NofxOS data provider and fix language consistency

2026-01-04 00:59:07 +08:00

errors.go

fix: sanitize API error messages to prevent sensitive info exposure

2026-01-03 13:11:15 +08:00

route_registry.go

feat(telegram): add AI agent bot with streaming and account context

2026-03-08 00:19:38 +08:00

server_test.go

refactor: standardize code comments

2025-12-08 01:43:22 +08:00

server.go

fix(auth): single-user deployment by default, no open registration

2026-03-08 18:32:50 +08:00

strategy.go

feat(telegram): add AI agent bot with streaming and account context

2026-03-08 00:19:38 +08:00

traderid_test.go

refactor: standardize code comments

2025-12-08 01:43:22 +08:00

utils_test.go

refactor: standardize code comments

2025-12-08 01:43:22 +08:00

utils.go

refactor: standardize code comments

2025-12-08 01:43:22 +08:00