Tyler J King
4e22729bef
Ceremony orchestrator + governance UI layer over substrate CRDs. guildhall presents and coordinates; substrate decides and enforces. Apps: - guildhall_web: Phoenix LiveView UI for ceremony workflows, Forge visualization, posture dashboards - guildhall_orchestrator: watches CeremonyRequest CRDs, notifies witnesses, collects signatures, tracks ceremony lifecycle - guildhall_ops_db: Ecto schemas for the five Ops DB tables (per DESIGN-OPS-DB-CHAIN-OF-CUSTODY-0001) - guildhall_graph_bridge: Microsoft Graph API reconciler (stub) - guildhall_chronicle: Chronicle event consumer + Ops DB projector (stub) Naming: guildhall components are orchestrators (workflow), NOT engines (enforcement). The ceremony engine is a substrate K8s operator. guildhall coordinates humans around CRDs. Elixir 1.17.3 / OTP 27 / Phoenix 1.8.5. SHA-256 git repo. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Tyler J King <tking@guildhouse.dev>
16 lines
377 B
Elixir
16 lines
377 B
Elixir
import Config
|
|
|
|
config :guildhall_web, GuildhallWeb.Endpoint,
|
|
cache_static_manifest: "priv/static/cache_manifest.json"
|
|
|
|
config :guildhall_web, GuildhallWeb.Endpoint,
|
|
force_ssl: [
|
|
rewrite_on: [:x_forwarded_proto],
|
|
exclude: [
|
|
hosts: ["localhost", "127.0.0.1"]
|
|
]
|
|
]
|
|
|
|
config :logger, level: :info
|
|
|
|
# Runtime production configuration is in config/runtime.exs.
|