Skip to content

docs: sanitize deployment references and refresh the project status - #35

Merged
gnacho merged 1 commit into
mainfrom
docs/34-sanitize-and-refresh-status
Oct 18, 2026
Merged

gnacho merged 1 commit into
mainfrom
docs/34-sanitize-and-refresh-status

Conversation

@gnacho

@gnacho gnacho commented Oct 18, 2026

Copy link
Copy Markdown
Owner

Closes #34.

Sanitize. deploy/README.md no longer names the real host, SSH port, container id or public hostname: they are <ctid> and <your-host> now. The fail2ban warning stays, phrased generically (it is a real trap: unauthenticated probes against a proxy can get you banned). Same for the CT 4125 comment in internal/store/store_test.go and the references in PLAN.md.

Refresh. PLAN.md said phases 0-3 were done, listed #21 (production migration) as pending and kept "publish the repo or not" as an open decision; #23/#24 were also still listed although they closed in PR #30. Now: phases 0-4 done (including the swap), phase 5 in progress (#22), repo public as of 18-Oct-2026. The READMEs claimed 37 Go tests; there are 40.

Verified: grep -rn for the hostname, the SSH port and the container id over the tree comes back empty; gofmt/go vet/go test ./... green (40 Go tests) and npm test green (10 tests).

@gnacho
gnacho merged commit 7df56f5 into main Oct 18, 2026
4 checks passed
@gnacho
gnacho deleted the docs/34-sanitize-and-refresh-status branch October 18, 2026 07:11
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.

Sanitize deployment references and refresh the project status before going public

1 participant