Static HTML and supported frontend build output are published as the finished files produced by the repository.
GitHub website hosting
Deploy GitHub projects with the right hosting contract.
GitHub is the connected source route for Host Luma AI Hosting. The Portal deploys supported static projects and a deliberately bounded managed Node 22 web-application path.
What fits
Two deployment types, one connected source.
Supported applications use npm start, the supplied PORT and GET /health through the managed lifecycle.
PHP, WordPress, customer databases, Docker and arbitrary background workers are not part of this product.
GitHub remains the source of code and changes. Host Luma provides deployment state, logs and the publishing/runtime path; it does not replace code review, external services or responsibility for the application.
A practical source workflow
Make the release traceable before it reaches visitors.
Use the repository and branch that contain the tested production project, not a local folder or unrelated monorepo root.
Choose static output or the supported Node application path from the actual runtime requirement.
Read build/deployment logs and, for Node, runtime logs and health state. Fix the source in GitHub rather than making server-side manual changes.
Test the HTTPS preview URL; then attach and verify a custom domain if it is ready for launch.
Delivery and recovery
Domains, CDN and earlier successful versions.
Each application has an HTTPS preview URL. One custom domain per application can be attached and verified through the Portal, with CDN delivery included. Do not call a preview URL a customer domain launch until the domain state is live.
A previous successful Git commit can be queued for a new deployment through the Portal. This preserves the Git-traceable release path; it is not a snapshot, database or environment rollback.
Repository access
Keep access specific to the application.
Private repositories can use per-application deploy-key access once configured and verified. Organisation-owned repositories need the appropriate review and authorisation; they are not presented as an unconditional self-service promise. Contact support before relying on a connection change, repository move or organisation setup.
Read the GitHub connection guide and framework compatibility reference before starting a project that is not clearly static.