mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
Miranda Limonczenko
7ce4ee53ae
Closes [DOCS-1289](https://linear.app/supabase/issue/DOCS-1289/get-the-linter-to-fix-what-it-flags-or-retirereplace-the-linter) Stacked on #50600, which points contributors at the authoring skills. Merge that one first. ## Problem Contributors experienced friction with the linter. They felt nickle and dimed for tiny nits and felt detracted from the work itself. PRs would become noisy with tiny one-word suggestions. Additionally, our homegrown linter is not very intelligent, causing frequent overrides. ## Solution This removes the linter entirely in favor of directing contributors to use SKILLS instead. The removal entails... - **CI.** Delete the three `docs_lint` workflows: the PR check, the external-PR comment companion, and the nightly `--fix` bot. Drop the stale `zizmor.yml` ignore entry for the deleted workflow. - **Tooling.** Delete `supa-mdx-lint.config.toml` and the 14 rule files. Drop the `lint:mdx` script and the `@supabase/supa-mdx-lint` dependency from docs, learn, and ui-library, and regenerate the lockfile. - **Content.** Remove the 181 directives. A separate commit carries Prettier's reformatting of the tables and blank lines those comments had suppressed, so the deletion commit stays readable. No prose changes. - **Style guide.** The word list states each rule directly instead of describing what the linter flagged. Every term survives, including the phrase groups that mirrored `Rule004ExcludeWords`. - **Skills.** `write-the-docs`, `edit-the-docs`, and `review-the-docs` drop `pnpm lint:mdx` from their self-review commands and check the word list directly. `ask-the-docs`'s CI reference drops both workflows. ## Manual testing 1. Run `git grep -i supa-mdx-lint -- . ':!pnpm-lock.yaml'`. No matches. 2. Run `pnpm install --frozen-lockfile --lockfile-only`. It passes, so the lockfile matches the three trimmed manifests. 3. Run `git diff master...HEAD --name-only --diff-filter=ACMR | grep -E '\.(md|mdx)$' | xargs npx prettier --config prettier.config.mjs --check`. All changed markdown passes. 4. Open the [reformatted filter table](https://docs-git-docs-retire-mdx-linter-supabase.vercel.app/docs/guides/observability/logs#filter-events) on the preview and compare it with [production](https://supabase.com/docs/guides/observability/logs#filter-events). The table renders the same. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Documentation guidance now uses manual prose and terminology review with the shared word list. * Clarified storage configuration and common Realtime channel mistakes. * Improved table formatting, text wrapping, and selected reference links. * Updated documentation authoring and review guidance. * **Chores** * Retired automated MDX linting from workflows and local validation commands. * Removed lint-suppression markers throughout documentation without changing instructions. * Added targeted documentation review guidance for pull requests. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
107 lines
5.8 KiB
Plaintext
107 lines
5.8 KiB
Plaintext
---
|
|
id: 'manage-usage-read-replicas'
|
|
title: 'Manage Read Replica usage'
|
|
---
|
|
|
|
## What you are charged for
|
|
|
|
Each [Read Replica](/docs/guides/platform/read-replicas) is a dedicated database. You are charged for its resources, which are the following, and mirrored from the primary database:
|
|
|
|
- [Compute](/docs/guides/platform/compute-and-disk#compute)
|
|
- [Disk Size](/docs/guides/platform/database-size#disk-size)
|
|
- Provisioned [Disk IOPS](/docs/guides/platform/compute-and-disk#provisioned-disk-throughput-and-iops)
|
|
- Provisioned [Disk Throughput](/docs/guides/platform/compute-and-disk#provisioned-disk-throughput-and-iops)
|
|
- [IPv4](/docs/guides/platform/ipv4-address).
|
|
|
|
<Admonition type="note">
|
|
|
|
Read Replicas are **not** covered by the [Spend Cap](/docs/guides/platform/cost-control#spend-cap).
|
|
|
|
</Admonition>
|
|
|
|
## How we calculate charges
|
|
|
|
Read Replica charges are the total of the charges listed below.
|
|
|
|
### Compute
|
|
|
|
Compute is charged by the hour, meaning you are charged for the exact number of hours that a Read Replica is running and, therefore, incurring Compute usage. If a Read Replica runs for part of an hour, you are still charged for the full hour.
|
|
|
|
Read Replicas run on the same Compute size as the primary database.
|
|
|
|
### Disk size
|
|
|
|
Read [the Manage Disk Size usage guide](/docs/guides/platform/manage-your-usage/disk-size) for details on how we calculate charges. The disk size of a Read Replica is 1.25x the size of the primary disk to account for WAL archives. With a Read Replica you go beyond your subscription plan's quota for Disk Size.
|
|
|
|
### Provisioned Disk IOPS (optional)
|
|
|
|
Read Replicas inherit any additional provisioned Disk IOPS from the primary database. Read the [Manage Disk IOPS usage guide](/docs/guides/platform/manage-your-usage/disk-iops) for details on how we calculate charges.
|
|
|
|
### Provisioned Disk Throughput (optional)
|
|
|
|
Read Replicas inherit any additional provisioned Disk Throughput from the primary database. Read the [Manage Disk Throughput usage guide](/docs/guides/platform/manage-your-usage/disk-throughput) for details on how we calculate charges.
|
|
|
|
### IPv4 (optional)
|
|
|
|
If the primary database has configured an IPv4 address add-on, its Read Replicas are also assigned one, with charges for each. Read the [Manage IPv4 usage guide](/docs/guides/platform/manage-your-usage/ipv4) for details on how we calculate charges.
|
|
|
|
### Usage on your invoice
|
|
|
|
Compute incurred by Read Replicas is shown as "Replica Compute Hours" on your invoice. Disk Size, Disk IOPS, Disk Throughput and IPv4 are not shown separately for Read Replicas and are rolled up into the project.
|
|
|
|
## Billing examples
|
|
|
|
### No additional resources configured
|
|
|
|
The project has one Read Replica, no IPv4, and no additional Disk IOPS and Disk Throughput configured.
|
|
|
|
| Line Item | Units | Costs |
|
|
| ----------------------------- | --------- | --------------------------- |
|
|
| Pro Plan | 1 | <Price price="25" /> |
|
|
| | | |
|
|
| Compute Hours Small Project 1 | 730 hours | <Price price="15" /> |
|
|
| Disk Size Project 1 | 8 GB | <Price price="0" /> |
|
|
| | | |
|
|
| Compute Hours Small Replica | 730 hours | <Price price="15" /> |
|
|
| Disk Size Replica | 10 GB | <Price price="1.25" /> |
|
|
| | | |
|
|
| **Subtotal** | | **<Price price="56.25" />** |
|
|
| Compute Credits | | -<Price price="10" /> |
|
|
| **Total** | | **<Price price="46.25" />** |
|
|
|
|
### Additional resources configured
|
|
|
|
The project has two Read Replicas, IPv4, and additional Disk IOPS and Disk Throughput configured.
|
|
|
|
| Line Item | Units | Costs |
|
|
| ----------------------------- | --------- | ---------------------------- |
|
|
| Pro Plan | 1 | <Price price="25" /> |
|
|
| | | |
|
|
| Compute Hours Large Project 1 | 730 hours | <Price price="111" /> |
|
|
| Disk Size Project 1 | 8 GB | <Price price="0" /> |
|
|
| Disk IOPS Project 1 | 3600 | <Price price="14.40" /> |
|
|
| Disk Throughput Project 1 | 200 MB/s | <Price price="7.12" /> |
|
|
| IPv4 Hours Project 1 | 730 hours | <Price price="4" /> |
|
|
| | | |
|
|
| Compute Hours Large Replica 1 | 730 hours | <Price price="111" /> |
|
|
| Disk Size Replica 1 | 10 GB | <Price price="1.25" /> |
|
|
| Disk IOPS Replica 1 | 3600 | <Price price="14.40" /> |
|
|
| Disk Throughput Replica 1 | 200 MB/s | <Price price="7.12" /> |
|
|
| IPv4 Hours Replica 1 | 730 hours | <Price price="4" /> |
|
|
| | | |
|
|
| Compute Hours Large Replica 2 | 730 hours | <Price price="111" /> |
|
|
| Disk Size Replica 2 | 10 GB | <Price price="1.25" /> |
|
|
| Disk IOPS Replica 2 | 3600 | <Price price="14.40" /> |
|
|
| Disk Throughput Replica 2 | 200 MB/s | <Price price="7.12" /> |
|
|
| IPv4 Hours Replica 2 | 730 hours | <Price price="4" /> |
|
|
| | | |
|
|
| **Subtotal** | | **<Price price="437.06" />** |
|
|
| Compute Credits | | -<Price price="10" /> |
|
|
| **Total** | | **<Price price="427.06" />** |
|
|
|
|
## FAQ
|
|
|
|
### Do Compute Credits apply to Read Replica Compute?
|
|
|
|
No, Compute Credits do not apply to Read Replica Compute.
|