silberengel/next.orly.dev - next.orly.dev - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
woikos	9c231169d2	Complete DDD improvements: handlers, ACL injection, Rule decomposition - Simplify HandleEvent to thin protocol adapter (~320 -> ~130 lines) - Create ingestion service for full event pipeline orchestration - Add specialkinds.go for special kind handler registration - Eliminate global ACL singleton with injectable Registry interface - Add ACLRegistry() accessor to Server for dependency injection - Decompose Rule value object into AccessControl, Constraints, TagValidationConfig sub-components for cleaner organization - Add LoggingSubscriber for domain event analytics - Update all policy tests for embedded struct initialization - Update DDD_ANALYSIS.md to 10/10 maturity score Files modified: - app/handle-event.go: Simplified to delegate to ingestion service - app/specialkinds.go: NEW - Special kind handler registration - app/server.go: Add aclRegistry field and ACLRegistry() accessor - pkg/interfaces/acl/acl.go: Add Registry interface - pkg/acl/acl.go: Add accessor methods for privatized fields - pkg/policy/policy.go: Decompose Rule into sub-value objects - pkg/policy/*_test.go: Update struct literals for embedded types - pkg/event/ingestion/service.go: Add ACLMode, special kinds support - pkg/event/processing/processing.go: Add domain event dispatcher - pkg/domain/events/subscribers/logging.go: NEW - Analytics subscriber - DDD_ANALYSIS.md: Update to 10/10 maturity score Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago
woikos	8be48ef8cc	Fix ACL startup timing and launcher ready check (v0.55.2) - ACL: Mark service ready immediately after gRPC server starts - ACL: Run Configure() in background goroutine (follow list loading) - Launcher: Actually call gRPC Ready() endpoint instead of just TCP port check - Launcher: Increase ACL ready timeout from 30s to 120s as fallback This fixes the issue where relay would timeout waiting for ACL because the launcher only checked if the TCP port was open, but the ACL service's Ready() was returning false until Configure() completed (which takes minutes for large follow lists). Now ACL marks itself ready immediately so the relay can start while follow lists continue loading in the background. Files modified: - cmd/orly-acl/main.go: Restructure startup to be async - cmd/orly-launcher/config.go: Increase ACL timeout to 120s - cmd/orly-launcher/supervisor.go: Add gRPC Ready() check - pkg/version/version: Bump to v0.55.2 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago
woikos	71129a98d2	Fix negentropy sync only seeing 100 events and ACL startup timeout (v0.55.1) - Remove debug 100 iteration limit from GetSerialsByRange The limit was a debug safety check that should have been removed. This was capping all range queries to 100 results, causing negentropy sync to only see 100 events instead of all events. - Fix ACL service startup to listen immediately before Configure The ACL server now starts the gRPC listener immediately after database ready, then runs Configure in the background. This prevents the launcher from timing out while waiting for ACL to load follow lists. - Add SetReady method to ACL service for proper ready signaling Files modified: - pkg/database/get-serials-by-range.go: Remove debug iteration limit - cmd/orly-acl/main.go: Start gRPC server before Configure - cmd/orly-acl/service.go: Add ready field and SetReady method - pkg/version/version: Bump to v0.55.1 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago
woikos	e20920d39b	Add split database and ACL binaries for modular deployment (v0.54.0) - Split orly-db into orly-db-badger and orly-db-neo4j backends - Split orly-acl into orly-acl-follows, orly-acl-managed, orly-acl-curation - Add shared pkg/database/server/ for gRPC database service - Add shared pkg/acl/server/ for gRPC ACL service - Add pkg/acl/grpc/ client for relay-to-ACL communication - Add gRPC proto definitions for ACL service (pkg/proto/orlyacl/) - Update launcher to compute binary names from backend/mode settings - When ACL disabled, relay runs in open mode (no restrictions) - Add Makefile with all-split, arm64-split, and per-binary targets - Include systemd service file for split IPC deployment Files modified: - Makefile: New build system with split binary targets - app/config/config.go: Add ACL gRPC client config options - cmd/orly-acl/: Legacy monolithic ACL server - cmd/orly-acl-curation/main.go: Curation mode binary - cmd/orly-acl-follows/main.go: Follows mode binary - cmd/orly-acl-managed/main.go: Managed mode binary - cmd/orly-db-badger/main.go: Badger backend binary - cmd/orly-db-neo4j/main.go: Neo4j backend binary - cmd/orly-launcher/config.go: Add DBBackend, compute binary names - cmd/orly-launcher/supervisor.go: Handle no-ACL mode, add ACL health check - main.go: Add gRPC ACL client initialization - orly.service: Systemd service for split IPC mode - pkg/acl/acl.go: Add gRPC ACL interface type - pkg/acl/grpc/client.go: gRPC ACL client implementation - pkg/acl/server/: Shared ACL gRPC server package - pkg/database/server/: Shared database gRPC server package - pkg/proto/orlyacl/: ACL service protobuf definitions - pkg/version/version: v0.54.0 - proto/orlyacl/: ACL proto source files Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	4 months ago