apps/docs/content/guides/getting-started/quickstarts/spring-boot.mdx
Before you begin, make sure you have:
java -versioncurl and unzip, to download and extract the generated project<$Partial path="quickstart_create_project.mdx" />
Save your database password securely. You need it for the connection string.
Use Spring Initializr to scaffold a new project with the Web, Spring Data JPA, and Postgres Driver dependencies. Run the following from the directory where you keep your projects.
curl https://start.spring.io/starter.zip \
-d dependencies=web,data-jpa,postgresql \
-d type=maven-project \
-d language=java \
-d groupId=com.example \
-d artifactId=instruments \
-d name=instruments \
-o instruments.zip
unzip instruments.zip -d instruments && cd instruments
Supabase's Agent Skills is a curated set of instructions that give your AI agent procedural knowledge about working with Supabase.
Install them so your AI coding agent can produce more accurate, reliable code using current Supabase patterns, such as authentication, server-side rendering, and database migrations, rather than relying solely on training data.
To install, run the following command in the root of your project:
npx skills add supabase/agent-skills
Navigate to your project dashboard and click on Connect.
<Admonition type="caution">The Transaction pooler (port 6543) doesn't work as your app's main data source, because Spring Data JPA uses Hibernate, which relies on server-side prepared statements. Use the Session pooler, or the direct connection string if you're in an IPv6 environment or have the IPv4 Add-On.
Under the Session pooler (port 5432), select the JDBC tab and copy the connection string. Replace the password placeholder with your saved database password, and percent-encode any reserved characters it contains, such as &, #, ?, or a space.
You can reset your database password in your Database Settings if you do not have it.
</Admonition>The connection string contains your database password, and application.properties is committed with your project. Set the string as an environment variable instead, and set it the same way on whatever platform you deploy to.
export SUPABASE_DB_URL='jdbc:postgresql://aws-[REGION].pooler.supabase.com:5432/postgres?user=postgres.[PROJECT-REF]&password=[YOUR-PASSWORD]&sslmode=require'
The string you copied doesn't set sslmode, so add it. The driver defaults to prefer, which falls back to sending your data in plaintext if the encrypted attempt fails. You can also enforce SSL on the database side.
Then reference the variable, along with the driver, in src/main/resources/application.properties.
spring.datasource.url=${SUPABASE_DB_URL}
spring.datasource.driver-class-name=org.postgresql.Driver
spring.jpa.hibernate.ddl-auto=update
If the app fails to start with Unable to determine Dialect without JDBC metadata, Hibernate couldn't open a connection at all. Look above that line in the logs for the real cause, most commonly password authentication failed.
By default Hibernate creates tables in the public schema. We recommend changing this as Supabase exposes the public schema as a data API.
Create the schema from the Table Editor as your app will need it before start. Then point Hibernate at it in application.properties.
spring.jpa.properties.hibernate.default_schema=app
Spring Data JPA maps Java classes to database tables. Create an Instrument entity in src/main/java/com/example/instruments/Instrument.java. With spring.jpa.hibernate.ddl-auto=update set, Hibernate creates the instruments table for you when the app starts.
package com.example.instruments;
import jakarta.persistence.Entity;
import jakarta.persistence.GeneratedValue;
import jakarta.persistence.GenerationType;
import jakarta.persistence.Id;
import jakarta.persistence.Table;
@Entity
@Table(name = "instruments")
public class Instrument {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
private String name;
public Instrument() {}
public Instrument(String name) {
this.name = name;
}
public Long getId() {
return id;
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}
Create an InstrumentRepository interface in the same package. Extending JpaRepository gives you findAll, save, and other query methods without writing any implementation.
package com.example.instruments;
import org.springframework.data.jpa.repository.JpaRepository;
public interface InstrumentRepository extends JpaRepository<Instrument, Long> {}
Add a CommandLineRunner bean to InstrumentsApplication.java that saves some sample instruments the first time the app starts.
package com.example.instruments;
import org.springframework.boot.CommandLineRunner;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Bean;
@SpringBootApplication
public class InstrumentsApplication {
public static void main(String[] args) {
SpringApplication.run(InstrumentsApplication.class, args);
}
@Bean
CommandLineRunner seedInstruments(InstrumentRepository instrumentRepository) {
return args -> {
if (instrumentRepository.count() == 0) {
instrumentRepository.save(new Instrument("violin"));
instrumentRepository.save(new Instrument("viola"));
instrumentRepository.save(new Instrument("cello"));
}
};
}
}
Create an InstrumentController that fetches every row from the instruments table through the repository and returns it as JSON.
package com.example.instruments;
import java.util.List;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
@RestController
public class InstrumentController {
private final InstrumentRepository instrumentRepository;
public InstrumentController(InstrumentRepository instrumentRepository) {
this.instrumentRepository = instrumentRepository;
}
@GetMapping("/instruments")
public List<Instrument> getInstruments() {
return instrumentRepository.findAll();
}
}
Run the Spring Boot app, and go to http://localhost:8080/instruments in your browser. You should see the list of instruments.
./mvnw spring-boot:run
ddl-auto with database migrations before going to production