Primo is a component-based CMS that makes it easier to develop, manage, and publish static sites. This project hosts Primo as a SvelteKit application and integrates it with Supabase to enable authentication, media uploads, and data storage. A single Primo server can handle hundreds of sites, publishes static sites to their own repos/endpoints, and enables rapid component-driven development.

This is a base repository for Primo Server that you can fork to host your own Server. All you need is a Supabase and Vercel or Cloudflare account (all free), and a few minutes to put up your Server from which you can create and manage one to hundreds of sites. Compared to Primo Desktop, Primo Server enables you to access your sites online, collaborate with developers and marketers, and upload images. You can also access your Server sites from Primo Desktop.

• Multiple users
• Image uploads
• Use from anywhere

Primo Server is in Beta. It is stable enough for personal projects.

This repo deploys Primo to Vercel or Cloudflare and uses Supabase for authentication, database (PostgreSQL), and storage.

Primo can be run on the free tier of either service (Vercel/Cloudflare & Supabase), and you can sign in with Github.

Before deploying your Primo Server, you'll need to sign up for Supabase and create a new project.

1. Create a Supabase account or sign in with Github
2. Create a new project
3. Disable email confirmations (Authentication > Providers > expand Email and uncheck 'Confirm email')
4. Select 'SQL' from the sidebar navigation
5. Click + New query
6. Paste in the contents of ./primo_schema.sql and click 'RUN'

1. Create a new Vercel project
2. Select your forked repository
3. Enter the following environment variables: your Supabase project URL, Public Key (anon public), and Admin Key (service_role secret) (which you can find in the Supabase project dashboard > Settings > API https://app.supabase.io/project/---yourprojectid---/settings/api) and deploy.

• VITE_SUPABASE_URL
• VITE_SUPABASE_PUBLIC_KEY
• VITE_SUPABASE_ADMIN_KEY

1. Create a new Cloudflare Pages project
2. Select your forked repository
3. Configure the project according to the screenshot below - don't select a framework preset, enter the build command, output directory, and the following environment variables - and deploy.

• VITE_SUPABASE_URL
• VITE_SUPABASE_PUBLIC_KEY
• VITE_SUPABASE_ADMIN_KEY
• NODE_VERSION = 16

4. Navigate to your new Primo Server. Sign up with an email address and password (this will be the admin account).

You can merge upstream updates by clicking 'Sync fork' on your forked repository. Your updates will automatically deploy to your Vercel/Cloudflare account.