Add manage.sh: start|stop|restart|status|logs #1

New issue

Open

opened 2026-04-06 22:25:18 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-04-06 22:25:18 -07:00

Owner

Summary

Every CF product has a manage.sh as the single operational entrypoint. Minerva currently starts with a raw python invocation. manage.sh becomes the canonical source of truth for port, conda env, and model paths.

Minimum interface

./manage.sh start    # start voice server with uvicorn
./manage.sh stop
./manage.sh restart
./manage.sh status
./manage.sh logs     # tail journalctl or log file
./manage.sh open     # open server URL in browser (optional)

Key decisions to encode

PORT=5000 (or standardize to 85xx range — see port issue)
CONDA_ENV=cf (CF standard)
MODEL_PATH from config/.env
Preflight: check conda env, check .env exists, check port free

References

Peregrine manage.sh as reference implementation
cf-dev review finding: Priority 1 blocker

## Summary Every CF product has a `manage.sh` as the single operational entrypoint. Minerva currently starts with a raw `python` invocation. `manage.sh` becomes the canonical source of truth for port, conda env, and model paths. ## Minimum interface ```bash ./manage.sh start # start voice server with uvicorn ./manage.sh stop ./manage.sh restart ./manage.sh status ./manage.sh logs # tail journalctl or log file ./manage.sh open # open server URL in browser (optional) ``` ## Key decisions to encode - `PORT=5000` (or standardize to 85xx range — see port issue) - `CONDA_ENV=cf` (CF standard) - `MODEL_PATH` from config/.env - Preflight: check conda env, check .env exists, check port free ## References - Peregrine manage.sh as reference implementation - cf-dev review finding: Priority 1 blocker