Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
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.
Description
Adds veil as an infrastructure entry: veil is a reverse proxy / web
server written in Rust on its own async runtime (no tokio). The entry uses veil's published container image
(
ghcr.io/aofusa/veil:musl-v0.10.1, thefull-containerbuild: epoll readiness reactor) and adds a configurationfile and a Proxy-Wasm module. I maintain veil.
How the endpoints are answered (nothing is proxied to an upstream application):
/baseline11(GET, and POST with Content-Length or chunked),/baseline2,/pipeline,/json/{count}?m=areanswered by a Proxy-Wasm module (
filter/, Rust, compiled towasm32-wasip1in the Dockerfile) loaded into veil,on a
type = "Respond"route. The POST body is read in the request-body phase. The dataset is read by veil at startup(
data_files) and parsed once per module instance; the JSON response is serialized on every request./static/*is veil's File backend with its open-file and content caches (watch = true: inotify, so replacedfiles are served immediately) and
[route.compression](br/gzip on HTTP/1.1, HTTP/2 and HTTP/3; uncompressed HTTP/1.1responses are sent with sendfile).
[[listener]]s: 8080 HTTP/1.1, 8081 TLS HTTP/1.1 only (no h2 in ALPN), 8082 h2c,8443 TLS h2 + HTTP/3 (quiche). TLS is rustls; worker threads follow the container's CPUs; access log off.
nonroot, seccomp, Landlock limited to/certs,/data,/etc/veil.Subscribed profiles: baseline, pipelined, limited-conn, json-tls, static-tls, baseline-h2, static-h2, baseline-h2c,
json-h2c, baseline-h3, static-h3.
Local validation (
./scripts/validate.sh veil, the publishedghcr.io/aofusa/veil:musl-v0.10.1): 72 passed, 0 failed (frag 9/9, h2/h2c, h3, static-tls compression).🤖 Generated with Claude Code