Automation
Packages
A package is a versioned file (or set of files) you publish next to your code — installers, tarballs, or container-ish blobs. konnos stores them for you; you upload and download with curl and a personal access token.
What this is (and isn’t)
Today konnos offers a generic package store — think of a labeled shelf for finished files, not a full Docker Hub clone. You can:
- Upload any file with a name + version via HTTPS
- Download it again by the same path
- List and delete versions in Settings → Packages
Container images
A full container registry (Docker / OCI docker push) is not a separate product yet. You can still ship an image as a file package:
# Save a local image as a tar
docker save my-app:1.0.0 -o my-app-1.0.0.tar
# Upload it as a generic package (token = personal access token)
curl -X PUT --data-binary @my-app-1.0.0.tar \
-H "Authorization: token YOUR_TOKEN" \
-H "Content-Type: application/octet-stream" \
https://code.konnos.org/api/packages/{username}/my-app/1.0.0/my-app-1.0.0.tar
# Later: download + load
curl -O https://code.konnos.org/api/packages/{username}/my-app/1.0.0/my-app-1.0.0.tar
docker load -i my-app-1.0.0.tarFor a real registry elsewhere, link it from your repo README.
Publish with curl
- 1
Mint a personal access token
Create a token under Settings → Developer → Tokens (classic). Copy it once — it won't be shown again.
- 2
Upload a file
Replace
{username},{name},{version}, and{filename}with your values:curl -X PUT --data-binary @your-file.tgz \ -H "Authorization: token YOUR_TOKEN" \ -H "Content-Type: application/octet-stream" \ https://code.konnos.org/api/packages/{username}/{name}/{version}/{filename} - 3
Download it again
curl -O https://code.konnos.org/api/packages/{username}/{name}/{version}/{filename}Private packages need the same
Authorization: token …header on download.
Manage in the dashboard
Open Settings → Packages to see what you've published and delete a version when you're done with it. Deleting a version removes its files permanently.