Deployment & Hosting

The LMS platform uses a modern, automated deployment pipeline. The infrastructure is split between edge networks for the frontend applications and managed backend infrastructure for our database and serverless functions.

Frontend Applications (Cloudflare Pages)

Both the Admin UI (lms-admin-v2) and the User UI (lms-user-v3) are hosted on Cloudflare Pages.

We utilize a continuous integration and continuous deployment (CI/CD) pipeline directly tied to our version control.

• Automatic Deployments: Cloudflare is connected directly to our GitHub repositories. Whenever a commit is pushed to or merged into the main branch, Cloudflare automatically triggers a new build.
• Build Process: Cloudflare runs npm install followed by our Vite build command, and deploys the optimized static assets to the global edge network.

Warning: Because pushes to the main branch trigger immediate production deployments, all development work should be done on separate feature branches and merged only when tested and approved.

Backend & Services (Supabase)

Our PostgreSQL database, authentication, and file storage are fully managed by Supabase.

Edge Functions

The server-side logic housed in the lms-supabase-function repository is deployed directly to Supabase's global edge network.

Unlike the frontend applications, Edge Functions are currently deployed via the Supabase CLI. To deploy a function to production, an authorized developer must run the following command from the root of the edge function repository:

supabase functions deploy <function-name>

Ensure your local Supabase CLI is authenticated with the production project before running deployment commands.