ProofedMesh/services/signing-service/.dockerignore at 3a01cc651fed1cf0ce9dc35fe6ea489f7bb43f374e6508528a8f5691a2e496cf - basicstack/ProofedMesh - Forgejo: Beyond coding. We Forge.

basicstack/ProofedMesh

SHA256

CTO b52936ce9d

validate / JSON Schema (ajv) (push) Successful in 20s

Details

validate / Rego (opa fmt + opa test) (push) Successful in 14s

Details

validate / Go (vet + test) (push) Successful in 21s

Details

build-images / signing-service image (push) Failing after 13s

Details

signing-service: Dockerfile, K8s manifests (agent-trust), image CI, secret convention

- Dockerfile: multi-stage (golang:1.23-alpine3.21 → distroless/static:nonroot),
  CGO off, trimpath, stripped, UID/GID 65532, read-only rootfs friendly.
- deploy/signing-service/: ServiceAccount, Deployment (2 replicas, probes,
  tight SecurityContext), ClusterIP Service on :8081, NetworkPolicy
  (ingress from agent-trust, DNS egress), example Secret, and README with
  the full dev + prod secret convention.
- .forgejo/workflows/build-images.yml: builds image on push + PR,
  pushes :<git-sha> + :main to harbor.basicstack.de on main pushes only.
  Clone pattern matches validate.yml (sha256 repo, manual git clone).
- README updates: service README gains Deployment section; repo README
  layout now mentions services/signing-service, services/transparency-log,
  deploy/, and the new workflow.

Scope matches DEV-605. OpenBao, OPA and Pocket-ID JWKS stay stubs and move
in their own follow-up subtasks; the prod secret shape is documented so
those subtasks can plug in without reshaping the Deployment.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-10-25 18:19:51 +00:00

4 lines

48 B

Text

Raw Blame History

 **/*_test.go.bak
 **/.DS_Store
 **/*.swp
 **/*.swo