Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/emmanueljarquin-sys/GrupoMecsaCMS/llms.txt

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

​
Overview

Grupo Mecsa CMS uses Supabase as its backend database and authentication provider. The system automatically detects whether it’s running in production or development and loads the appropriate configuration.

​
Configuration Files

The CMS uses two main configuration approaches:

​
1. Main Configuration File

Location: config/supabase.php This is the centralized configuration file that handles:
  • Environment detection (production vs development)
  • Loading credentials from environment variables or defaults
  • Providing helper functions for API requests

​
2. Supabase Class

Location: supabase.php (root) Provides object-oriented interface for:
  • Authentication (login, password reset)
  • Data operations (CRUD)
  • Admin operations (user management)

​
Environment-Specific Configuration

​
Production Environment

The system automatically detects production when the hostname contains grupomecsa.net
In production, credentials are loaded from:
  1. Environment variables (recommended)
  2. Default values in config/supabase.php
$supabase_url = getenv('SUPABASE_URL') ?: 'https://awhuzekjpoapamijlvua.supabase.co';
$supabase_key = getenv('SUPABASE_KEY') ?: 'sb_publishable_G6dRjvRfALqwuYaG1kew7w_Xud8hTgb';
$supabase_service_role = getenv('SUPABASE_SERVICE_ROLE') ?: 'sb_secret_C-Z-MttzHCPnOR1y2Py4rw_VSsTvV_w';

​
Development Environment

Local configuration is only loaded when not in production environment
For local development, create a local.supabase.php file in the root directory:
local.supabase.php
<?php
// Local Supabase Configuration (Development Only)
$supabase_url = 'https://your-project.supabase.co';
$supabase_key = 'your-anon-public-key';
$supabase_service_role = 'your-service-role-key';
?>
Never commit local.supabase.php to version control! Add it to .gitignore to prevent exposing credentials.

​
Setup Instructions

1

Get Supabase Credentials

  1. Log in to your Supabase Dashboard
  2. Select your project
  3. Go to Settings → API
  4. Copy the following:
    • Project URL
    • anon public key
    • service_role key (for admin operations)
2

Configure Development Environment

Create local.supabase.php in the root directory:
<?php
$supabase_url = 'https://xxxxx.supabase.co';
$supabase_key = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...';
$supabase_service_role = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...';
?>
3

Configure Production Environment

Set environment variables on your server:
export SUPABASE_URL="https://xxxxx.supabase.co"
export SUPABASE_KEY="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
export SUPABASE_SERVICE_ROLE="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
Or configure in Apache/PHP-FPM:
.htaccess
SetEnv SUPABASE_URL "https://xxxxx.supabase.co"
SetEnv SUPABASE_KEY "your-anon-key"
SetEnv SUPABASE_SERVICE_ROLE "your-service-role-key"
4

Set Database Schema

The CMS uses the cms schema by default. This is configured in config/supabase.php:
$supabase_schema = 'cms';
Ensure your Supabase database has a cms schema with the required tables.
5

Verify Configuration

Test the connection by logging into the CMS at http://localhost/GrupoMecsaCMS/login.php

​
Configuration Details

​
Key Types

The CMS requires two different API keys for different security levels:
Key TypeVariableUsage
Anon/Public Key$supabase_keyStandard database operations with Row Level Security (RLS)
Service Role Key$supabase_service_roleAdmin operations that bypass RLS (user management, password resets)

​
Schema Configuration

The system uses schema-based routing for API requests: 
$supabase_schema = 'cms'; // Default schema
All REST API requests include these headers:
  • Accept-Profile: cms
  • Content-Profile: cms
This ensures queries target the correct database schema.

​
Platform-Specific Handling

The configuration automatically detects Windows (XAMPP) vs Linux and uses the appropriate cURL implementation
Windows/XAMPP:
  • Uses curl.exe via shell_exec()
  • Includes SSL bypass flags: -k --ssl-no-revoke
  • Required for local XAMPP development
Linux/Production:
  • Uses PHP’s native curl_init() and related functions
  • Standard SSL handling for production servers

​
Helper Functions

The config/supabase.php file provides several helper functions:

​
Basic Request

$result = supabase_request('GET', '/clientes?select=*');

​
Service Role Request (Admin)

$result = supabase_request_service('POST', '/auth/v1/admin/users', $userData);

​
Quick GET

$result = supabase_get('/clientes?select=*');

​
Response Format

array(
  'http' => 200,              // HTTP status code
  'body' => '{...}',          // Raw response body
  'json' => array(...),       // Decoded JSON (if applicable)
  'error' => null             // Error message (if any)
)

​
Troubleshooting

​
Connection Issues

If you see SSL certificate errors on Windows/XAMPP, ensure curl.exe is available in your system PATH

​
Authentication Errors

  1. Verify your API keys are correct
  2. Check that the keys have not expired
  3. Ensure RLS policies allow your operations
  4. For admin operations, verify you’re using the service role key

​
Schema Not Found

  1. Verify the cms schema exists in your Supabase database
  2. Check that all tables are in the correct schema
  3. Run the schema creation SQL from docs/supabase_email_builder.sql

​
Next Steps

Security Configuration

Learn about security best practices and session management

Deployment

Deploy your CMS to production servers

Build docs developers (and LLMs) love

Get started for freeTalk to us