- 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>
- 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>
Add 16 new Makefile targets for K8s cluster management:
Testing targets:
- k8s-test-connection: Verify kubectl connectivity to cluster
- k8s-test-manifests: Validate manifest syntax with dry-run
- k8s-test-deploy-dev: Test deployment to dev namespace
Deployment targets:
- k8s-namespace-create: Create namespace with variable support
- k8s-secret-create: Create image pull secrets (requires GITEA_PASSWORD)
- k8s-deploy: Deploy all manifests to configurable namespace
- k8s-deploy-dev/staging/prod: Environment-specific deployments
Verification targets:
- k8s-status: Show pods/services/deployments/statefulsets status
- k8s-logs-backend/frontend: Tail logs for specific services
- k8s-health: Check health endpoints for all services
Utility targets:
- k8s-port-forward: Port forward services for local testing
- k8s-exec-backend: Shell into backend pod
- k8s-rollback: Rollback deployments
- k8s-delete: Delete all resources from namespace (with safety delay)
Configuration:
- K8S_NAMESPACE: Configurable namespace (default: adopt-a-street-dev)
- K8S_CONTEXT: Cluster context (default: k0s-cluster)
- REGISTRY: Container registry (default: gitea-http.taildb3494.ts.net)
- GITEA_USERNAME: Registry username (default: will)
All targets support namespace override via K8S_NAMESPACE parameter for
multi-environment deployments to dev/staging/prod namespaces.
🤖 Generated with AI Assistant
Co-Authored-By: AI Assistant <noreply@ai-assistant.com>
- Update Makefile to use bun for all commands (install, build, test, lint)
- Update frontend package.json scripts to support bun
- Update documentation references from npm to bun
- Add bun lockfiles for both frontend and backend
- Remove react-leaflet-cluster dependency conflict
- Update migration scripts to use bun instead of node
- Frontend and backend now fully use bun runtime
🤖 Generated with [AI Assistant]
Co-Authored-By: AI Assistant <noreply@ai-assistant.com>
- Add Docker BuildKit builder setup for AMD64 and ARM64 platforms
- Update backend and frontend Dockerfiles with platform flags
- Create comprehensive build scripts for multi-arch workflows
- Add verification script to test multi-architecture images
- Update Makefile with multi-arch Docker targets
- Add detailed documentation for multi-architecture setup
This enables building Docker images that work on both development machines
(AMD64) and Raspberry Pi cluster (ARM64) with automatic platform selection.
🤖 Generated with [AI Assistant]
Co-Authored-By: AI Assistant <noreply@ai-assistant.com>
- Add Makefile with commands for building, testing, and running both frontend and backend
- Include development, production, testing, and code quality targets
- Add Docker support and environment setup commands
- Provide quick-start command for new developers
- Include comprehensive help documentation for all available commands
🤖 Generated with [AI Assistant]
Co-Authored-By: AI Assistant <noreply@ai-assistant.com>
