Docs
Grant, publish, pull, keep tidy
In-app Help is the operator source of truth after install. This page is the first loop so you know the shape before you open the UI.
Start here
Four steps on a new host
- 01
Grant access
Create a group, add grants for the software and channel, then create a repository user. Pull and publish are separate permissions.
- 02
Publish from CI
Upload a deb, Arch package, MSI, or nupkg onto a channel. The catalogue records the artifact. Promote when the lane is ready.
- 03
Clients pull
Copy APT, Arch, NuGet, or MSI snippets from the user. Indices are GPG-signed. Clients only see what the grants allow.
- 04
Keep it tidy
Leave the default retention policy until you understand pin, purge delay, and channel-specific bindings.
Topics
What the in-app Help covers
Grant access
Groups, grants, and users. Pull, publish, and creating new packages. Copy-paste client snippets from the user detail panel.
Packages and artifacts
A package is a software name. An artifact is a versioned blob with format, distribution, architecture, and channel publication.
Channels
Fixed lane: alpha, beta, testing, canary, release. Promote and unpublish from the UI. Upload always names a channel.
Client setup
APT sources and auth.conf, Arch pacman, NuGet V3, MSI latest. Full Help lives in the operator UI after install.
Retention
Default policy keeps 30 unpinned versions with a purge delay. Pin protects a build. More specific bindings win.
Home, audit, errors
Dashboard counts and channel charts. Audit for uploads and downloads. Client error reports on the artifact (fed by ArtifactD.ClientErrorReporting).
Client error SDK
Add ArtifactD.ClientErrorReporting from the Artifactd NuGet feed. Point it at the dataplane with a pull token, attach unhandled handlers, and call ReportError only for curated failures. Reports attach to the matching released artifact.