hero_services stabilize #20

New issue

Open

opened 2026-02-23 09:46:13 +00:00 by despiegk · 0 comments

despiegk commented

2026-02-23 09:46:13 +00:00

Owner

put full openrpc in which exposes all features from hero_service
make integration tests using this openrpc
use zinit jobs for everything which is one off (make skill for it)
remove all ports from server services, only unix sockets
for ui services: keep http interface with rpc post (which get's proxied to backend)
serious integration tests
consistency for clients/sdk for generated and non generated clients for servers (openrpc)
update skills
use macro for openrpc client in services

see what needs to be resolved in https://forge.ourworld.tf/lhumina_code/hero_services/issues

skill /hero_crates_best_practices_check

requirements

zinit sdk used everywhere
start is part of _ui and _server so we start ourselves basically using zinit sdk
use only openrpc over UDS socket on server and ui unless if needed because other protocol e.g. redis and zinit itself and...
ui uses sdk, sdk uses openrpc to server, server does not use sdk
its in line with skill: /hero_crates_best_practices_check unless the exceptions
remove ALL branches only remain. main/development/development_$username for active branches
NO branches apart from development and main should be active + 2 days (always some exceptions make the rule)
all services in service manager so its easy to use

- put full openrpc in which exposes all features from hero_service - make integration tests using this openrpc - use zinit jobs for everything which is one off (make skill for it) - remove all ports from server services, only unix sockets - for ui services: keep http interface with rpc post (which get's proxied to backend) - serious integration tests - consistency for clients/sdk for generated and non generated clients for servers (openrpc) - update skills - use macro for openrpc client in services see what needs to be resolved in https://forge.ourworld.tf/lhumina_code/hero_services/issues skill /hero_crates_best_practices_check ## requirements - [ ] zinit sdk used everywhere - [ ] start is part of _ui and _server so we start ourselves basically using zinit sdk - [ ] use only openrpc over UDS socket on server and ui unless if needed because other protocol e.g. redis and zinit itself and... - [ ] ui uses sdk, sdk uses openrpc to server, server does not use sdk - [ ] its in line with skill: /hero_crates_best_practices_check unless the exceptions - [ ] remove ALL branches only remain. main/development/development_$username for active branches - [ ] NO branches apart from development and main should be active + 2 days (always some exceptions make the rule) - [ ] all services in service manager so its easy to use