cameleer/cameleer-server

Fork 0

Files

hsiegeln b393d262cb

CI / build (push) Successful in 1m7s

Details

CI / cleanup-branch (push) Has been skipped

Details

CI / docker (push) Successful in 41s

Details

CI / deploy (push) Successful in 39s

Details

CI / deploy-feature (push) Has been skipped

Details

refactor: remove OIDC env var config and seeder

OIDC configuration is already fully database-backed (oidc_config table,
admin API, OidcConfigRepository). Remove the redundant env var binding
(SecurityProperties.Oidc), the env-to-DB seeder (oidcConfigSeeder), and
the OIDC section from application.yml.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-17 13:20:35 +01:00

3.0 KiB

Raw Blame History

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project

Cameleer3 Server — observability server that receives, stores, and serves Camel route execution data and route diagrams from Cameleer3 agents. Pushes config and commands to agents via SSE.

cameleer3 (https://gitea.siegeln.net/cameleer/cameleer3) — the Java agent that instruments Camel applications
Protocol defined in cameleer3-common/PROTOCOL.md in the agent repo
This server depends on com.cameleer3:cameleer3-common (shared models and graph API)

Modules

cameleer3-server-core — domain logic, storage, agent registry
cameleer3-server-app — Spring Boot web app, REST controllers, SSE, static resources

Build Commands

mvn clean compile          # Compile all modules
mvn clean verify           # Full build with tests

Run

java -jar cameleer3-server-app/target/cameleer3-server-app-1.0-SNAPSHOT.jar

Key Conventions

Java 17+ required
Spring Boot 3.4.3 parent POM
Depends on com.cameleer3:cameleer3-common from Gitea Maven registry
Jackson JavaTimeModule for Instant deserialization
Communication: receives HTTP POST data from agents, serves SSE event streams for config push/commands
Maintains agent instance registry with states: LIVE → STALE → DEAD
Storage: PostgreSQL (TimescaleDB) for structured data, OpenSearch for full-text search
Security: JWT auth with RBAC (AGENT/VIEWER/OPERATOR/ADMIN roles), Ed25519 config signing, bootstrap token for registration
OIDC: Optional external identity provider support (token exchange pattern). Configured via admin API, stored in database (oidc_config table)
User persistence: PostgreSQL users table, admin CRUD at /api/v1/admin/users

CI/CD & Deployment

CI workflow: .gitea/workflows/ci.yml — build → docker → deploy on push to main or feature branches
Build step skips integration tests (-DskipITs) — Testcontainers needs Docker daemon
Docker: multi-stage build (Dockerfile), $BUILDPLATFORM for native Maven on ARM64 runner, amd64 runtime
REGISTRY_TOKEN build arg required for cameleer3-common dependency resolution
Registry: gitea.siegeln.net/cameleer/cameleer3-server (container images)
K8s manifests in deploy/ — Kustomize base + overlays (main/feature), shared infra (PostgreSQL, OpenSearch, Authentik) as top-level manifests
Deployment target: k3s at 192.168.50.86, namespace cameleer (main), cam-<slug> (feature branches)
Feature branches: isolated namespace, PG schema, OpenSearch index prefix; Traefik Ingress at <slug>-api.cameleer.siegeln.net
Secrets managed in CI deploy step (idempotent --dry-run=client | kubectl apply): cameleer-auth, postgres-credentials, opensearch-credentials
K8s probes: server uses /api/v1/health, PostgreSQL uses pg_isready, OpenSearch uses /_cluster/health
Docker build uses buildx registry cache + --provenance=false for Gitea compatibility

3.0 KiB Raw Blame History

CLAUDE.md

Project

Related Project

Modules

Build Commands

Run

Key Conventions

CI/CD & Deployment

3.0 KiB

Raw Blame History