48c839d927
This is the snapshot the production landing site (nibiru-framework.com) is deployed from. Brings together the recent splash + docs migration to the v4 "Cosmos" design system, the new in-framework AI module, and the framework groundwork that backs the framework-reference extraction. What lands: - docs/: Astro + Starlight site with the v4 dark cosmic palette, GalaxyHero canvas constellation, Mission Control chat (wired to /api/oracle → api.neuronetz.ai via providers.mjs Ollama), 5-panel MMVC stage (Model · AI · Module · Controller · View), translated EN/DE/JA/ES/FR content, PWA + sitemap + llms.txt + Umami analytics. - docs/design-system/: canonical mockup bundle (source/index-v2.html for splash, source/docs-system.html + preview/ for docs, SPEC.md, tokens). - docs/scripts/extraction/framework-reference-v2.md: deep framework reference (~1.6k lines, file:line citations, every public factory and idiom — basis for the LoRA training corpus. - application/module/ai/: AI module with chat / embed / RAG / agent plugins, plus pdoQuery / httpGet / fileRead tools and Modelfile + smoke-test in training/. - application/module/users/: user / ACL / form-factory traits used as the reference plugin pattern for the framework docs. - application/settings/config/database/: schema + seed migrations including the AI module tables (200–203). - Form factory + autogenerator changes the framework-reference-v2 covers. Production secrets stay out: docs/.env, settings.production.ini and ai.production.ini are all gitignored (.example files are in tree). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
39 lines
1.5 KiB
YAML
39 lines
1.5 KiB
YAML
# =============================================================================
|
|
# Local testing override.
|
|
#
|
|
# Use:
|
|
# docker compose -f docker-compose.yml -f docker-compose.local.yml up --build
|
|
#
|
|
# What this changes vs. production:
|
|
# - Publishes the app on http://localhost:4321 (no nginx-proxy needed).
|
|
# - Drops the VIRTUAL_HOST / LETSENCRYPT_HOST env vars.
|
|
# - Maps the production `nginx-proxy` network reference to the local
|
|
# `backend` network — local dev boxes here use `backend` (also external)
|
|
# as their proxy network instead of jwilder's default `nginx-proxy` name.
|
|
# If you don't have a local proxy at all, comment the networks: blocks
|
|
# out and use `network_mode: "host"` (uncomment below) so the container
|
|
# can reach Ollama on localhost:11434.
|
|
# =============================================================================
|
|
|
|
services:
|
|
docs:
|
|
ports:
|
|
- "4321:4321"
|
|
environment:
|
|
VIRTUAL_HOST: ""
|
|
VIRTUAL_PORT: ""
|
|
LETSENCRYPT_HOST: ""
|
|
LETSENCRYPT_EMAIL: ""
|
|
# If you run Ollama on the same machine and have no proxy network, uncomment:
|
|
# network_mode: "host"
|
|
# And in your .env:
|
|
# OLLAMA_BASE_URL=http://127.0.0.1:11434
|
|
|
|
# Compose merges these into the production file's `networks:` block. The
|
|
# `name:` override re-points the production reference (`nginx-proxy`) at
|
|
# whatever Docker network actually exists locally — here, `backend`.
|
|
networks:
|
|
nginx-proxy:
|
|
name: backend
|
|
external: true
|