<- Back to projects
Case study
Community Platform

Lightcity Church Enugu — Church Platform

Sole engineer on the NestJS API behind Lightcity Church Enugu's platform, and part of the tech team that built the Next.js site on top of it. The API runs on self-managed VPS infrastructure with PostgreSQL: sermons live in Google Drive and sync automatically, MixLR embeds let out-of-town members join live meetings, and a backoffice (in progress) gives church staff a direct path to upload sermons and create events.

The problem

A growing church needs one place where members can download sermons, share testimonies, and tune in to meetings from out of town — without a media team managing uploads by hand.

Sole engineer on the NestJS API behind Lightcity Church Enugu's platform, and part of the tech team that built the Next.js site on top of it. The API runs on self-managed VPS infrastructure with PostgreSQL: sermons live in Google Drive and sync automatically, MixLR embeds let out-of-town members join live meetings, and a backoffice (in progress) gives church staff a direct path to upload sermons and create events.

The approach

Kept sermons in Google Drive — where the media team already worked — and made the platform sync from it, instead of forcing a new upload workflow.

Automated the sync with scheduled cron jobs: fetch new sermon files, organise them by year and series, and update the database without touching existing records.

Set up the VPS, PostgreSQL, and deployment pipeline directly to keep hosting costs sustainable for a church budget.

Designed the platform around three member needs: downloading sermons, sharing testimonies, and joining meetings remotely via MixLR.

What was used

Next.js for the member-facing website, built with the church tech team.

NestJS for the API, sermon sync jobs, and backoffice endpoints — solo build.

PostgreSQL for sermon, event, and testimony records.

Google Drive API for sermon storage and automated retrieval.

MixLR for live audio streaming of church meetings.

The outcome

Sermon publishing went from a manual multi-step process to an automated sync that runs on a schedule.

Out-of-town members can join live meetings and catch up on sermons from anywhere.

The church owns its infrastructure end-to-end at predictable cost.

Want the engineering version?
I can walk through tradeoffs, data flow, and implementation details in a deeper technical conversation.
Talk about a project