issue: create 1beb - deploy ngit-relay rate limiting fix

This commit is contained in:
DanConwayDev
2026-01-16 22:16:37 +00:00
parent d09a2b0f7f
commit 3a3957d83f
@@ -0,0 +1,30 @@
# Deploy ngit-relay Rate Limiting Fix to Production
**ID:** 1beb
## Problem
The ngit-relay rate limiting fix (commit 81e35bb) is on branch `fix-rate-limiting` but not deployed to production. The fix increases khatru rate limiter from 100→500 connections/IP and 1/2min→10/min refill rate. Docker image was built locally but not pushed to registry, and containers are still running old v0.0.3 image.
## Plan
- [ ] Merge fix-rate-limiting to master in ngit-relay repo
- [ ] Build and tag Docker image as v0.0.4
- [ ] Push Docker image to GitHub Container Registry
- [ ] Update nixos-vps1 service configs to use v0.0.4
- [ ] Commit nixos-vps1 config changes
- [ ] Deploy to VPS using deploy command
- [ ] Verify deployment (containers running v0.0.4, reduced 429 errors)
- [ ] Push ngit-relay master branch to remote
## Progress
### 2026-01-16 [Session Start]
- Started: Created issue to track deployment workflow
## Notes
- Branch: fix-rate-limiting in /persistent/dcdev/clones/ngit-relay
- Commit: 81e35bb
- Services affected: gitnostr-com-ngit-relay, relay-ngit-dev-ngit-relay
- VPS: 94.156.119.146