These files are examples for ordinary static-site maintenance. Read and adapt them before use. The HTTP helper follows redirects, which can contact hosts other than the initial URL; the TLS helper connects to the supplied host on port 443. DNS, proxy, and trust-store behavior also depends on your local environment.
| Resource | Format | Purpose |
|---|---|---|
| Static-site release checklist | Markdown | Pre-publish checks for a generated artifact. |
| Caddy static-site headers | Caddy snippet | Example headers for a no-JavaScript static site. |
| HTTP header check | POSIX shell | Fetch a URL, follow redirects, discard the body, and print status and response headers. |
| TLS expiry check | POSIX shell | Inspect the presented leaf certificate and check its remaining lifetime. |
| Offline field notes | Markdown, English | A generated snapshot of the English Notes section; it excludes posts, tutorials, essays, and decisions. |
| Resource checksums | Text | SHA-256 values for all five files above. |
The shell helpers require curl, openssl, a POSIX shell, and common Unix utilities including mktemp. Download and inspect the scripts, then invoke them with sh and a local filename. Both validate argument counts; curl reports transfer errors, and an unreadable certificate makes OpenSSL fail. A successful exit does not establish that a service is healthy:
- The HTTP helper does not fail solely because a server returns
4xxor5xx; inspectHTTP_STATUS,FINAL_URL, and the headers. - The TLS helper checks certificate expiry. It does not establish a trusted certificate chain or verify that the certificate matches the hostname; those need separate checks.
- The offline bundle is a snapshot. Use the online notes and their sources for later corrections, and check the download checksum before relying on a saved copy.
Review paths, host names, headers, and failure handling before using any example in a different environment.