Update Kubernetes deployment image references to match the actual
image names pushed to the Gitea registry:
- adopt-a-street/backend -> adopt-a-street-backend
- adopt-a-street/frontend -> adopt-a-street-frontend
Also remove node affinity preference from backend deployment to allow
more flexible pod scheduling, and fix registry-secret namespace to
align with current deployment structure.
This fixes ImagePullBackOff errors where Kubernetes couldn't find the
images at the incorrect paths.
🤖 Generated with OpenCode
Co-Authored-By: AI Assistant <noreply@ai-assistant.com>
- Replace Socket.IO with SSE for real-time server-to-client communication
- Add SSE service with client management and topic-based subscriptions
- Implement SSE authentication middleware and streaming endpoints
- Update all backend routes to emit SSE events instead of Socket.IO
- Create SSE context provider for frontend with EventSource API
- Update all frontend components to use SSE instead of Socket.IO
- Add comprehensive SSE tests for both backend and frontend
- Remove Socket.IO dependencies and legacy files
- Update documentation to reflect SSE architecture
Benefits:
- Simpler architecture using native browser EventSource API
- Lower bundle size (removed socket.io-client dependency)
- Better compatibility with reverse proxies and load balancers
- Reduced resource usage for Raspberry Pi deployment
- Standard HTTP-based real-time communication
🤖 Generated with [AI Assistant]
Co-Authored-By: AI Assistant <noreply@ai-assistant.com>
Changed registry server from:
gitea-http.taildb3494.ts.net
to:
gitea-gitea-http.taildb3494.ts.net
This matches the actual Gitea HTTP service name in the Kubernetes cluster.
🤖 Generated with OpenCode
Co-Authored-By: OpenCode <noreply@opencode.com>
- Add deploy/k8s/registry-secret.yaml with Gitea registry credentials
- Make registry-secret namespace-agnostic (removed hardcoded 'tools' namespace)
- Update k8s-deploy target to automatically apply registry secret
- Simplify deployment workflow - no longer requires manual k8s-secret-create step
- Update help documentation to reflect streamlined deployment process
The registry secret is now automatically deployed to the target namespace,
making the deployment workflow more convenient and consistent across all
environments (dev, staging, prod).
🤖 Generated with OpenCode
Co-Authored-By: OpenCode <noreply@opencode.com>
