docs: correct the engine tuning facts, add the recovery catalog row, show in-process HTTPS on std - #71
Merged
Conversation
…and show in-process HTTPS on std (goceleris/celeris#415, #418) engines.md: - CELERIS_ADAPTIVE_START chooses only the start engine; it does not turn off runtime switching (chooseStartEngine is its only reader). Point to Config.Engine for a single engine with no switching. - The High tier does not turn on multishot recv, provided buffer rings or fixed files: multishot recv with a provided buffer ring is opt-in (CELERIS_IOURING_MULTISHOT_RECV=1) and fixed files are development-only (celeris#541). The feature matrix says the same. - A table of the tuning environment variables, each as the code at celeris 5b2e83b reads it. middleware.md: recovery was named only in prose; it now has a catalog row under a new Error handling category. deployment.md: in-process HTTPS works today on the std engine with StartWithListener(tls.NewListener(...)) (HTTP/1.1; checked at celeris 5b2e83b: 200, scheme https, IsTLS true). Show it alongside the loopback terminator, and link celeris#446.
This was referenced Sep 19, 2026
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
goceleris-docs | 1ed8185 | Commit Preview URL Branch Preview URL |
Sep 19 2026, 06:39 AM |
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 docs-site half of goceleris/celeris#415 and #418. The celeris README half is goceleris/celeris#677.
Refs goceleris/celeris#415, goceleris/celeris#418
CELERIS_ADAPTIVE_STARTonly chooses the start engine. The page said it "disables runtime switching", butchooseStartEngineis the variable's only reader (celeris 5b2e83b), so the controller can still switch. The page now points toConfig.Enginefor a single engine with no switching.Hightier row and the feature matrix claimed multishot recv, provided buffer rings and fixed files. Multishot recv with a provided buffer ring is opt-in: the ring is created only underCELERIS_IOURING_MULTISHOT_RECV=1. Fixed files are development-only (celeris#541).CELERIS_MAX_IOURING_TIERtreats a typo asnone, which disables the io_uring engine. ThePBUF_COUNTdefault is effectively 1024.recoverywas named only in prose. It now has a catalog row under a new Error handling category, linking the Error handling page.StartWithListener(tls.NewListener(...)), next to the loopback terminator. I checked it at celeris 5b2e83b with the std engine: status 200, HTTP/1.1,c.Scheme() == "https",c.IsTLS() == true.Left for after the celeris#657 fix lands: the Adaptive section says a busy connection "is never stranded on the slower engine". celeris#657 shows async and idle connections can be, and its fix is in progress.