Skip to content

Docs/maintainers and tls#147

Merged
amavashev merged 6 commits into
mainfrom
docs/maintainers-and-tls
May 2, 2026
Merged

Docs/maintainers and tls#147
amavashev merged 6 commits into
mainfrom
docs/maintainers-and-tls

Conversation

@amavashev
Copy link
Copy Markdown
Collaborator

Summary

Checklist

  • Tests added/updated for new behavior
  • AUDIT.md updated (if protocol surface changed)
  • README.md updated (if public API changed)
  • Lint and test suite passes locally

Test plan

amavashev added 6 commits May 2, 2026 19:10
Two CII Best Practices quick wins ahead of the badge submission.

1. MAINTAINERS.md (new)
   Lists project lead (Albert Mavashev / @amavashev), contributing
   organizations (Runcycles, K2nio, Singleton Labs, Anthropic), and
   triage / review / release SLAs. Answers the CII "Roles document"
   criterion (Basics) which was previously NEEDS DECISION. Also gives
   external contributors a clear "who do I talk to" entry point and
   shows up on the GitHub repo About sidebar.

2. README "Production deployment & TLS" section (new)
   Documents the recommended deployment topology (TLS-terminating
   reverse proxy → HTTP cycles-server:7878 → password-protected Redis),
   names common proxy choices (nginx / Caddy / Traefik / ALB), and
   explains the rationale for terminating TLS at the ingress layer
   rather than the app. Adds a network-hardening table covering admin
   server isolation and required production env vars
   (REDIS_PASSWORD, ADMIN_API_KEY, WEBHOOK_SECRET_ENCRYPTION_KEY).

   Answers the CII "TLS for in-transit" Security criterion which was
   previously NEEDS DECISION. More importantly: it's a real question
   first-time deployers actually have, and now there's a written
   answer in the README rather than asking on Discord.

Skipped from the original quick-win list:
- CONTRIBUTING.md per-repo: GitHub auto-defaults to the org-wide
  CONTRIBUTING.md at runcycles/.github root. No per-repo file needed —
  visible at /community page already.
- spotbugs-maven-plugin: SpotBugs has a high false-positive rate on
  Spring code and adds an ongoing CI maintenance tax. CodeQL +
  JaCoCo's 95% coverage gate already cover the Quality answer
  defensibly.
@amavashev amavashev merged commit a0bfc05 into main May 2, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant