Skip to content

Remove reference to Tigris data transfer being free #1990

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 7, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion about/pricing.html.markerb
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,6 @@ The following types of traffic are free:
* All inbound data transfer
* Data transfer between apps or Machines in the same region (for organizations using granular data transfer rates)
* Data transfer from apps without an assigned IP address (for organizations not using granular data transfer rates)
* Data transfer to Tigris Object Storage

Fly.io pricing is per region group for outbound data transfer. You'll see a more detailed breakdown of cost per region and per traffic type on your monthly invoice.

Expand Down
4 changes: 2 additions & 2 deletions launch/autoscale-by-metric.html.markerb
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ fly secrets set -a my-autoscaler --stage FAS_API_TOKEN="FlyV1 ..."
The next auth token you'll need is one that has permissions to read from your organization's Prometheus data on Fly:

```cmd
fly tokens create readonly -o my-org
fly tokens create readonly my-org
```

Copy the token and use it as a secret on your autoscaler app:
Expand Down Expand Up @@ -126,7 +126,7 @@ You can scale multiple independent applications with the same autoscaler by usin
To enable multi-app scaling, you will need to use an organization-wide auth token rather than an app-specific deploy token:

```cmd
fly tokens create org -o my-org
fly tokens create org my-org
```

and then set the resulting token on your autoscaler application:
Expand Down