Signed apt and dnf/yum repositories on GitHub Pages

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
linux
Domain
devops, release

Research direction

The payload names no source files, so start from how release artifacts are produced today and where GETTING-STARTED lives. The work needs a GPG signing key stored as a repo secret, generated apt Packages/Release and rpm repodata published to GitHub Pages under /apt and /rpm, and setup lines in GETTING-STARTED. It is done when apt install sys1 and dnf install sys1 both install and update from those URLs. Signing and repo layout are design decisions, so confirm them with the maintainers first.

Written by the indexing model from the issue text.

Description

distribution roadmap

So people can apt install sys1 / dnf install sys1 and get updates.

  • GPG signing key (repo secret)
  • generate Packages/Release (apt) and repodata (rpm) from release artifacts
  • publish under https://a-hackers-guide.github.io/sys1/apt and /rpm
  • document setup lines in GETTING-STARTED
Dominant language
Go
Stars
1
Forks
0
Avg merge
12m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from A-Hackers-Guide/sys1

All issues in A-Hackers-Guide/sys1

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.