Make it easy to copy/paste into docs!

including:

• breaking changes
• tests with the new context
• updating the serve command

See https://www.youtube.com/watch?v=wKHJdwYSXjA (17m) for a tutorial

And https://sre.google/sre-book/monitoring-distributed-systems/ to see what kind of graphs are good ideas

https://www.gomponents.com/

As it's passed in via flag via an admin l, it doesn't need to be escaped

Once I confirm that I can use "request.Host" as an origin flag, hardcore that and remove the flag

Add a flag that lets me specify a traceid url as an html template so I can inject that rendered template into submit and click on a link to see the http trace instead of copy-pasting the traceid into the portal manually

This should be easy and allow easier DNS proxying

Code from DNS package to Exchange Context:

// ExchangeContext performs a synchronous UDP query, like Exchange. It
// additionally obeys deadlines from the passed Context.
func ExchangeContext(ctx context.Context, m *Msg, a string) (r *Msg, err error) {
	client := Client{Net: "udp"}
	r, _, err = client.ExchangeContext(ctx, m, a)
	// ignoring rtt to leave the original ExchangeContext API unchanged, but
	// this function will go away
	return r, err
}

Then I can set that to any of the options in https://github.com/miekg/exdns/blob/d851fa434ad51cb84500b3e18b8aa7d3bead2c51/q/q.go#L161

$ go run . serve | format_jsonl.py fmt

---
line: ⇨ http server started on 127.0.0.1:8080
2023/12/30 14:11:39 traces export: Post "http://127.0.0.1:5080/api/default/traces": dial tcp 127.0.0.1:5080: connect: connection refused

That second line comes from the otel libraries logging using the log library. I need to redirect that to the server JSON logs, exactly like https://caddyserver.com/docs/json/logging/sink/ . I could look up how that works or how https://pkg.go.dev/golang.org/x/exp/slog#SetDefault works

embedded directory

right now its:

static/
    3p/
        ...
    templates/
        ...
    index.css
    loading-spinner.svg

What if I did instead:

embedded/
    templates/
        ...
    static/
        3p/
            ...
        index.css
        loading-spinner.svg

Then I could use an embedded FS for serving instead of manually listing paths... Something to think about if the app grows

This makes it more clear for normal digs what's happening

I think this is possible. Dig* functions should act on results as much as possible instead of calling other dog funcs

This breaks the filled form link when using HTTPS... Can probably just use a relative link?

https://github.com/oklog/run

• server hardening middleware
• traces
• metadata- traceid, date, version
• gh login
• playwright tests
• dashboards
  • req count
  • dns query count

The easiest way to trigger this is by trying to render a page with an invalid template. The code panics and I need to make sure the panic ends up in the trace and the user gets a 5xx

The flags have diverged a little bit, especially --subnet.

That way I can keep using --protocol for DNS protocol