8 Commits
Author SHA1 Message Date
woggioni 5c6a5980ec fixed css
CI / Build and push docker image (push) Successful in 3m36s
release/0.0.5
2026-09-07 04:13:18 +08:00
woggioni 74c7400957 added arm64 docker image 2026-09-06 23:11:27 +08:00
woggioni-opencode-agent 47d2280970 Upgrade to kaya 0.0.3 with trusted-proxy forwarded header support
CI / Build and push docker image (push) Successful in 1m25s
- bump kaya-core/kaya-rsgi to >= 0.0.3 and add kaya-forwarded: forwarded
  header handling is no longer built into core, it is opt-in via
  ForwardedHeadersMixin and gated on trusted proxy CIDRs
- add TRUSTED_PROXY_CIDRS setting (comma-separated CIDRs, validated at
  startup; empty means no proxy is trusted) and wire the mixin in app.py
- cover trusted/untrusted peers, all-trusted chains and the RFC 7239
  Forwarded header with port in the test suite
- document the new variable in README, .env.example and docker-compose.yml
release/0.0.4
2026-09-05 16:18:37 +08:00
woggioni d51f380a3f fixed styling
CI / Build and push docker image (push) Successful in 1m18s
release/0.0.3
2026-09-04 21:14:31 +08:00
woggioni-opencode-agent c5b653efba Upgrade to kaya 0.0.2 and run on the rloop event loop
CI / Build and push docker image (push) Successful in 1m39s
- pin kaya-core/kaya-rsgi >= 0.0.2 (ctx.client now honors Forwarded and
  X-Forwarded-* headers); adapt route tests and add explicit coverage
- add rloop dependency and set GRANIAN_LOOP=rloop in the Docker image so
  granian serves the app on the Rust event loop instead of asyncio
- regenerate requirements.txt (kaya 0.0.2, rloop 0.5.0)
- document the new loop and forwarded-header behavior in the README
release/0.0.2
2026-09-04 19:57:32 +08:00
woggioni f043ea4afe changed image repository name 2026-09-04 19:57:31 +08:00
woggioni-opencode-agent 628903afe0 Remove unused APP_HOST/APP_PORT settings 2026-09-04 19:57:31 +08:00
woggioni-opencode-agent b8f4e3026b Initial commit: ifconfig.me clone on the kaya framework 2026-09-04 19:57:31 +08:00