How to deploy a web app from GitHub on MoodLensAI
Last reviewed September 13, 2026
Connect your GitHub account, pick a repository and branch, choose the matching runtime preset, then trigger the deploy from your dashboard. MoodLensAI resolves your branch to a specific commit, builds it and runs it on a managed server with HTTPS — you decide when each deploy happens; nothing redeploys automatically on push.
Prerequisites
- A GitHub account with the repository you want to deploy (public or private).
- A MoodLensAI account.
- An app built with a supported framework: Laravel, Next.js, React (static), Vue (static), Django, FastAPI, or Node.js (Express or NestJS).
Steps
-
1
Connect your GitHub account
From your dashboard, start the GitHub connect flow. You are redirected to GitHub to authorize MoodLensAI, then back to your dashboard once it succeeds.
-
2
Choose the repository and branch
MoodLensAI lists the repositories your account owns, collaborates on, or belongs to through an organization. Pick the one you want to deploy and the branch to track.
-
3
Confirm the runtime preset
MoodLensAI detects your framework from file signals in the repository, never by running your code, and preselects the matching preset. Change it if the detection is wrong. MoodLensAI resolves your chosen branch to its current commit, so the exact code you are about to deploy is pinned before anything builds.
-
4
Trigger the deploy
Deploying is a deliberate action you take from your dashboard — MoodLensAI does not watch your repository and redeploy automatically on every push. When you are ready, start the deploy and MoodLensAI downloads that commit's source archive, builds it and runs it.
-
5
Wait for the health check
Before your app goes live, MoodLensAI runs an automated health check against it. It only becomes active once that check passes, so a broken build never silently replaces a working deployment.
Common failures
Build fails on a missing environment variable
Frameworks like Laravel need certain variables — a database connection, an app key — before they will boot. See "Environment variables explained".
Wrong runtime preset selected
Picking a preset that does not match your actual framework usually fails at build or start time. Match the preset to what your app actually is.
Health check fails after a successful build
Usually means the app is not listening on the expected port, or crashes on boot — check your framework's start command and required configuration.
Repository or branch not found
If you renamed the branch, transferred the repository, or lost access to it on GitHub, reselect it from your dashboard.
Security notes
Connecting your account creates an encrypted, scoped GitHub access token, never shown to you again after the initial connection, used only to list your repositories and read the exact commit you deploy. MoodLensAI never pushes anything back to your repository.