geomind_code/dev_docs
22
0
Fork 0
Code Issues 10 Pull requests 1 Projects Releases 2 Packages 1 Wiki Activity Actions

Update skills to reflect Unix socket model as primary deployment #24

New issue
Open
opened 2026-02-20 02:03:15 +00:00 by mik-tf · 0 comments
mik-tf commented 2026-02-20 02:03:15 +00:00
Member
Copy link

Context

Hero services now use Unix domain sockets via hero_proxy as the primary deployment model. TCP ports are the standalone dev fallback. The hero_sockets and hero_ports skills already document this, but makefile_helper and build_lib still present TCP ports as the default without socket context.

Changes needed

  • makefile_helper: Clarify PORT is for standalone dev, add note about socket-based production deployment, reference hero_sockets skill
  • build_lib: Add note that PORTS in buildenv.sh is for dev fallback / port registry identity, not production binding. Reference hero_sockets for production.

Both skills should cross-reference hero_sockets so readers know the full picture.

## Context Hero services now use Unix domain sockets via hero_proxy as the primary deployment model. TCP ports are the standalone dev fallback. The `hero_sockets` and `hero_ports` skills already document this, but `makefile_helper` and `build_lib` still present TCP ports as the default without socket context. ## Changes needed - **`makefile_helper`**: Clarify PORT is for standalone dev, add note about socket-based production deployment, reference `hero_sockets` skill - **`build_lib`**: Add note that `PORTS` in buildenv.sh is for dev fallback / port registry identity, not production binding. Reference `hero_sockets` for production. Both skills should cross-reference `hero_sockets` so readers know the full picture.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
development
development_mik
main
latest
v1.0.0
v0.1.0
v0.0.1-rc1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
geomind_code/dev_docs#24
No description provided.