What a build contains
What a build of an application with spring_boot_starter_supabase contains, and when something is not in it. A module that follows a key reads it when build_runner runs, from application.yml or application.properties without a profile (see Modules left out of the build). The modules of the packages it depends on come with it: for spring_boot_dart, see Auto-configuration.
Always in
No build: and no platform:: in every build of an application that depends on the starter.
| Module | What it holds |
|---|---|
springBootStarterSupabaseDataAutoConfiguration |
How the repositories reach the database, as defaults of the data starter's properties (the lowest precedence): spring.supabase.db.url set makes it spring.datasource.url; not set, spring.data.store is supabase, the store over the project's REST API. Before the data starter's module. |
springBootStarterSupabaseAutoConfiguration |
The credentials, the HTTP client, the data store, Storage, Edge Functions, the cache keys, Auth and Realtime. |
By platform
platform:: the module is only in the build of that platform; no property is read.
| Module | Platform | What it holds |
|---|---|---|
springBootStarterSupabaseServerAutoConfiguration |
server |
The defaults of Spring Security's resource server, so that a server accepts the tokens of the project's Auth as bearer tokens (properties of the lowest precedence). |
springBootStarterSupabaseAdminAutoConfiguration |
server |
supabaseAuthAdmin, the admin API of Supabase Auth, which manages users as the service role. It uses the service-role key, which passes row-level security and must never ship in an app. |
native: builds where dart:io exists (a server, an AOT executable, a Flutter app on a phone or a desktop), not a browser build. server: native without Flutter, never a Flutter app. -DSPRING_ALL_PLATFORMS=true keeps every module.
What the generator writes for it
A part of the generator (see Starter parts) runs only when the application reaches its package.
| Part or builder | What it does |
|---|---|
| Through its dependencies | The parts of the packages the starter reaches: data (the supabaseStore is described to the build, so a repository method the store cannot do fails the build), cache, WebSocket, security, web and actuator. No part of its own. |
Good to know
- A Flutter app (on a phone, a desktop or the web) and a browser build compile the two server modules away. An edge function, compiled with
-DSPRING_ALL_PLATFORMS=true, keeps them.