The original idea of ZipZen is to make developers' lives easier when they have to release binaries.
GitHub/GitLab Releases exist, but none of them are more than a “container” for release artifacts. Artifactory and Nexus are bloated and require more setup/money than most of us want to deal with, if not mandatory.
As we truly wanted to give developers something that lifts off weight from them, this week our focus was on repository support. But a bit differently than what you may expect: no configuration required to set up an APT, YUM, or Helm repository.
So, the results of this week:
- Some CLI improvements
- Reworked, clearer documentation
- Zero-configuration APT, YUM, and Helm repository support
Obviously, I'm proud of the repository support. Developers only have to upload a .dev, .rpm, or .tgz/tar.gz package, and everything is sorted out automatically. If a GPG key is set, the apt repository and .rpm packages will be signed as well.
Next up, we'll mostly work on public release pages and getting more feedback on the platform. Also, we'll work on adding CI/CD integration examples as well, so it is going to be a no-brainer to use ZipZen with GitHub/GitLab.
