Environment Configuration

This guide explains environment-specific configurations in LamaPress.

Table of Contents

• Overview
• Environment Detection
  • Environment Helper Functions
• WordPress Constants
  • Debug Settings
  • Database Settings
  • Security Settings
• Vite Configuration
  • Development Mode
  • Production Mode
• Environment Files
  • .env File
  • wp-config.php
• Best Practices
  • 1. Use Environment Variables
  • 2. Never Commit Secrets
  • 3. Document Configuration
• Related Documentation

---

Overview

LamaPress supports environment-specific configurations for development, staging, and production environments.

Environment Detection

Environment Helper Functions

Use helper functions to detect environment:

if (llIsLocal()) {
    // Local development code
}

if (llIsStaging()) {
    // Staging-specific code
}

if (llIsProduction()) {
    // Production-specific code
}

Available functions:

• llIsLocal() - Returns true if running on local environment (detects .test domain extension)
• llIsStaging() - Returns true if running on staging environment (detects .dev domain extension)
• llIsProduction() - Returns true if running on production environment (not local or staging)

How it works: Environment detection is based on the server name extension:

• Local: .test (Laravel Herd default)
• Staging: .dev (Laravel Forge staging domains)
• Production: All other domains

WordPress Constants

Debug Settings

Development:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
define('SCRIPT_DEBUG', true);

Production:

define('WP_DEBUG', false);
define('WP_DEBUG_LOG', false);
define('WP_DEBUG_DISPLAY', false);
define('SCRIPT_DEBUG', false);

Database Settings

Configure database per environment:

define('DB_NAME', 'database_name');
define('DB_USER', 'database_user');
define('DB_PASSWORD', 'database_password');
define('DB_HOST', 'database_host');

Security Settings

Security settings:

define('DISALLOW_FILE_EDIT', true);
define('FORCE_SSL_ADMIN', true);

Vite Configuration

Development Mode

Development mode uses Vite dev server:

npm run dev

Features:

• Hot module replacement
• Source maps
• Fast refresh

Production Mode

Production mode builds optimized assets:

npm run build

Features:

• Minified code
• Optimized assets
• Code splitting

Environment Files

.env File

Use .env for sensitive data (not committed):

DB_NAME=database_name
DB_USER=database_user
DB_PASSWORD=database_password

Load in wp-config.php:

if (file_exists(__DIR__ . '/.env')) {
    $env = parse_ini_file(__DIR__ . '/.env');
    foreach ($env as $key => $value) {
        define($key, $value);
    }
}

wp-config.php

Configure WordPress in wp-config.php:

// Database
define('DB_NAME', 'database_name');
define('DB_USER', 'database_user');
define('DB_PASSWORD', 'database_password');
define('DB_HOST', 'localhost');

// Debug
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);

// Security
define('DISALLOW_FILE_EDIT', true);

Best Practices

1. Use Environment Variables

Use environment variables for configuration:

• Database credentials
• API keys
• Environment settings

2. Never Commit Secrets

Never commit sensitive data:

• Add .env to .gitignore
• Use environment variables
• Store secrets securely

3. Document Configuration

Document environment setup:

• Required variables
• Configuration steps
• Environment differences

Related Documentation

• Deployment Overview - Deployment process
• Laravel Forge - Forge setup
• Production Checklist - Pre-deployment checklist

---

Next Steps:

• Review Deployment Overview for deployment
• Check Laravel Forge for Forge setup
• See Production Checklist for checklist