chore: rename cameleer3 to cameleer
Some checks failed
CI / cleanup-branch (push) Has been skipped
CI / build (push) Failing after 18s
CI / docker (push) Has been skipped
CI / deploy (push) Has been skipped
CI / deploy-feature (push) Has been skipped

Rename Java packages from com.cameleer3 to com.cameleer, module
directories from cameleer3-* to cameleer-*, and all references
throughout workflows, Dockerfiles, docs, migrations, and pom.xml.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
hsiegeln
2026-04-15 15:28:42 +02:00
parent 1077293343
commit cb3ebfea7c
569 changed files with 4356 additions and 3245 deletions

View File

@@ -2,7 +2,7 @@
## Goal
Standalone demo prototype: upload a Camel JAR, build a container image with the cameleer3 monitoring agent injected, deploy to k3s, and see full observability appear in cameleer3-server.
Standalone demo prototype: upload a Camel JAR, build a container image with the cameleer monitoring agent injected, deploy to k3s, and see full observability appear in cameleer-server.
## Project
@@ -35,7 +35,7 @@ Deploy Service (Spring Boot 3, Java 21, port 8082)
├─► Gitea Container Registry (images)
├─► k3s cluster / cameleer-demo namespace (workloads)
└─► cameleer3-server (agents auto-register via bootstrap token)
└─► cameleer-server (agents auto-register via bootstrap token)
```
## No Auth
@@ -49,11 +49,11 @@ Generated Dockerfile per app:
```dockerfile
FROM eclipse-temurin:21-jre-alpine
ADD https://gitea.siegeln.net/api/packages/cameleer/maven/com/cameleer3/cameleer3-agent/1.0-SNAPSHOT/cameleer3-agent-1.0-SNAPSHOT.jar /opt/cameleer/agent.jar
ADD https://gitea.siegeln.net/api/packages/cameleer/maven/com/cameleer/cameleer-agent/1.0-SNAPSHOT/cameleer-agent-1.0-SNAPSHOT.jar /opt/cameleer/agent.jar
COPY app.jar /opt/app/app.jar
ENV CAMELEER_SERVER_URL=http://cameleer3-server.cameleer.svc:8081
ENV CAMELEER_SERVER_URL=http://cameleer-server.cameleer.svc:8081
ENV CAMELEER_APP_NAME=<user-provided-name>
ENV CAMELEER_AUTH_TOKEN=<bootstrap-token>
@@ -68,7 +68,7 @@ Each app gets a Deployment in the `cameleer-demo` namespace:
- Resource requests/limits from user config (defaults: 250m/256Mi requests, 500m/512Mi limits)
- User-provided env vars injected into the container spec
- No Service or Ingress (apps only need outbound access to cameleer3-server)
- No Service or Ingress (apps only need outbound access to cameleer-server)
- Labels: `app.kubernetes.io/managed-by: cameleer-deploy`, `cameleer/app-name: <name>`
## Data Model (In-Memory)
@@ -101,7 +101,7 @@ On GET /api/apps, reconcile status with actual K8s pod phase via kubectl. On sta
| Column | Content |
|--------|---------|
| Name | Clickable → cameleer3-server exchanges page |
| Name | Clickable → cameleer-server exchanges page |
| Status | Badge: Running / Pending / Failed / Building |
| Image | Image tag (mono text) |
| Resources | CPU/Memory limits |
@@ -124,7 +124,7 @@ All components from @cameleer/design-system. CSS modules for layout.
## Configuration
Deploy service env vars:
- `CAMELEER_SERVER_URL` — cameleer3-server URL for agent registration (default: `http://cameleer3-server.cameleer.svc:8081`)
- `CAMELEER_SERVER_URL` — cameleer-server URL for agent registration (default: `http://cameleer-server.cameleer.svc:8081`)
- `CAMELEER_BOOTSTRAP_TOKEN` — bootstrap token for agent registration
- `CAMELEER_REGISTRY` — container registry prefix (default: `gitea.siegeln.net/cameleer/demo-apps`)
- `CAMELEER_AGENT_MAVEN_URL` — URL for agent snapshot JAR
@@ -139,7 +139,7 @@ Deploy service env vars:
- Container: Docker (multi-stage build)
- Deploy: k3s at 192.168.50.86, namespace `cameleer-demo`
- Registry: Gitea container registry
- Agent: cameleer3-agent 1.0-SNAPSHOT from Gitea Maven registry
- Agent: cameleer-agent 1.0-SNAPSHOT from Gitea Maven registry
## Out of Scope