Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[OpenClaw 1/8] Audit Hermes VPS resources and prepare for OpenClaw deployment #724

New Issue
Closed
opened 2026-03-21 13:57:22 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-21 13:57:22 +00:00
Collaborator
Copy Link

Description

Before installing anything, audit the Hermes VPS to understand what we're working with.

Tasks

  1. Check VPS specs — CPU cores, RAM, disk space, swap, OS version
  2. Check existing services — What's already running? (Gitea, any Docker containers, Tailscale)
  3. Check disk usage — How much free space for models and OpenClaw workspace?
  4. Check Tailscale status — Is Tailscale running? Can we access the VPS via Tailscale hostname?
  5. Check Node.js — Is Node 22+ or 24 installed? If not, note what's needed
  6. Check Docker — Is Docker installed and running?
  7. Document findings — Post results as a comment on this issue

Acceptance Criteria

  • VPS resource audit is documented
  • Available headroom for Ollama + OpenClaw is quantified
  • Any blockers are identified (e.g., not enough RAM, missing deps)
  • Findings inform whether we go Docker or bare-metal install

Constraints

  • Do NOT install anything yet — this is observation only
  • Use local inference where possible to check

Parent epic: rockachopa/Timmy-time-dashboard#663

Migrated from perplexity/the-matrix#115

## Description Before installing anything, audit the Hermes VPS to understand what we're working with. ### Tasks 1. **Check VPS specs** — CPU cores, RAM, disk space, swap, OS version 2. **Check existing services** — What's already running? (Gitea, any Docker containers, Tailscale) 3. **Check disk usage** — How much free space for models and OpenClaw workspace? 4. **Check Tailscale status** — Is Tailscale running? Can we access the VPS via Tailscale hostname? 5. **Check Node.js** — Is Node 22+ or 24 installed? If not, note what's needed 6. **Check Docker** — Is Docker installed and running? 7. **Document findings** — Post results as a comment on this issue ### Acceptance Criteria - [ ] VPS resource audit is documented - [ ] Available headroom for Ollama + OpenClaw is quantified - [ ] Any blockers are identified (e.g., not enough RAM, missing deps) - [ ] Findings inform whether we go Docker or bare-metal install ### Constraints - Do NOT install anything yet — this is observation only - Use local inference where possible to check > Parent epic: rockachopa/Timmy-time-dashboard#663 --- _Migrated from perplexity/the-matrix#115_
kimi was assigned by Timmy 2026-03-21 18:02:08 +00:00
kimi added this to the OpenClaw Sovereignty milestone 2026-03-21 20:24:22 +00:00
claude added the rejected-direction label 2026-03-23 13:51:16 +00:00
perplexity commented 2026-03-23 13:52:03 +00:00
Author
Collaborator
Copy Link

🧹 Closed — Rejected Direction (OpenClaw)

OpenClaw direction was explicitly rejected by the principal. The harness is the product — sovereign AI runs on Hermes with local models, not OpenClaw.

Ref: Deep Backlog Triage #1076. Reopen if needed.

🧹 **Closed — Rejected Direction (OpenClaw)** OpenClaw direction was explicitly rejected by the principal. The harness is the product — sovereign AI runs on Hermes with local models, not OpenClaw. Ref: Deep Backlog Triage #1076. Reopen if needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label rejected-direction
Milestone
No items
No Milestone OpenClaw Sovereignty
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees kimi
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#724
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?