6 Commits

Author	SHA1	Message	Date
hsiegeln	9ed2cedc98	feat: self-service sign-up with email verification and onboarding ... Complete sign-up pipeline: email registration via Logto Experience API, SMTP email verification, and self-service trial tenant creation. Layer 1 — Logto config: - Bootstrap Phase 8b: SMTP email connector with branded HTML templates - Bootstrap Phase 8c: enable SignInAndRegister (email+password sign-up) - Dockerfile installs official Logto connectors (ensures SMTP available) - SMTP env vars in docker-compose, installer templates, .env.example Layer 2 — Experience API (ui/sign-in/experience-api.ts): - Registration flow: initRegistration → sendVerificationCode → verifyCode → addProfile (password) → identifyUser → submit - Sign-in auto-detects email vs username identifier Layer 3 — Custom sign-in UI (ui/sign-in/SignInPage.tsx): - Three-mode state machine: signIn / register / verifyCode - Reads first_screen=register from URL query params - Toggle links between sign-in and register views Layer 4 — Post-registration onboarding: - OnboardingService: reuses VendorTenantService.createAndProvision(), adds calling user to Logto org as owner, enforces one trial per user - OnboardingController: POST /api/onboarding/tenant (authenticated only) - OnboardingPage.tsx: org name + auto-slug form - LandingRedirect: detects zero orgs → redirects to /onboarding - RegisterPage.tsx: /platform/register initiates OIDC with firstScreen Installers (install.sh + install.ps1): - Both prompt for SMTP config in SaaS mode - CLI args, env var capture, cameleer.conf persistence Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-25 00:21:07 +02:00
hsiegeln	fa6bca0add	fix: use apk instead of apt-get in Logto Dockerfile ... The Logto base image (ghcr.io/logto-io/logto:latest) is Alpine-based, not Debian. Switch from apt-get to apk for installing bootstrap deps. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-13 16:47:05 +02:00
hsiegeln	ec38d0b1c2	feat: merge bootstrap into cameleer-logto image ... Adds logto-entrypoint.sh that seeds DB, starts Logto, waits for health, runs bootstrap, then keeps Logto running. Eliminates the separate logto-bootstrap init container.	2026-04-13 16:17:13 +02:00
hsiegeln	3ca13b6b88	perf: add BuildKit cache mounts for Maven and npm in Docker builds ... Maven .m2 and npm caches persist across --no-cache builds, avoiding full dependency re-downloads on every CI run. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-06 22:29:14 +02:00
hsiegeln	3fcbc431fb	fix: restore multi-stage Dockerfiles, use cameleer-docker-builder ... Follow cameleer3-server CI pattern: docker job uses cameleer-docker-builder:1 (has Docker CLI), Dockerfiles contain multi-stage builds (self-contained, no external toolchain needed). - Dockerfile: restore frontend + maven + runtime stages - ui/sign-in/Dockerfile: add node build stage + Logto base - ci.yml: docker job reverts to cameleer-docker-builder:1, passes REGISTRY_TOKEN as build-arg, adds build cache Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-06 15:51:59 +02:00
hsiegeln	ad97a552f6	refactor: no builds in Dockerfiles, CI builds all artifacts ... Dockerfiles now only COPY pre-built artifacts: - Dockerfile (SaaS): just COPY target/*.jar, no multi-stage build - ui/sign-in/Dockerfile (Logto): just FROM logto + COPY dist/ - Removed docker/logto.Dockerfile (had node build stage) CI pipeline builds everything: - docker job: builds frontend, JAR, sign-in UI, then packages into images using the simple Dockerfiles - Uses cameleer-build:1 (has node + maven + docker) - build job: also builds sign-in UI for testing Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-06 15:39:19 +02:00