SBCC Management System

[ AT_A_GLANCE ]

• PROBLEM: Outgoing SMTP ports were blocked on Railway, breaking attendance alerts and volunteer schedules in production; macOS SSL verification and complex ministry-module dependencies also broke local schema migrations (FieldDoesNotExist).
• SYSTEM: Django 5.1 + DRF API → React 19 (Vite) + TailwindCSS/Flowbite UI → PostgreSQL (Neon) on Railway, containerized with Docker, with Brevo handling email delivery.
• APPROACH: Replaced SMTP with a BrevoEmailBackend over Brevo’s HTTP API, added a non-verifying-SSL dev CustomEmailBackend for macOS, manually reordered Django migration operations to resolve field dependency conflicts, and added a check_frequent_absences background service that drives in-app + email pastoral-care follow-ups.
• RESULT: Church administration is fully digitized and operational on the linked demo, with reliable email delivery in cloud environments and resilient internal attendance monitoring.

[ SITREP ]

• INCIDENT TRIGGER: The system was engineered to centralize and digitize church operations—including membership, attendance, events, and inventory—that were previously handled through inefficient manual documentation.
• OBJECTIVE: Improve operational record accuracy, automate volunteer scheduling, and provide administrators with real-time analytics and printable reports to permanently streamline church management.

[ APPLICATION_CONTEXT ]

The SBCC (Santa Cruz Bible Christian Church) Management System is a full-stack, cloud-hosted administrative dashboard. Functioning as a centralized hub, it gives church leadership a unified interface to track dynamic membership data, analyze weekly attendance patterns, and autonomously schedule volunteers.

[ SYSTEM_TOPOLOGY ]

• API_GATEWAY: Python 3.12, Django 5.1, and Django REST Framework (DRF) enforcing robust backend endpoints.
• CLIENT_NODE: React 19 (Vite), TailwindCSS, and Flowbite React to construct a highly responsive modern UI.
• DATA_STORE: PostgreSQL (via Neon) providing stable cloud production data.
• INFRA_LAYER: Docker for containerization, Railway for the primary deployment footprint, and Brevo (Sendinblue) acting as the automated email notification conduit.

[ FAILURE_ANALYSIS // NETWORK_BLOCKAGE_AND_MIGRATIONS ]

• DETECTED_ANOMALY: Critical attendance alerts and volunteer schedules failed to execute in production environments. Developers also faced local schema update failures due to SSL and dependency conflicts.
• ROOT_CAUSE: Outgoing SMTP ports were aggressively blocked by cloud hosting platforms (like Railway). Additionally, macOS-specific SSL certificate verification errors broke development workflows, and complex dependencies in the ministries module triggered FieldDoesNotExist errors during database schema migrations.

[ MITIGATION_PROTOCOL ]

1. HTTP_TRANSPORT_BYPASS: Developed a specialized BrevoEmailBackend that bypasses heavily restricted SMTP ports by strictly utilizing Brevo’s HTTP API, ensuring highly reliable delivery in cloud environments.
2. SSL_WORKAROUND: Implemented a CustomEmailBackend for development environments utilizing a non-verifying SSL context to circumvent rigid macOS certificate constraints.
3. SURGICAL_MIGRATIONS: Manually intercepted and reordered Django migration operations to resolve core field dependency conflicts, enabling smooth schema transitions without panicking the database.
4. TELEMETRY_MONITORING: Engineered a robust check_frequent_absences background service that dynamically calculates attendance rates and triggers both in-app notifications and “Pastoral Care” emails to re-engage missing members.

RESULT: The church administration system is fully digitized and operational. Administrators now command a reliable, cloud-hosted platform fortified by resilient internal monitoring and guaranteed notification delivery.