Connect your Supabase project.

1. Create the library tables

Open your project’s SQL Editor and create a new query. Open the file below, copy the entire SQL, paste it into the editor, and click Run. Run this migration once in a new project.

You should see Success. No rows returned. It creates the catalog, access policies, audit history, and cover storage bucket. If it fails, the transaction rolls back; resolve the reported error before retrying.

2. Create your administrator login

Go to Authentication → Users → Add user → Create new user. Enter your email and a strong password. Enable Auto Confirm User if offered. Keep the password private. New accounts start with the reader role.

3. Assign the administrator role

Open the SQL below. Replace both occurrences of YOUR_ADMIN_EMAIL with the email you just created. Run it in SQL Editor. The final result should show your email and the role admin.

Only your project-owner dashboard should assign roles. Never add this SQL or a privileged key to the website’s JavaScript.

4. Add your first book

Open the admin workspace below and sign in. Choose Add book, fill in its details, and save as Draft. Review with Preview, then publish it. Published books appear in the reader library; drafts and archived books stay in administration.

The live catalog starts empty. Fictional sample titles are not automatically imported. This version manages catalog information and covers; payments, real borrowing, and licensed e-book/audio delivery remain future features.

Check access and keep backups

Test that a reader account cannot enter administration, and that the public catalog shows only published books. Export JSON for a metadata copy. Back up the Supabase database and cover files separately for recovery. Cover images are public, including draft covers; do not upload licensed books/audio to the cover bucket.