You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An evalhub server command group for managing the eval-hub-server lifecycle:
evalhub server run — run the server in the foreground.
evalhub server start — start the server as a background daemon (writes a PID file and log file, waits for the health endpoint before reporting success).
evalhub server stop — stop the background daemon (graceful shutdown with a timeout, then force-kill).
evalhub server status — report whether the server is running and healthy, including URL and log path when available.
Server configuration management through the existing evalhub config workflow using a new server_config_file key:
evalhub config set server_config_file <path> — validates the YAML file and stores a profile-scoped copy under ~/.config/evalhub/server/<profile>/config.yaml.
evalhub config get server_config_file / show — displays the stored value.
evalhub config unset server_config_file — removes the stored config file and cleans up the profile directory.
A new --unfold flag on evalhub config get to print the contents of file-based configuration values (currently only applicable to server_config_file).
Support for TLS-enabled servers (health checks over HTTPS, https:// URLs reported in start/status output).
Requested documentation updates
Add a new "Server" section to the CLI reference documenting evalhub server run|start|stop|status, including example invocations (foreground vs background) and description of PID/log file locations.
Document the server_config_file config key: how to set/get/unset it, and the YAML validation requirements (must exist, be valid YAML, and be a mapping).
Document the --unfold flag on evalhub config get, its mutual exclusivity with --unmask, and that it only applies to file-based config keys.
Include examples covering: starting the server in the foreground, starting/stopping in the background, checking status, handling TLS, and removing the server config setting.
Summary
Document the new
evalhub serverCLI command group and related server configuration management introduced in eval-hub/eval-hub-sdk#149.Background
PR eval-hub/eval-hub-sdk#149 adds:
evalhub servercommand group for managing theeval-hub-serverlifecycle:evalhub server run— run the server in the foreground.evalhub server start— start the server as a background daemon (writes a PID file and log file, waits for the health endpoint before reporting success).evalhub server stop— stop the background daemon (graceful shutdown with a timeout, then force-kill).evalhub server status— report whether the server is running and healthy, including URL and log path when available.evalhub configworkflow using a newserver_config_filekey:evalhub config set server_config_file <path>— validates the YAML file and stores a profile-scoped copy under~/.config/evalhub/server/<profile>/config.yaml.evalhub config get server_config_file/show— displays the stored value.evalhub config unset server_config_file— removes the stored config file and cleans up the profile directory.--unfoldflag onevalhub config getto print the contents of file-based configuration values (currently only applicable toserver_config_file).https://URLs reported instart/statusoutput).Requested documentation updates
evalhub server run|start|stop|status, including example invocations (foreground vs background) and description of PID/log file locations.server_config_fileconfig key: how to set/get/unset it, and the YAML validation requirements (must exist, be valid YAML, and be a mapping).--unfoldflag onevalhub config get, its mutual exclusivity with--unmask, and that it only applies to file-based config keys.References