You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(apple-containers): add Apple Containers runtime support
Allow Supabase CLI-managed services to run on Apple Containers via
--runtime apple-container or [local].runtime in config.toml.
Keep Docker as the default runtime while adding runtime-aware service
lifecycle handling, analytics log forwarding, status reporting, and
related test coverage for Apple container execution paths.
Copy file name to clipboardExpand all lines: docs/supabase/start.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@ Starts the Supabase local development stack.
4
4
5
5
Requires `supabase/config.toml` to be created in your current working directory by running `supabase init`.
6
6
7
+
Use `--runtime` to override the local container runtime for the current command. To make it persistent for the project, set `[runtime].backend` in `supabase/config.toml`.
8
+
7
9
All service containers are started by default. You can exclude those not needed by passing in `-x` flag. To exclude multiple containers, either pass in a comma separated string, such as `-x gotrue,imgproxy`, or specify `-x` flag multiple times.
8
10
9
11
> It is recommended to have at least 7GB of RAM to start all services.
Copy file name to clipboardExpand all lines: docs/supabase/status.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,4 +4,6 @@ Shows status of the Supabase local development stack.
4
4
5
5
Requires the local development stack to be started by running `supabase start` or `supabase db start`.
6
6
7
+
The pretty output includes a runtime summary with the selected local runtime, project id, and tracked containers, networks, and volumes.
8
+
7
9
You can export the connection parameters for [initializing supabase-js](https://supabase.com/docs/reference/javascript/initializing) locally by specifying the `-o env` flag. Supported parameters include `JWT_SECRET`, `ANON_KEY`, and `SERVICE_ROLE_KEY`.
Copy file name to clipboardExpand all lines: docs/supabase/stop.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,6 @@ Stops the Supabase local development stack.
4
4
5
5
Requires `supabase/config.toml` to be created in your current working directory by running `supabase init`.
6
6
7
-
All Docker resources are maintained across restarts. Use `--no-backup` flag to reset your local development data between restarts.
7
+
Local container resources are maintained across restarts for both the `docker` and `apple-container` runtimes. Use `--no-backup` flag to reset your local development data between restarts.
8
8
9
-
Use the `--all` flag to stop all local Supabase projects instances on the machine. Use with caution with `--no-backup` as it will delete all supabase local projects data.
9
+
Use the `--all` flag to stop all local Supabase projects instances on the machine. Use with caution with `--no-backup` as it will delete all supabase local projects data.
0 commit comments