Package Registry

Start by creating a project in your dashboard, then use our CLI to upload your package files. Once uploaded, you can publish the release to make it publicly available. Check out our documentation for detailed setup instructions.

ZipZen supports APT (Debian/Ubuntu), YUM/RPM (Red Hat/CentOS), and Helm repositories. You can upload .deb, .rpm, and Helm chart files, and we'll automatically generate the repository metadata for you.

GPG signing is automatically handled by ZipZen if you set a GPG key for your project. We'll sign your packages with our secure keys, or you can provide your own GPG key for signing.

Not yet. However, we're working on a feature to allow you to make your packages private.

Once published, users can add your repository to their system and install packages using standard package managers. We provide simple one-line setup commands for APT, YUM, and Helm repositories. If you uploaded binaries, your users can download them directly from the release page.

A project is like a container for your package - it has a name, description, and settings. A release is a specific version of your package (like v1.0.0) that contains the actual files users will download and install.

To update a package, create a new release with a new version number. Users can then upgrade using their package manager. You can also yank (remove) releases if needed, though this should be done carefully.