dearsky/numa
1
0
Fork 0
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 25 Wiki Activity

feat: self-host fonts, styled block page, wildcard TLS #16

Merged
razvandimescu merged 4 commits from perf/hot-path-optimizations into main 2026-03-27 08:19:54 +08:00
Conversation 0 Commits 4 Files Changed 29 +2064 -182
razvandimescu commented 2026-03-27 08:02:28 +08:00 (Migrated from github.com)
Copy Link

Summary

  • Self-hosted fonts — replace Google Fonts CDN with 5 woff2 files (73KB total), served from API server via include_bytes!. Zero external requests, works offline, consistent with privacy stance
  • Styled block page — when a blocked domain hits the proxy, show a helpful "Blocked by Numa" page with allowlist instructions (was confusing "not a .numa domain" error)
  • Shared error_page() template — deduplicate ~160 lines of CSS between 403 and 404 proxy pages
  • Wildcard TLS — add *.numa SAN to cert so unregistered .numa domains get valid HTTPS (styled 404 without cert warning)
  • Fix Instrument Serif font-weight — use 400 (only available weight) instead of synthetic bold 600/700 across all pages
  • Landing page — performance section, blog link, comparison table updates, OG tags
  • Blog post — "Building a DNS Resolver from Scratch in Rust" with real wire-format captures

Test plan

  • cargo fmt --check clean
  • cargo clippy -- -D warnings clean
  • All tests pass
  • Fonts load at localhost:5380/fonts/fonts.css (200, correct content)
  • woff2 files serve with correct font/woff2 content-type and 1-year cache headers
  • Dashboard renders with self-hosted Instrument Serif / DM Sans / JetBrains Mono
  • Blog renders correctly via pandoc template
  • Blocked domain proxy page shows styled "Blocked by Numa" message
  • No remaining Google Fonts references in site/ or src/

🤖 Generated with Claude Code

## Summary - **Self-hosted fonts** — replace Google Fonts CDN with 5 woff2 files (73KB total), served from API server via `include_bytes!`. Zero external requests, works offline, consistent with privacy stance - **Styled block page** — when a blocked domain hits the proxy, show a helpful "Blocked by Numa" page with allowlist instructions (was confusing "not a .numa domain" error) - **Shared error_page() template** — deduplicate ~160 lines of CSS between 403 and 404 proxy pages - **Wildcard TLS** — add `*.numa` SAN to cert so unregistered `.numa` domains get valid HTTPS (styled 404 without cert warning) - **Fix Instrument Serif font-weight** — use 400 (only available weight) instead of synthetic bold 600/700 across all pages - **Landing page** — performance section, blog link, comparison table updates, OG tags - **Blog post** — "Building a DNS Resolver from Scratch in Rust" with real wire-format captures ## Test plan - [x] `cargo fmt --check` clean - [x] `cargo clippy -- -D warnings` clean - [x] All tests pass - [x] Fonts load at `localhost:5380/fonts/fonts.css` (200, correct content) - [x] woff2 files serve with correct `font/woff2` content-type and 1-year cache headers - [x] Dashboard renders with self-hosted Instrument Serif / DM Sans / JetBrains Mono - [x] Blog renders correctly via pandoc template - [x] Blocked domain proxy page shows styled "Blocked by Numa" message - [x] No remaining Google Fonts references in site/ or src/ 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 dependencies
Pull requests that update a dependency file
 docker
Pull requests that update docker code
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 rust
Pull requests that update rust code
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/numa#16
Delete Branch "perf/hot-path-optimizations"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?