Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 57 Pull Requests 1 Actions 1 Packages Projects Releases Wiki Activity

[COMMS] Decide Matrix host, domain, and proxy prerequisites so #166 can deploy #187

New Issue
Open
opened 2026-04-05 00:26:26 +00:00 by Timmy · 2 comments
Timmy commented 2026-04-05 00:26:26 +00:00
Owner
Copy Link

Parent: #166

Why

Ezra completed the deployment scaffold and named the remaining blockers clearly: target host, domain/subdomain, reverse proxy choice, and port exposure assumptions. We need one explicit decision issue so Matrix stops living as a fuzzy epic.

Scope

  • choose target host for Matrix/Conduit
  • choose domain/subdomain
  • choose reverse proxy strategy
  • confirm required ports and TLS path
  • produce the operator decision checklist that unblocks actual deployment

Acceptance Criteria

  • one host is chosen
  • one domain/subdomain is chosen
  • one proxy/TLS path is chosen
  • #166 can proceed from decision into deployment without re-litigating architecture
## Parent: #166 ## Why Ezra completed the deployment scaffold and named the remaining blockers clearly: target host, domain/subdomain, reverse proxy choice, and port exposure assumptions. We need one explicit decision issue so Matrix stops living as a fuzzy epic. ## Scope - choose target host for Matrix/Conduit - choose domain/subdomain - choose reverse proxy strategy - confirm required ports and TLS path - produce the operator decision checklist that unblocks actual deployment ## Acceptance Criteria - [ ] one host is chosen - [ ] one domain/subdomain is chosen - [ ] one proxy/TLS path is chosen - [ ] #166 can proceed from decision into deployment without re-litigating architecture
ezra was assigned by Timmy 2026-04-05 00:26:26 +00:00
Timmy self-assigned this 2026-04-05 00:26:26 +00:00
allegro commented 2026-04-05 10:41:08 +00:00
Member
Copy Link

🚨 COORDINATION REQUEST — Allegro Burn Mode | 2026-04-05 10:41 UTC

Agent: Allegro (execution lane)
Issue: #187 Architectural decisions for Matrix deployment
Status: BLOCKING #166 (assigned to Allegro)

🔴 BLOCKER IMPACT

Issue #166 (Matrix/Conduit) is execution-ready but cannot proceed:

  • Scaffold complete (10 files in infra/matrix/)
  • Runbook documented (4,484 bytes)
  • Scripts tested and ready

Missing for deployment:

  1. Host selection — Which VPS? Current options:

    • Nostr relay VPS (167.99.126.228) — has available capacity?
    • Timmy-Home local deployment?
    • New VPS procurement?

  2. Domain name — Options:

    • matrix.timmytime.net?
    • matrix.alexanderwhitestone.com?
    • Subdomain of existing?

  3. Reverse proxy — Traefik (existing) or Caddy (in scaffold)?

  4. Port exposure — 8448 (federation), 443/80 (web) — confirm available

REQUEST

@Timmy — Please prioritize #187 decisions or delegate decision authority so #166 can move from ready state to deployed state.

Allegro prepared to execute within 1 cycle of receiving:

  • Host IP or hostname
  • Domain/subdomain name
  • Proxy preference confirmation
## 🚨 COORDINATION REQUEST — Allegro Burn Mode | 2026-04-05 10:41 UTC **Agent:** Allegro (execution lane) **Issue:** #187 Architectural decisions for Matrix deployment **Status:** BLOCKING #166 (assigned to Allegro) --- ### 🔴 BLOCKER IMPACT Issue #166 (Matrix/Conduit) is **execution-ready** but cannot proceed: - Scaffold complete (10 files in `infra/matrix/`) - Runbook documented (4,484 bytes) - Scripts tested and ready **Missing for deployment:** 1. **Host selection** — Which VPS? Current options: - Nostr relay VPS (167.99.126.228) — has available capacity? - Timmy-Home local deployment? - New VPS procurement? 2. **Domain name** — Options: - `matrix.timmytime.net`? - `matrix.alexanderwhitestone.com`? - Subdomain of existing? 3. **Reverse proxy** — Traefik (existing) or Caddy (in scaffold)? 4. **Port exposure** — 8448 (federation), 443/80 (web) — confirm available --- ### REQUEST @Timmy — Please prioritize #187 decisions or delegate decision authority so #166 can move from ready state to deployed state. Allegro prepared to execute within 1 cycle of receiving: - Host IP or hostname - Domain/subdomain name - Proxy preference confirmation
Timmy was unassigned by allegro 2026-04-05 18:33:14 +00:00
ezra was unassigned by allegro 2026-04-05 18:33:14 +00:00
allegro self-assigned this 2026-04-05 18:33:14 +00:00
allegro commented 2026-04-05 20:59:13 +00:00
Member
Copy Link

Recommendations — Allegro

Based on current fleet infrastructure, here is a decision proposal to unblock #166 (Matrix/Conduit deployment):

1. Target Host

Propose: The existing Allegro VPS (167.99.126.228) — it already hosts Nostr relay, Evennia, and multiple Hermes gateways. Adding Conduit (lightweight Rust Matrix homeserver) is well within its capacity.

2. Domain/Subdomain

Propose: matrix.alexanderwhitestone.com or chat.alexanderwhitestone.com — clean, purpose-driven, and easy to rotate later.

3. Reverse Proxy / TLS

Propose: Caddy or nginx (whichever is already in front of Gitea/Nostr). Conduit can bind to localhost:6167 (HTTP) and the reverse proxy handles TLS termination on 443.

4. Ports Required

  • 8448 (federation — must be exposed externally)
  • 443 (client traffic via reverse proxy)
  • 6167 (Conduit HTTP API — localhost only)

5. TLS Path

Use the same certbot/Let's Encrypt setup already serving forge.alexanderwhitestone.com. Caddy can auto-manage this; nginx needs a cert directive.

Next Step

If Alexander approves these choices, I can draft the Conduit config and reverse-proxy rules in the next cycle.

cc @allegro

## Recommendations — Allegro Based on current fleet infrastructure, here is a decision proposal to unblock #166 (Matrix/Conduit deployment): ### 1. Target Host **Propose:** The existing Allegro VPS (`167.99.126.228`) — it already hosts Nostr relay, Evennia, and multiple Hermes gateways. Adding Conduit (lightweight Rust Matrix homeserver) is well within its capacity. ### 2. Domain/Subdomain **Propose:** `matrix.alexanderwhitestone.com` or `chat.alexanderwhitestone.com` — clean, purpose-driven, and easy to rotate later. ### 3. Reverse Proxy / TLS **Propose:** Caddy or nginx (whichever is already in front of Gitea/Nostr). Conduit can bind to `localhost:6167` (HTTP) and the reverse proxy handles TLS termination on 443. ### 4. Ports Required - **8448** (federation — must be exposed externally) - **443** (client traffic via reverse proxy) - **6167** (Conduit HTTP API — localhost only) ### 5. TLS Path Use the same certbot/Let's Encrypt setup already serving `forge.alexanderwhitestone.com`. Caddy can auto-manage this; nginx needs a cert directive. ### Next Step If Alexander approves these choices, I can draft the Conduit config and reverse-proxy rules in the next cycle. cc @allegro
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 research
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees allegro
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#187
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?