Go live: roll out the eco-gnome deploy slot to kai-server (eco-app#40 Phase 1) #45
Labels
No labels
burndown-2026-06
burndown-2026-08
headless
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/eco-app#45
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
eco-app#40 Phase 1 landed a self-hosted Eco Gnome deploy slot in coilyco-bridge/deploy (services/eco-gnome). It pins the upstream published images (ghcr.io/eco-gnome/eco-gnome-website + a -migrator), so no fork and no .NET build. The slot is ready but NOT live.
Ask (operator rollout)
Roll out the services/eco-gnome slot to kai-server - the operator deploy (Flux / k3s or the deploy repo's rollout path) - serving the calculator at eco-app.coilysiren.me/calculator. The /calculator surface already landed on eco-app main.
Then Phase 2 (tracked on eco-app#40, still open)
Related
eco-app#40 (Phase 1 slot + Phase 2), coilyco-bridge/deploy services/eco-gnome, eco-app#37 (website epic).
Scope update: the 'Reskin from eco-gnome's default look to house style' bullet under 'Then Phase 2' is dropped - Kai decided eco-app keeps the stock upstream Eco Gnome UI permanently (eco-app#47, landed in eco-app@70a5a40). The rollout ask and the DataExporter bullet are unchanged.