Show HN: Attune – Build and publish APT repositories in seconds

Re:Show HN: Attune – Build and publish APT repositories in s... by yjftsjthsd-h on Friday April 18, 2025 @01:14PM (#43729972)

It's probably intuitive to anybody who's tried to do this the hard way, but if your target is people without that experience, you might want to dumb it down even more. So this is from your readme:

  attune repo create -u 'http://localhost:9000/debian' -d bookworm
  attune repo pkg -r 1 add -c stable/v17 ~/Downloads/teleport_17.4.4_arm64.deb

And I think I know what `-d bookworm` must be, but I've no clue what -r or -c are doing in the second command.

Also, from your post here (and why are the quick start steps different here?),

  attune repo create --uri https://apt.releases.example.com

What is that URI supposed to be? Is that where the thing will eventually get served from and I have to run this on the server, or synchronize an output directory to the server, or is that going to do some sort of magic upload itself?

[ Parent | on HN ]

Re:Show HN: Attune – Build and publish APT repositories in s... by ilikebits on Friday April 18, 2025 @01:21PM (#43730048)

Totally agree here. The current target is people who are familiar with the process, and we plan to write more documentation as we start thinking more about accessibility to a broader audience. We actually ran into this issue ourselves while building the tool - the Debian documentation is all there, but not the easiest to approach. These docs are one of the rough edges (sorry!) since we wanted to get this out earlier for feedback.

To answer your direct question: on self-hosted repositories, the URI right now is just a string identifier. We are working right now on a cloud hosted service, and there the URI will help us figure out which repository to actually serve.

[ Parent | on HN ]