curl for a Nexus raw repository¶
nxr publishes and fetches version directories whose files are digest-verified on the way in and on the way out.
One binary, nothing to install on the server: the URL in argv, credentials from the call or the environment, and an alias file read only when -R names it.
The 30-second version¶
What the recording shows, one beat per command:
- Publish:
nxr upputs a version directory on the server, the claim name first, then the bytes and their.sha256markers. - Name:
nxr channel set --if-forwardpointslatestat it, and a pointer only moves forward. - Fetch:
nxr downpulls that version back, and an interrupted pull resumes by repeating the same command. - Verify:
nxr verifychecks every digest offline, no network.
Every line is real output: the binary this repository builds, against its mock server.
just demo replays the session on your machine and shows more: an edited artifact, the refusal to overwrite it, a flaky server and one that requires credentials.
The full demo: run it.
Get started is the same four commands, copy-pasteable.
What do you want to do?¶
- First transfer in Rust The facade, one transfer, the local mock.
cargo add nexus-raw-core - First transfer in Node The same API as promises, a diff before any write.
pnpm add @nexus-raw/nxr - First transfer in a terminal The release binary and the one-liners.
nxr up - Publish a version The claim lands first, bytes and markers follow.
nxr up --claim-first - Fetch artifacts Named files come down verified, an interrupted pull resumes.
nxr down - See it run The full session against the mock, then on your machine.
just demo - Use it in CI Exit codes, NDJSON events, credentials from the environment.
nxr --json - When it breaks Decode the error, recover, rerun safely.
nxr doctor
More: every flag of every command, the four primitives included · the wire protocol · the Rust API · why it is shaped this way.