Files
supabase/apps/docs/data/content-listings/local-development.data.ts
T
Wen Bo Xie ffd2754c7a docs(cli): document experimental supabase stack commands and native runtime (#50391)
Add two guides under Local Development for the experimental `supabase
stack` commands, wire them into the docs nav, the CLI reference, the
marketing features list, and the pages that readers reach with a port
conflict.

New pages:
- guides/local-development/parallel-projects: run one local project per
app, git worktree, branch, or named environment on a single machine.
Covers identity, automatic port assignment, removing fixed ports from
config.toml, named projects, finding endpoints, stop and destroy, the
`[experimental] stack` setting, and current limitations.
- guides/local-development/runtimes: the Docker and native runtimes, how
the CLI picks one, native platform requirements, artifact download and
cache locations, and runtime limitations.

Cross-links and context:
- Local development index, CLI getting started, CLI workflows, managing
environments, AI tools, MCP, and the edge functions port troubleshooting
entry now point readers to the new guides where a second `supabase
start` fails on a port conflict.
- CLI reference: `supabase stack`, `stack start`, `stack stop`, `stack
destroy`, the `experimental.stack` config key, and a note on `supabase
start` and `[experimental] stack`.
- www: two feature entries and copy tweaks on the hosted Postgres and
innovation teams solution pages.
- supa-mdx-lint: allow worktree, glibc, musl, and checksum.
2026-10-02 08:39:18 +02:00

63 lines
2.1 KiB
TypeScript

import type { ContentListingGroup } from '~/lib/content-listings.schema'
export const localDevelopmentParallelProjectsLearnMore: ContentListingGroup = {
id: 'local-development-parallel-projects-learn-more',
heading: 'Learn more',
type: 'grid',
columns: 2,
items: [
{
title: 'Install and run the CLI',
href: '/guides/local-development/cli/getting-started',
description: 'Install the CLI and start your first local project.',
},
{
title: 'Local development workflow',
href: '/guides/local-development/cli-workflows',
description: 'Day-to-day commands for one local project, from migrations to troubleshooting.',
},
{
title: 'Docker and native runtimes',
href: '/guides/local-development/docker-and-native-runtimes',
description:
'How the CLI picks a runtime, what the native runtime needs, and where it stores data.',
},
{
title: 'Managing config and secrets',
href: '/guides/local-development/managing-config',
description:
'Keep configuration and secrets consistent across local, staging, and production.',
},
{
title: 'CLI configuration',
href: '/guides/local-development/cli/config',
description: 'Every key in config.toml, including the experimental stack setting.',
},
],
}
export const localDevelopmentRuntimesLearnMore: ContentListingGroup = {
id: 'local-development-runtimes-learn-more',
heading: 'Learn more',
type: 'grid',
columns: 3,
items: [
{
title: 'Running multiple local projects',
href: '/guides/local-development/running-multiple-local-projects',
description:
'Run a local project for every app, git worktree, or environment on one machine.',
},
{
title: 'Install and run the CLI',
href: '/guides/local-development/cli/getting-started',
description: 'Install the CLI and start your first local project.',
},
{
title: 'CLI configuration',
href: '/guides/local-development/cli/config',
description: 'Every key in config.toml, including the experimental stack setting.',
},
],
}