Skip to content

start-cli v1.0.3

Latest

Choose a tag to compare

@dr-bonez dr-bonez released this 14 Jul 00:53
b14b742

What's Changed

Added

  • host/registry profiles work in every config file, not just the workspace. A config
    file's host/registry is a namespace of named profiles — default, prod, whatever you
    like — and a bare URL is shorthand for the default profile, so a legacy flat
    host: https://box.local still targets that URL. Profiles from a -c file, the workspace
    .startos/config.yaml, ~/.startos/config.yaml, and /etc/startos/config.yaml all combine
    into one namespace, so you can keep reusable profiles in your home config and reach them from
    anywhere — inside a packaging workspace or not. A profile's value can be a URL or the name of
    another profile, and -H/-r just set the default profile for that invocation (-H prod
    points default at your prod profile); resolution follows the chain to a URL. A value that
    isn't a URL is reported only when it's the one resolved, so a stale ambient config never fails an
    unrelated command.

Fixed

  • .local (mDNS) hostnames resolve again. Every command against a .local address — the
    way most people reach their server — failed after ~5s with an opaque
    error sending request for url (...), while curl against the same URL succeeded instantly.
    start-cli ships as a statically linked musl binary, and musl's getaddrinfo implements no
    NSS: it ignores /etc/nsswitch.conf, so mdns4_minimal is never consulted and the lookup
    falls through to unicast DNS, which dies on musl's hard-coded 5s timeout. A .local host is
    now resolved through the system resolver (getent, the same path curl takes) when the
    client context is built, so the HTTP client and the log/progress websockets alike are handed
    an address. Linux only — macOS resolves .local natively. (#3469)

  • An ambient config file no longer shadows the workspace .startos/config.yaml. A host
    set in ~/.startos/config.yaml or /etc/startos/config.yaml was merged into the same field as
    an explicit -H/-r, so it silently outranked the workspace's default profile — the opposite
    of the documented layering, and a trap for anyone with a leftover pre-1.0 flat config in their
    home directory. Profiles now layer in a strict order, highest precedence first: a command-line
    flag (-H/-r), a config file named with -c, the workspace config, ~/.startos/config.yaml,
    then /etc/startos/config.yaml. Where the same profile name is defined at more than one level
    the higher tier wins; what you name on the command line overrides the workspace, what you don't
    is an ambient default beneath it. A -H/-r naming an unknown profile still errors rather than
    quietly falling through to a lower tier.

start-cli Checksums

SHA-256

c9994c74bbeafb28d9542437b9cfdae450b375ebfc0894aeda33b73a2e2cc46f  start-cli_aarch64-linux
6b4f25dec7c0f285fa4e3d5244e255392dce8df3ddcc4fec818a59bc7d4f32a5  start-cli_aarch64-macos
946f6c1bb1eb6265a8c47e95cbfd582f6c97935544be63b992132e99d6e079e8  start-cli_riscv64-linux
c7e4c990eb5da600958937fd869f5c3fc394c5639c7fa7579e0c344b2a7750e8  start-cli_x86_64-linux
3a0f80e9d05e3a1a44bce2868494930ae6597a73f4376de3b3ad9d17d1824732  start-cli_x86_64-macos

BLAKE-3

9fe10538c8693177657450c8290cae36d99188a7812fa6f78bf53d5154689f7f  start-cli_aarch64-linux
614487194c40bd16f59d232b12e5f8edae421ba401614c87c0d196aef53c673a  start-cli_aarch64-macos
a32095d6c9d7e60a8a21a8cab3c25c0be9ffae8279e7073527c51ce9cc360d68  start-cli_riscv64-linux
abb1972fc06d9355b5f65ebba8f45c43d9697849181a4fcbc585c27b83f4eebb  start-cli_x86_64-linux
845a7e1bf8fb1c018f8974fec204cb12fd95931cb411fb765fd73afbaf5ad296  start-cli_x86_64-macos

start-cli packages Checksums

SHA-256

0b71e5bc65d599ee9e79038d30cb8e6a961f755d01800d8f2969279e44b19762  start-cli-1.0.3-b14b742~dev_aarch64.deb
f1d33d046b9024ae8d39ae64471ee01f736969dce675e9ea1e147d366f97b5f3  start-cli-1.0.3-b14b742~dev_riscv64.deb
ccf90d4525f799eaab31ea2bbca6fe0bed57f293cfb212c6e5678434e5995dda  start-cli-1.0.3-b14b742~dev_x86_64.deb

BLAKE-3

fd217fbe759750eacb5e3d042d1543509b850480052c41df7330ec0a55015e12  start-cli-1.0.3-b14b742~dev_aarch64.deb
0576865a0a59c0e1e27909f5a70620a78eaf33afed3017844d4ad20f09095f90  start-cli-1.0.3-b14b742~dev_riscv64.deb
d57200f224a5b8f6c615f78e70ec018eda52b3c979229b26b03e198ad930c56b  start-cli-1.0.3-b14b742~dev_x86_64.deb