Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Knill01/PM-Hive/llms.txt

Use this file to discover all available pages before exploring further.

Hive requires several environment variables to connect to Supabase and configure authentication. These variables must be set in your deployment environment (Vercel, Netlify, etc.) or locally for development.

​
Required Environment Variables

​
SUPABASE_URL
string
required
Your Supabase project URL. Format: https://[project-ref].supabase.coExample: https://vcssfbdprqmpmuhwaapb.supabase.co
​
SUPABASE_ANON_KEY
string
required
The anonymous (public) key for your Supabase project. This key is safe to use in client-side code and respects Row Level Security policies.Find this in your Supabase project dashboard under Settings → API.
​
SUPABASE_SERVICE_KEY
string
required
The service role key for server-side operations that bypass Row Level Security. Keep this secret - never expose it to the client.
The service role key has full database access and bypasses all RLS policies. Only use it in serverless functions or backend code. Never include it in client-side bundles.
Alternative names supported: SUPABASE_SERVICE_ROLE_KEY
​
ADMIN_EMAILS
string
Comma-separated list of email addresses to grant admin access, bypassing the usuarios.rol check.Example: admin@company.com,superadmin@company.comUsed by the /api/auth-sync serverless function to whitelist administrators.

​
Client-Side Variables (Vercel)

When deploying to Vercel or similar platforms, you can prefix environment variables with NEXT_PUBLIC_ to make them available in the client bundle:
​
NEXT_PUBLIC_SUPABASE_URL
string
Client-accessible Supabase URL (alternative to SUPABASE_URL)
​
NEXT_PUBLIC_SUPABASE_ANON_KEY
string
Client-accessible anonymous key (alternative to SUPABASE_ANON_KEY)
The application automatically falls back between NEXT_PUBLIC_* prefixed variables and regular environment variables. See supabaseClient.js:14-22 for implementation details.

​
Environment Variable Priority

The Supabase client initialization follows this priority order:
  1. Process environment variables - process.env.NEXT_PUBLIC_SUPABASE_URL
  2. Window globals - window.SUPABASE_URL (for local development)
  3. Hardcoded fallbacks - Development defaults (only for development)
// Environment variable resolution
const supabaseUrl =
  (typeof process !== 'undefined' && process.env?.NEXT_PUBLIC_SUPABASE_URL) ||
  window.SUPABASE_URL ||
  'https://vcssfbdprqmpmuhwaapb.supabase.co'; // fallback for development

const supabaseAnonKey =
  (typeof process !== 'undefined' && process.env?.NEXT_PUBLIC_SUPABASE_ANON_KEY) ||
  window.SUPABASE_ANON_KEY ||
  'eyJhbGci...';

​
Development Setup

For local development, create a .env.local file in the frontend directory:
.env.local
# Supabase Configuration
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
SUPABASE_SERVICE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

# Admin Whitelist
ADMIN_EMAILS=your-email@company.com

# Vercel Deployment (optional)
NEXT_PUBLIC_SUPABASE_URL=${SUPABASE_URL}
NEXT_PUBLIC_SUPABASE_ANON_KEY=${SUPABASE_ANON_KEY}
Never commit .env.local or .env files to version control. Add them to .gitignore.

​
Production Setup

​
Vercel

Set environment variables in the Vercel dashboard:
  1. Go to Project Settings → Environment Variables
  2. Add each variable for Production, Preview, and Development environments
  3. Click Save

​
Other Platforms

For Netlify, Railway, or other platforms, refer to their documentation for setting environment variables:
  • Netlify: Site Settings → Build & Deploy → Environment
  • Railway: Project Settings → Variables
  • Render: Environment → Environment Variables

​
Validation

The application validates the Supabase connection on initialization: 
// supabaseClient.js:48-60
supabase.from('usuarios').select('count', { count: 'exact', head: true })
  .then(response => {
    if (response.error) {
      console.error('❌ Error conectando a Supabase:', response.error.message);
    } else {
      console.log('✅ Supabase conectado correctamente (usuarios table accesible)');
    }
  });
Check the browser console for connection status messages when the application loads.

​
Troubleshooting

This error occurs when serverless functions cannot find required environment variables.Solution: Ensure SUPABASE_URL, SUPABASE_ANON_KEY, and SUPABASE_SERVICE_KEY (or SUPABASE_SERVICE_ROLE_KEY) are set in your deployment environment.
The Supabase JavaScript SDK is not loaded from the CDN.Solution: Verify that index.html includes the Supabase CDN script:
<script src="https://unpkg.com/@supabase/supabase-js"></script>
The client is not authenticated or the access token is invalid.Solution: Ensure users are logged in before making API calls. The serverless functions require a valid Authorization: Bearer <token> header.

Build docs developers (and LLMs) love

Get started for freeTalk to us