chore: rename cameleer3 to cameleer
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:
@@ -2,7 +2,7 @@
|
||||
|
||||
**Date:** 2026-04-11
|
||||
**Status:** Approved
|
||||
**Scope:** cameleer3-server + cameleer-saas
|
||||
**Scope:** cameleer-server + cameleer-saas
|
||||
|
||||
---
|
||||
|
||||
@@ -113,7 +113,7 @@ returns 404 and the page shows its existing error state.
|
||||
|
||||
The SaaS platform sits on the same Docker network as PostgreSQL and ClickHouse.
|
||||
It already has their connection URLs in `ProvisioningProperties` (`datasourceUrl`
|
||||
for cameleer3 PostgreSQL, `clickhouseUrl` for ClickHouse). It already uses raw
|
||||
for cameleer PostgreSQL, `clickhouseUrl` for ClickHouse). It already uses raw
|
||||
JDBC (`DriverManager.getConnection()`) for tenant data cleanup in
|
||||
`TenantDataCleanupService`. The infrastructure dashboard uses the same pattern.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user