@knowcode/doc-builder 1.8.2 → 1.8.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knowcode/doc-builder",
-  "version": "1.8.2",
+  "version": "1.8.4",
   "description": "Reusable documentation builder for markdown-based sites with Vercel deployment support",
   "main": "index.js",
   "bin": {

package/setup-database-v2.sql

@@ -0,0 +1,53 @@
+-- Doc-builder Supabase Database Setup V2
+-- Simplified schema using domains instead of site IDs
+-- Run this in your Supabase SQL Editor
+
+-- Drop old tables if migrating
+-- DROP TABLE IF EXISTS docbuilder_access;
+-- DROP TABLE IF EXISTS docbuilder_sites;
+
+-- Single table for user access control
+CREATE TABLE docbuilder_access (
+    user_id UUID REFERENCES auth.users(id) ON DELETE CASCADE,
+    domain TEXT NOT NULL,
+    created_at TIMESTAMPTZ DEFAULT NOW(),
+    PRIMARY KEY (user_id, domain)
+);
+
+-- Create index for faster lookups
+CREATE INDEX idx_docbuilder_access_domain ON docbuilder_access(domain);
+
+-- Enable Row Level Security
+ALTER TABLE docbuilder_access ENABLE ROW LEVEL SECURITY;
+
+-- RLS Policy: Users can only see their own access
+CREATE POLICY "Users see own access" ON docbuilder_access
+    FOR SELECT USING (user_id = auth.uid());
+
+-- Example: Grant access to a user for a specific domain
+-- INSERT INTO docbuilder_access (user_id, domain) 
+-- VALUES ('user-uuid-here', 'doc-builder-delta.vercel.app');
+
+-- Example: Grant access to multiple users for a domain
+-- INSERT INTO docbuilder_access (user_id, domain) VALUES 
+--   ('user-1-uuid', 'mydocs.vercel.app'),
+--   ('user-2-uuid', 'mydocs.vercel.app'),
+--   ('user-3-uuid', 'mydocs.vercel.app');
+
+-- Example: Grant a user access to multiple domains
+-- INSERT INTO docbuilder_access (user_id, domain) VALUES 
+--   ('user-uuid', 'docs.example.com'),
+--   ('user-uuid', 'internal-docs.example.com'),
+--   ('user-uuid', 'api-docs.example.com');
+
+-- View all access for a domain (admin use)
+-- SELECT u.email, da.created_at
+-- FROM docbuilder_access da
+-- JOIN auth.users u ON da.user_id = u.id
+-- WHERE da.domain = 'mydocs.vercel.app';
+
+-- Migration from old schema (if needed)
+-- INSERT INTO docbuilder_access (user_id, domain)
+-- SELECT da.user_id, ds.domain
+-- FROM old_docbuilder_access da
+-- JOIN docbuilder_sites ds ON da.site_id = ds.id;

package/user-access-view.sql

@@ -0,0 +1,49 @@
+-- Create a view to easily see user access with email addresses
+-- This makes it much easier to manage user access
+
+-- Drop the view if it exists (to recreate with latest schema)
+DROP VIEW IF EXISTS user_access_view;
+
+-- Create the view joining docbuilder_access with auth.users
+CREATE VIEW user_access_view AS
+SELECT 
+    u.email,
+    da.domain,
+    da.created_at as access_granted,
+    u.created_at as user_created,
+    u.last_sign_in_at,
+    u.id as user_id
+FROM 
+    docbuilder_access da
+    JOIN auth.users u ON da.user_id = u.id
+ORDER BY 
+    da.domain, 
+    u.email;
+
+-- Grant permissions to authenticated users to view their own records
+GRANT SELECT ON user_access_view TO authenticated;
+
+-- Example queries using the view:
+
+-- 1. See all users for a specific domain
+-- SELECT * FROM user_access_view WHERE domain = 'docs.example.com';
+
+-- 2. See all domains a user has access to
+-- SELECT * FROM user_access_view WHERE email = 'user@example.com';
+
+-- 3. Count users per domain
+-- SELECT domain, COUNT(*) as user_count 
+-- FROM user_access_view 
+-- GROUP BY domain 
+-- ORDER BY user_count DESC;
+
+-- 4. Find users who haven't logged in recently
+-- SELECT email, domain, last_sign_in_at 
+-- FROM user_access_view 
+-- WHERE last_sign_in_at < NOW() - INTERVAL '30 days'
+-- OR last_sign_in_at IS NULL;
+
+-- 5. Export all access for documentation
+-- SELECT email, domain, access_granted 
+-- FROM user_access_view 
+-- ORDER BY domain, email;

package/user-management/README.md

@@ -217,10 +217,7 @@ Run the setup command:
 
 ### "Site not found"
 
-Make sure the site exists in the `docbuilder_sites` table. You can check with:
-```bash
-./add-users.sh sites
-```
+With the new domain-based system, sites no longer need to be registered. Just use the domain directly when granting access.
 
 ### "User already exists"
 
@@ -232,29 +229,23 @@ The user already has access to this site. No action needed.
 
 ## 📊 Database Schema
 
-The system uses two main tables:
-
-### docbuilder_sites
-- `id` (UUID) - Primary key
-- `domain` (TEXT) - Site URL without https://
-- `name` (TEXT) - Display name
-- `created_at` (TIMESTAMP)
+The system uses a single table with domain-based access:
 
 ### docbuilder_access
 - `user_id` (UUID) - References auth.users
-- `site_id` (UUID) - References docbuilder_sites
+- `domain` (TEXT) - Site domain (e.g., docs.example.com)
 - `created_at` (TIMESTAMP)
+- Primary key on (user_id, domain)
 
 ## 🎯 Common Workflows
 
 ### Setting up a new documentation site
 
-1. Add the site to the database (manually or via SQL)
-2. Add users who should have access:
-   ```bash
-   ./add-users.sh add my-docs.vercel.app user1@example.com
-   ./add-users.sh add my-docs.vercel.app user2@example.com
-   ```
+No site registration needed! Just add users with domain access:
+```bash
+./add-users.sh add my-docs.vercel.app user1@example.com
+./add-users.sh add my-docs.vercel.app user2@example.com
+```
 
 ### Onboarding multiple team members
 

package/user-management/add-users.sh

@@ -18,8 +18,14 @@ NC='\033[0m' # No Color
 # Configuration
 SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
 CONFIG_FILE="$SCRIPT_DIR/.supabase-config"
+ENV_FILE="$SCRIPT_DIR/.env"
 PROJECT_ID="xcihhnfcitjrwbynxmka"  # Default project ID
 
+# Load .env file if exists
+if [ -f "$ENV_FILE" ]; then
+    source "$ENV_FILE"
+fi
+
 # Load configuration if exists
 if [ -f "$CONFIG_FILE" ]; then
     source "$CONFIG_FILE"
@@ -209,7 +215,7 @@ execute_sql() {
     
     # Method 1: Try using psql if DATABASE_URL is available
     if [ ! -z "$DATABASE_URL" ]; then
-        local output=$(psql "$DATABASE_URL" -f "$temp_file" 2>&1)
+        local output=$(psql "$DATABASE_URL" -t -A -f "$temp_file" 2>&1)
         local status=$?
         rm "$temp_file"
         
@@ -219,15 +225,21 @@ execute_sql() {
         fi
     fi
     
-    # Method 2: Try newer supabase db execute (for newer CLI versions)
-    if command -v supabase &> /dev/null && supabase db execute --help &> /dev/null 2>&1; then
-        local output=$(cat "$temp_file" | supabase db execute 2>&1)
-        local status=$?
-        rm "$temp_file"
+    # Method 2: Try using supabase db dump to get connection details
+    if command -v supabase &> /dev/null; then
+        # Get database URL from supabase status
+        local db_url=$(supabase status --output json 2>/dev/null | grep -o '"db_url":"[^"]*' | cut -d'"' -f4)
         
-        if [ $status -eq 0 ]; then
-            echo "$output"
-            return 0
+        if [ ! -z "$db_url" ] && [ "$db_url" != "null" ]; then
+            # Try psql with the extracted URL
+            local output=$(psql "$db_url" -t -A -f "$temp_file" 2>&1)
+            local status=$?
+            rm "$temp_file"
+            
+            if [ $status -eq 0 ]; then
+                echo "$output"
+                return 0
+            fi
         fi
     fi
     
@@ -257,9 +269,17 @@ create_user() {
     # Check if user exists first
     local check_sql="SELECT id, email FROM auth.users WHERE email = '$email';"
     
-    local result=$(execute_sql "$check_sql")
+    echo -e "${CYAN}Checking database for user...${NC}"
+    local result=$(execute_sql "$check_sql" 2>&1)
+    
+    # Debug output
+    if [ ! -z "$DEBUG" ]; then
+        echo -e "${BLUE}[DEBUG] SQL Result:${NC}"
+        echo "$result"
+    fi
     
-    if echo "$result" | grep -q "$email"; then
+    # Check if the result contains the email (case insensitive)
+    if echo "$result" | grep -qi "$email"; then
         echo -e "${YELLOW}ℹ️  User already exists${NC}"
         return 0
     else