[M8.3a] Finish the verified installer (#171)

Open
  • Is something wrong?
#239 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, github
Domain
devops, infrastructure

Research direction

Read deploy/README.md and review draft PR #171, which installs the verified agent and Caddy from a signed repository. The Caddy path needs validation on a real system, and the work is blocked by the test VM issue and domain ownership. Done when an organization administrator can enroll a real server with the copied command and Caddy runs with --resume.

Written by the indexing model from the issue text.

Description

blocked priority:P1 security-review task track:cross-cutting
Task id

M8.3a

Track

X: cross-cutting

Scope
  • Draft PR #171 installs the verified agent and Caddy from its signed repository. Its Caddy path has never run on a real system. Follow the acceptance in deploy/README.md, then merge.
  • get.shipkeep.dev stays out of the documentation until the domain is owned.
Acceptance criteria

An organization administrator enrolls a real server with the copied command; Caddy runs with --resume.

Blocked by

The test VM issue, then the domain.

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

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 shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.