本页还没有译文
本页 53 段还没译成简体中文,下面显示的是英文原文。Use Supabase with Hono
还没翻译译自英文(supabase.com)本页 53 段都还没译
Agent Prompt
Help me add Supabase to my Hono project. Create a Supabase project at
database.new and run the instruments table SQL. Then:
1. Run `npx supabase@latest bootstrap hono` to scaffold the app with Supabase
and SSR auth pre-configured.
2. Run `npm install` to install dependencies.
3. Copy `.env.example` to `.env`, set your Supabase URL and publishable key,
and enable anonymous sign-ins in the Auth settings.
4. Run `npm run dev` and open http://localhost:5173.
REFERENCE
https://supabase.com/docs/guides/getting-started/quickstarts/hono.md1. Create a Supabase project
To start, you need a Supabase project.
Create a new Supabase project from the Dashboard of any organization you belong to.
Want to create a project programmatically?
Use the Management API or ask the MCP server to create a new Supabase project.
2. Set up your database
When your Supabase project is up and running, create an instruments table with some sample data. Then set only the privileges each Postgres role needs, add Row Level Security (RLS) for enhanced security for database data by default, and create an RLS policy to make the data in the table publicly readable.
Do these steps within your project's dashboard by copying and running the snippet in your project's SQL Editor.
Note
Save some steps by clicking here to prefill the SQL in the SQL Editor, and then clicking Run.
Want to setup the database programmatically?
You can use the Management API or ask the MCP server to execute SQL queries.
-- Create the table
create table instruments (
id bigint primary key generated always as identity,
name text not null
);
-- Insert sample data into the table
insert into instruments (name)
values
('violin'),
('viola'),
('cello');
-- Grant the privileges the role needs, which is read access
grant select on public.instruments to anon;
-- Enable row level security for the table
alter table instruments enable row level security;
-- Create a policy to allow the anon role to read from the instruments table
create policy "public can read instruments"
on public.instruments
for select to anon
using (true);Disabled the Data API during project setup?
If you disabled the Data API during project setup, enable it in the Integrations > Data API section of the Dashboard and expose the specific tables or functions you want to access. To automatically grant access for new tables and functions in public, enable Automatically expose new tables.
3. Create a Hono app
Bootstrap the Hono example app from the Supabase Samples using the CLI.
npx supabase@latest bootstrap hono4. Set up AI tooling (optional)
Supabase provides two ways to give AI tools context about your project: Agent Skills, which give your AI coding agent procedural knowledge, and the MCP server, which connects AI assistants to your Supabase project directly.
Agent Skills
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.
Installing Agent Skills
To install, run the following command in the root of your project:
npx skills add supabase/agent-skillsSupabase MCP server
The Supabase MCP server connects AI assistants to Supabase, so they can inspect your schema and act on your projects on your behalf. Find out how to add it to your client in the MCP docs.
5. Install dependencies
The package.json file in the project includes the necessary dependencies, including @supabase/supabase-js and @supabase/ssr to help with server-side auth.
npm install6. Declare Supabase environment variables
Copy the .env.example file to .env.
cp .env.example .envUpdate the values with your Supabase project URL and publishable key, which you can get from the helper below, or from the project Connect panel.
Get API details
To interact with data in database tables, you use the client libraries that wrap the auto-generated Data API endpoints, authenticating using the Project URL and key from the project Connect dialog.
Project URL: https://<project-ref>.supabase.co (find yours in the dashboard)
Publishable key: sb_publishable_... (find yours in the dashboard)
Note
See API keys for a full explanation of all key types, their uses, and where to find them.
7. Set up anonymous sign-ins
This app signs users in anonymously, so enable anonymous sign-ins in the Auth settings.
Anonymous sign-ins use the authenticated role, but the database setup in step 2 grants read access to the anon role only. Without the privilege and a matching policy for authenticated, the instruments query returns no rows. Grant the privilege and add the policy. Run the following SQL using the SQL Editor in the Supabase Dashboard or with psql over a direct connection. To connect with psql, see Direct connection.
grant select on public.instruments to authenticated;
create policy "authenticated can read instruments"
on public.instruments
for select to authenticated
using (true);8. Query data from the app
The bootstrapped app already includes the route that reads your instruments table, in src/index.tsx. The middleware in src/middleware/auth.middleware.ts creates a request-scoped Supabase client, so getSupabase(c) returns a client that already carries the signed-in user's auth token. Your RLS policies apply to the query.
app.get('/instruments', async (c) => {
const supabase = getSupabase(c)
const { data, error } = await supabase.from('instruments').select('*')
if (error) {
console.error(error)
return c.json({ error: error.message }, 500)
}
return c.json(data)
})9. Start the app
Start the app, go to http://localhost:5173, sign in anonymously, then open the instruments list.
npm run devProduction requirements
The quickstart procedure in this guide optimizes for getting you to a working app, not for production.
Before you deploy:
- If your app reads or writes through the Data API, review your Row Level Security policies. Any policy you added here is scoped to this quickstart's sample data, not to real user data.
- Set your Supabase credentials as environment variables on whatever platform you deploy to, rather than committing them to source control.
- Configure a custom domain for your Supabase project once you're ready to go live.
Next steps
- Learn how server side auth works with Hono.
- Insert more data into your database
- Upload and serve static files using Storage