Production Deployment & Infrastructure Guide

This document details the containerization architecture, production hosting on Render, Cloudflare R2 / AWS S3 storage, and operational runbooks for Eniceberny Bakery and Culinary Hub.

1. Production Architecture Overview

The production infrastructure is orchestrated via Docker containers running on Render PaaS backed by managed PostgreSQL:

graph TD
    subgraph Public Web Traffic
        DNS[Cloudflare / Custom Domain enicebakerygh.com] -->|HTTPS 443| LB[Render Load Balancer]
    end
    subgraph Container Services
        LB --> Web[eniceberny-web: Apache + PHP 8.4]
        Web -->|Dispatch Async Jobs| Queue[(Redis / Database Queue)]
        Queue --> Worker[eniceberny-worker: php artisan queue:work]
        Cron[eniceberny-scheduler: php artisan schedule:run] --> Web
    end
    subgraph Data & Storage
        Web --> DB[(Managed PostgreSQL 16)]
        Worker --> DB
        Web --> Storage[Cloudflare R2 / S3 Media Bucket]
    end

2. Multi-Stage Dockerfile Architecture

The production image is built using a clean two-stage Dockerfile to minimize attack surface and image size:

Stage 1 — Node 20 Builder

• Base image: node:20-alpine.
• Copies package.json, package-lock.json, and installs production dependencies.
• Compiles frontend assets with Vite: npm run build.
• Outputs optimized bundles to public/build/.

Stage 2 — PHP 8.4 Apache Runtime

• Base image: php:8.4-apache.
• Installs system libraries and compiled extensions: pdo, pdo_pgsql, pgsql, mbstring, exif, pcntl, bcmath, gd (with FreeType and JPEG support), zip, opcache.
• Configures Apache mod_rewrite, sets document root to /var/www/html/public, and enforces AllowOverride All.
• Injects Composer, installs production PHP dependencies (composer install --no-dev --optimize-autoloader).
• Copies compiled assets from Stage 1.
• Implements healthcheck probe targeting /up.

3. Infrastructure as Code (render.yaml)

The platform includes an automated Render blueprint (render.yaml) defining all components:

4. Environment Variables Directory

The following environment variables must be configured in production:

5. Post-Deployment Runbook

On initial launch or subsequent database schema updates:

1. Execute Database Migrations:

   php artisan migrate --force
   

2. Seed Default Catalog & Operational Sample Data:

   php artisan db:seed --class=DatabaseSeeder --force
   

3. Verify Super Admin Access:

   php artisan auth:ensure-admin
   

4. Optimize Caches:

   php artisan config:cache
   php artisan route:cache
   php artisan view:cache
   

5. Verify Public Probes:
   • Check GET https://enicebakerygh.com/up returns HTTP 200 OK.
   • Verify XML sitemap at GET https://enicebakerygh.com/sitemap.xml.
   • Verify robots rules at GET https://enicebakerygh.com/robots.txt.