non7top / non7top/nginx-modules
Decide: keep or retire per-file GitHub Releases once the apt-cosign repo is live
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 4h 21m
- Merged PRs (30d)
- 1
Description
Once #1 (a real apt-cosign-verified apt tree) is working and wr-salt-new's `ispconfig3/vts.sls` switches to installing via it, decide what happens to the current per-file GitHub Releases mechanism (`nginx-module-vts--` releases, each `.deb` + `.cosign.bundle`):
- Retire it - one mechanism to maintain, apt tree becomes the only distribution path.
- Keep it - as a manual-download/audit path independent of the apt tree, or for direct `cosign verify-blob` verification without needing apt-cosign installed.
Blocked on #1 landing first.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #1 and wr-salt-new/ispconfig3/vts.sls, then inspect the current nginx-module-vts-- GitHub Releases and their .deb and .cosign.bundle artifacts. After the apt-cosign-verified apt tree is working, decide whether the per-file release mechanism is kept or retired. Done means the choice and its rationale are recorded for the distribution path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100