chore: align public-facing assets with cameleer.io
All checks were successful
Build & Publish / publish (push) Successful in 2m16s
SonarQube Analysis / sonarqube (push) Successful in 3m57s

Replace personal/internal references in shipped artifacts ahead of
institutionalizing the product. registry.cameleer.io becomes the public
endpoint for the npm package and repository URL; gitea.siegeln.net
remains the internal CI publish target. Mock seed-admin renamed from
"Hendrik Siegeln" to "Ada Sterling" across pages, audit log, RBAC
mocks, and ui-mocks; Java exception namespace switched from
com.cameleer3 to io.cameleer in the route detail mock.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
hsiegeln
2026-04-28 17:35:56 +02:00
parent 2bf4144380
commit 0c4a6d430e
22 changed files with 50 additions and 50 deletions

View File

@@ -51,18 +51,18 @@ import { ThemeProvider } from '../design-system/providers/ThemeProvider'
This design system is published as `@cameleer/design-system` to the Gitea npm registry.
### Registry: `https://gitea.siegeln.net/api/packages/cameleer/npm/`
### Registry: `https://registry.cameleer.io/api/packages/cameleer/npm/`
### Setup in a consuming app
1. Add `.npmrc` to the project root:
```
@cameleer:registry=https://gitea.siegeln.net/api/packages/cameleer/npm/
//gitea.siegeln.net/api/packages/cameleer/npm/:_authToken=${GITEA_TOKEN}
@cameleer:registry=https://registry.cameleer.io/api/packages/cameleer/npm/
//registry.cameleer.io/api/packages/cameleer/npm/:_authToken=${REGISTRY_TOKEN}
```
Note: CI pipelines for consuming apps also need this `.npmrc` and a `GITEA_TOKEN` secret to fetch the package during `npm ci`.
Note: CI pipelines for consuming apps also need this `.npmrc` and a `REGISTRY_TOKEN` secret to fetch the package during `npm ci`.
2. Install:
@@ -132,7 +132,7 @@ import camelSvg from '@cameleer/design-system/assets/camel-logo.svg' // simp
<!-- gitnexus:start -->
# GitNexus — Code Intelligence
This project is indexed by GitNexus as **design-system** (1536 symbols, 2408 relationships, 23 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
This project is indexed by GitNexus as **design-system** (1537 symbols, 2409 relationships, 23 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
> If any GitNexus tool warns the index is stale, run `npx gitnexus analyze` in terminal first.