No description
|
All checks were successful
Deploy qio.no / deploy (push) Successful in 10m15s
Ports git.laima/humoji's new escalating throttle on GET /api/challenge into this backend's in-process fork: 333ms/1s/5s gaps as a client burns through challenges, resetting after 30s idle. A wrong guess already burns the challenge server-side, so brute-forcing means requesting challenges in a loop - the issue rate is what needed limiting, not the verify rate. Uses the same X-Forwarded-For/X-Real-IP precedence as main.py's get_client_ip() rather than porting the standalone server's HUMOJI_TRUST_PROXY flag, since this backend always sits behind Caddy here. Returns 429 + Retry-After + retryAfterMs, matching what the updated client widget expects. |
||
|---|---|---|
| .forgejo/workflows | ||
| .github/workflows | ||
| backend | ||
| docs | ||
| public | ||
| scripts | ||
| src | ||
| .gitignore | ||
| CLAUDE.md | ||
| CNAME | ||
| eslint.config.js | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| vite.config.js | ||
React + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel (or oxc when used in rolldown-vite) for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and typescript-eslint in your project.