Remove the bom (Mumbai) region - #2508
Merged
Merged
Conversation
Lillian asked for bom to come out of the docs. Customers running there have already been told, so these are deletions rather than deprecation notices. Five edits. The regions table row, the pricing selector entry, the region code list on the Machine placement page, and the high-demand example on the same page. The load balancing example needed rework rather than trimming. It deployed 10 Machines across ams, bom, sea and sin, and the walkthrough depends on three of them being in ams and ten in total, not on which the other three regions are. Also sea is not in the regions table and has not been for some time, so both it and bom are replaced with nrt and sjc. The counts and every figure in the walkthrough are unchanged. Left alone: app-guides/minio.mdx names bom and maa inside quoted fly launch output. Editing that would misreport what the tool prints.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully 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
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.
Lillian asked for
bomto come out of the docs. Customers running there have already been told, so these are deletions rather than deprecation notices. Closes superfly/docs-tracking#316.Four files, five edits:
reference/regions.mdx, the table rowsnippets/RegionPricingSelector.jsx, the pricing selector entrymachines/guides-examples/machine-placement.mdx, the list of region codes and the "regions in high demand" examplereference/load-balancing.mdx, which needed rework rather than trimmingOn the load balancing example. It deployed 10 Machines across
ams,bom,seaandsin, and every figure in the walkthrough depends on three Machines being inamsand ten in total, not on which the other three regions are. 60 is three at the soft limit, 200 is ten at the soft limit, 250 is ten at the hard limit.So
bomandseaare replaced withnrtandsjc, the counts are untouched, and no number in the walkthrough changes.seawent because it is not in the regions table and has not been for some time, so the example was already naming a region that does not exist.Left alone on purpose.
app-guides/minio.mdxnamesbomandmaainside a quotedfly launchoutput block. Editing it would misreport what the tool prints, the same reasoning applied to the flyctl URLs in #2502 and the--volume-sizedescription in #2488.maaappearing there is itself evidence that the block is old output.Verified. The docs regions table, the docs pricing selector and
FlyioPriceCalc.Regionsinsuperfly/ui-exnow list an identical 17 regions. Before this they disagreed onbom, whichfly.io/pricinghad already dropped, so the two pricing pages were showing different regions.One thing I did not fix, and it predates this. The load balancing walkthrough jumps from "61+ concurrent requests, the proxy does not route to other regions on soft limits alone" straight to "200+, all Machines are at their soft limit". It never says what happens at 75, where the three
amsMachines hit their hard limit and traffic must start reaching the other seven. Worth a separate look by someone who can confirm the proxy behavior.