fulmine: add the production-stack entry - #1100
Merged
Merged
Conversation
nigrosimone
marked this pull request as ready for review
August 11, 2026 09:47
nigrosimone
requested review from
Kaliumhexacyanoferrat and
MDA2AV
as code owners
August 11, 2026 09:47
Contributor
Author
|
/benchmark -f fulmine --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
Contributor
Author
|
The I had the split backwards. The nginx entry gives its proxy 30 logical CPUs and its server 24; I had given the edge 16 and the server 38, on a profile where the edge terminates TLS and h2 for every request and serves I also suspected the Happy to sweep /benchmark -f fulmine -t production-stack --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
Contributor
Author
|
It's good for me |
MDA2AV
approved these changes
Aug 11, 2026
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
2 participants
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.
Subscribes the fulmine entry to
production-stack. Four services as the rules ask: a stock Caddy edge, Redis, the shared authsvc built as-is, and the server.The edge terminates TLS and h2, serves
/static/*off disk, sends/public/*straight through, and puts/api/*behindforward_authagainst the authsvc, copyingX-User-Idon. Nothing in the server looks at a token.On the server side most of it was already there for
crud: the cache-aside read is now registered under both/crud/items/:idand/api/items/:id, and the JSON route under/public/json/:count. New are/public/baseline, thePOST /api/items/{id}that answers 204 and invalidates, and/api/me, which reads the user byX-User-Idwith a 30 second TTL.I ran the stack locally against the repo certs and seed, and walked the validation checks by hand: h2 negotiates,
/staticcomes from the edge,/public/baselinegives 55,/public/json/25has 25 items with the full schema and correct totals,/api/*is 401 without a token and with a bogus one on both GET and POST,/api/items/1returns id 1, cache-aside reads MISS then HIT, POST answers 204 and the next read is MISS again, and/api/mereturns user 42./benchmark -f fulmine -t production-stack --save