[hero_proc] Support per-user hero_proc instance #70

New issue

Closed

opened 2026-04-29 07:10:23 +00:00 by mahmoud · 0 comments

mahmoud commented

2026-04-29 07:10:23 +00:00

Owner

Problem

Currently hero_proc requires root to run. The goal is that each user
(e.g. the driver user) has their own hero_proc instance running under
their own account, so we don't have to run everything as root.

Requirements

hero_proc should be startable as a non-root user
Each user gets their own hero_proc instance
Socket path scoped per user: $HERO_SOCKET_DIR/hero_proc/rpc.sock
should resolve correctly per user context
hero_codescalers and other services should be driven from the
driver user's hero_proc, not root's
Only hero_router needs to run as root (for port binding)

Relevant code

crates/hero_proc_server/ — supervisor daemon
crates/hero_proc_lib/ — SQLite persistence layer

Acceptance Criteria

hero_proc starts and runs correctly as driver user
Socket is accessible under the user's context
hero_codescalers and other services can be managed from user-level hero_proc
Only hero_router requires root

## Problem Currently hero_proc requires root to run. The goal is that each user (e.g. the `driver` user) has their own hero_proc instance running under their own account, so we don't have to run everything as root. ## Requirements - hero_proc should be startable as a non-root user - Each user gets their own hero_proc instance - Socket path scoped per user: `$HERO_SOCKET_DIR/hero_proc/rpc.sock` should resolve correctly per user context - hero_codescalers and other services should be driven from the driver user's hero_proc, not root's - Only hero_router needs to run as root (for port binding) ## Relevant code - `crates/hero_proc_server/` — supervisor daemon - `crates/hero_proc_lib/` — SQLite persistence layer ## Acceptance Criteria - [ ] hero_proc starts and runs correctly as `driver` user - [ ] Socket is accessible under the user's context - [ ] hero_codescalers and other services can be managed from user-level hero_proc - [ ] Only hero_router requires root