mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 01:45:10 +03:00
Nik RichersandNik Richers
6418820b0b
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? This PR converts link sections in the self-hosting overview page to the `ContentListings` component, puts conceptual guidance before deployment options, and adds badge support for the Docker card (minor). Relates to DOCS-1137 ## Current behavior `self-hosting.mdx` uses hand-authored `<GlassPanel>` / `<Link>` JSX for two sections: - **Get started**: Docker card with a JSX title containing a `<Badge>` element (was previously deferred for this reason). - **Community-driven projects**: Two cards with trivial `<span>`-wrapped string titles. Get started and Community cards appear at the top of the page, before the conceptual overview. The Support and community section uses hand-authored bullet lists for GitHub, Discord, and Reddit links. ## New behavior - The self-hosting overview page now uses data-driven `ContentListings` instead of hand-written cards and bullet lists. - Conceptual content (how self-hosting differs, your responsibilities, telemetry) comes first; deployment options and community resources follow. - Section intro text lives in listing data rather than inline MDX. - Brand icons added to all listing cards (Docker, Kubernetes, Traefik, GitHub, Discord, Reddit). - Minor: Added support for badges to content listings, such as "Official" in the Docker tile Data lives in `self-hosting.data.ts` (5 groups, 8 links) and is registered in `content-listings/index.ts`. ## Additional context ### Icon usage rights New brand icons (Kubernetes, Traefik, Reddit) are sourced from [Simple Icons](https://simpleicons.org) (CC0 1.0). Existing icons (Docker, GitHub, Discord) reuse assets already in `apps/docs/public/img/icons/`. Use is non-commercial documentation only — consistent with existing docs icon usage and trademark fair-use for identifying linked third-party services. ### To do: - [ ] Check with @aantti if he's on board with switching the page to content listings we can lint for and the content restructure to match other overview pages ## Verification | Gate | Result | |------|--------| | `pnpm vitest run lib/content-listings.test.ts` | ✅ 12/12 passed | | `pnpm build:guides-markdown` | ✅ 744 files generated | | `pnpm lint:mdx` (self-hosting.mdx) | ✅ No warnings on changed file | ### Proof: restructured self-hosting page with ContentListings and icons | [Before (production)](https://supabase.com/docs/guides/self-hosting) | [After (PR preview)](https://docs-git-nikrichers-docs-1137-self-hosting-supabase.vercel.app/docs/guides/self-hosting) | |---|---| |  |  | <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Updated the self-hosting guide to use dynamic content listings for “Get started,” community resources, support options, and sharing experiences. * Added richer listing cards with optional badges and improved icon handling. * Expanded self-hosting resource groups to surface more relevant links in docs navigation. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Nik Richers <nik@validmind.ai>
54 lines
2.4 KiB
Plaintext
54 lines
2.4 KiB
Plaintext
---
|
|
title: 'Self-Hosting'
|
|
description: 'Host Supabase on your own infrastructure.'
|
|
subtitle: 'Install and run your own Supabase on your computer, server, or cloud infrastructure.'
|
|
hideToc: true
|
|
---
|
|
|
|
Self-hosting is a good fit if you need full control over your data, have compliance requirements that prevent you from using managed services, or want to run Supabase in an isolated environment.
|
|
|
|
### How self-hosted Supabase differs
|
|
|
|
Self-hosted Supabase is different from:
|
|
|
|
- **Supabase CLI** (local development), which is intended for development and testing only.
|
|
- **Managed Supabase** platform, which is fully hosted and operated by Supabase.
|
|
|
|
Self-hosted Supabase mimics a single project. Studio doesn't support multiple organizations or projects. Platform-only [features](/features) such as branching, advanced metrics beyond logs, managed backups and PITR, analytics and vector buckets, ETL, and the platform management API are **unavailable** in self-hosted configuration. Most settings are configured through [environment variables](https://github.com/supabase/supabase/blob/master/docker/.env.example).
|
|
|
|
### Your responsibilities when self-hosting
|
|
|
|
When you self-host, **you are responsible for**:
|
|
|
|
- Server provisioning and maintenance
|
|
- Security hardening and keeping OS and services updated
|
|
- Service configuration and management
|
|
- Postgres database maintenance
|
|
- High availability and scalability
|
|
- Backups and disaster recovery
|
|
- Monitoring and uptime
|
|
|
|
### Telemetry
|
|
|
|
Self-hosted Supabase (run via Docker Compose) **does not phone home or collect any telemetry**.
|
|
|
|
The **Supabase CLI** is a [separate tool](/docs/guides/local-development/cli/getting-started) and collects usage telemetry to help improve the developer experience. See [CLI telemetry](/docs/guides/local-development/cli/getting-started#telemetry) for opt-out methods.
|
|
|
|
<ContentListings id="self-hosting-get-started" />
|
|
|
|
<ContentListings id="self-hosting-community" />
|
|
|
|
## Support and community
|
|
|
|
Self-hosted Supabase is community-supported.
|
|
|
|
<ContentListings id="self-hosting-resolve-issues" />
|
|
|
|
<ContentListings id="self-hosting-get-help" />
|
|
|
|
<ContentListings id="self-hosting-share-experience" />
|
|
|
|
### Enterprise self-hosting
|
|
|
|
If you're an enterprise using self-hosted Supabase, we'd love to hear from you. Reach out to our [Growth Team](https://forms.supabase.com/enterprise) to discuss your use case, share feedback, or explore design partnership opportunities.
|