2. Set up your database
When your Zuvo 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.
-- 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);
3. Create an Astro app
Create an Astro app using the npm create command.
npm create astro@latest my-app
cd my-app
4. Set up AI tooling (optional)
Zuvo 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 Zuvo project directly.
Agent Skills
Agent Skills is a curated set of instructions that give your AI agent procedural knowledge about working with Zuvo.
Install them so your AI coding agent can produce more accurate, reliable code using current Zuvo 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-skills
Zuvo MCP server
The Zuvo MCP server connects AI assistants to Zuvo, 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 Zuvo client library and Node adapter
Install the supabase-js client library and the @astrojs/node adapter to enable server-side rendering.
npm install @supabase/supabase-js @astrojs/node
6. Configure Astro for SSR
Update your astro.config.mjs.
import node from '@astrojs/node'
import { defineConfig } from 'astro/config'
export default defineConfig({
output: 'server',
adapter: node({
mode: 'standalone',
}),
})
7. Declare Zuvo environment variables
Create a .env.local file and populate with your Zuvo connection variables that you can get from the helper below, or from the project Connect panel:
Open Connect panel
PUBLIC_SUPABASE_URL=<SUBSTITUTE_SUPABASE_URL>
PUBLIC_SUPABASE_PUBLISHABLE_KEY=<SUBSTITUTE_SUPABASE_PUBLISHABLE_KEY>
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.
8. Create a Zuvo client helper
Create a utility file to initialize the Zuvo client:
import { createClient } from '@supabase/supabase-js'
const supabaseUrl = import.meta.env.PUBLIC_SUPABASE_URL
const supabasePublishableKey = import.meta.env.PUBLIC_SUPABASE_PUBLISHABLE_KEY
export function createServerClient() {
return createClient(supabaseUrl, supabasePublishableKey)
}
9. Query Zuvo data from Astro
Create a new file at src/pages/instruments.astro and populate with the following.
This queries all rows from the instruments table you created earlier and renders them on the page.
---
import { createServerClient } from "../lib/supabase";
const supabase = createServerClient();
const { data: instruments, error } = await supabase.from("instruments").select();
---
<html>
<head>
<title>Instruments</title>
</head>
<body>
{error ? (
<p>Error loading instruments: {error.message}</p>
) : (
<ul>
{instruments?.map((instrument) => (
<li>{instrument.name}</li>
</ul>
</body>
</html>
10. Start the app
Run the development server, go to http://localhost:4321/instruments in your browser of choice to check the list of instruments.
npm run dev
Production 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 Zuvo credentials as environment variables on whatever platform you deploy to, rather than committing them to source control.
- Configure a custom domain for your Zuvo project once you're ready to go live.
Next steps
- Set up Auth for your app
- Insert more data into your database
- Upload and serve static files using Storage