Version Fluid Compute in vercel.json - #189
Merged
Merged
Conversation
Fluid was enabled in the dashboard on 2026-08-08; pinning it here makes it deploy-time config like the syd1 region pin — versioned, applied to every deployment (previews included), and safe against the dashboard toggle ever being flipped back accidentally. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
One-liner: pin
"fluid": trueinremix/vercel.json.Lopu enabled Fluid Compute in the dashboard on 2026-08-08 (it needs a new deployment to take effect). This versions the setting in the repo the same way the
syd1region pin is versioned, so:Context: Fluid gives in-function concurrency (many requests share one warm instance → far fewer Mongo connection pools against M0's ~500-connection cap), scale-to-one (≥1 instance kept warm, largely retiring the cold-start tax PR #161 shrank), and Active CPU billing (CPU billing pauses during Mongo I/O waits — most of Thingtime's request time). Details in docs/architecture/geo-distribution.md §7 (PR #185).
Merging this = the deployment that turns Fluid on for production.
🤖 Generated with Claude Code