chore: scrub sensitive data and rewrite docs for public launch - #4
Merged
Conversation
The repo went public so I cleaned out anything tied to my actual infrastructure and rewrote the README in my own voice instead of the dense template I had before. - rota.example.yaml: replace shonpt / 30571705 / kushtaka.ai / "Kushtakas Public Site" with example.com, your-namecheap-username, 12345678, "My Public Site". Same domain in the config-parse test fixture. The placeholder IP 1.2.3.4 stays. - registrar.rs tests: example.com / sld="example" / tld="com" instead of kushtaka.ai. Same fixture in the getHosts XML body. - xml.rs test: CertificateID="12345678" instead of the real one. - dsm.rs: drop the aur0 reference in the module doc + the stage() doc comment. Rephrase to describe on-host integration testing generically. - backend.rs: example FQDN in DcvChallenge doc is now example.com. Style: - Strip every em-dash (U+2014) and en-dash (U+2013) from doc and code comments. Replace with periods, commas, semicolons, or colons depending on context. - README rewritten in first person. Drops the "where the reasoning frays" manifesto framing and the load-bearing-jargon phrases in favor of a direct "this is why I'm building it, here's what it does" shape. - Cargo.toml description loses its em-dash too. Verification: cargo fmt --check clean, clippy -D warnings clean, 18 tests pass. No remaining em/en dashes anywhere except the intentional ASCII --- horizontal rules in the workspace. Git history of these strings on main is purged in a follow-up filter-repo + force-push step.
albedosehen
added a commit
that referenced
this pull request
May 7, 2026
The repo went public so I cleaned out anything tied to my actual infrastructure and rewrote the README in my own voice instead of the dense template I had before. - rota.example.yaml: replace your-namecheap-username / 12345678 / example.com / "My Public Site" with example.com, your-namecheap-username, 12345678, "My Public Site". Same domain in the config-parse test fixture. The placeholder IP 1.2.3.4 stays. - registrar.rs tests: example.com / sld="example" / tld="com" instead of example.com. Same fixture in the getHosts XML body. - xml.rs test: CertificateID="12345678" instead of the real one. - dsm.rs: drop the the host reference in the module doc + the stage() doc comment. Rephrase to describe on-host integration testing generically. - backend.rs: example FQDN in DcvChallenge doc is now example.com. Style: - Strip every em-dash (U+2014) and en-dash (U+2013) from doc and code comments. Replace with periods, commas, semicolons, or colons depending on context. - README rewritten in first person. Drops the "where the reasoning frays" manifesto framing and the load-bearing-jargon phrases in favor of a direct "this is why I'm building it, here's what it does" shape. - Cargo.toml description loses its em-dash too. Verification: cargo fmt --check clean, clippy -D warnings clean, 18 tests pass. No remaining em/en dashes anywhere except the intentional ASCII --- horizontal rules in the workspace. Git history of these strings on main is purged in a follow-up filter-repo + force-push step.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repo just went public. This cleans out any reference to my actual infrastructure and rewrites the README in my own voice instead of the manifesto template I had before.
Sensitive data scrub
rota.example.yaml: replacesyour-namecheap-username/12345678/example.com/My Public Sitewithyour-namecheap-username,12345678,example.com,My Public Site. Placeholder IP1.2.3.4stays.registrar.rstests:example.com/sld="example"/tld="com"everywhere. Same fixture in the getHosts XML body.xml.rstest:CertificateID="12345678"instead of the real one.dsm.rs: drops thethe hostreference in the module doc and thestage()doc. Rephrased generically.backend.rs: example FQDN inDcvChallengedoc is nowexample.com.rota-core::configupdated accordingly.Style
Cargo.tomldescription loses its em-dash too.Verification
cargo fmt --all -- --checkcleancargo clippy --workspace --all-targets -- -D warningscleancargo test --workspace: 18 tests pass---horizontal rules in the workspace.What's not in this PR
Git history is still dirty. The next step (after this merges) is a
git filter-repo --replace-textpass plus a force-push ofmainso the old commits no longer exposeyour-namecheap-username/12345678/example.com. SHAs will change.