# Web applications

Source : https://webgune.cloud/en-us/docs/applications-web · Mis à jour le 2026-10-27

# Web Applications

When you deploy from GitHub, the auto builder inspects your repository's contents to automatically choose the runtime, and the install and build commands, with no configuration file to write on your end.

## Recognized runtimes

More than 35 frameworks are automatically detected, each with its own start command. The full list, detection signals, and generated commands are on [Supported frameworks](/docs/frameworks-supportes). The main families:

| Family | Examples | Guide |
|---------|----------|-------|
| Fullstack & SSR | Next.js, Nuxt, SvelteKit, Remix, Astro, RedwoodJS, SolidStart, Qwik… | [Supported frameworks](/docs/frameworks-supportes) |
| Node.js backend | Express, Fastify, NestJS, Koa, AdonisJS, FeathersJS, Moleculer… | [Node.js](/docs/web-nodejs) |
| Static frontend | Vite (React / Vue / Svelte), Gatsby, Gulp | [React / Vite](/docs/web-react) |
| Python | Django, FastAPI, Flask | [Python](/docs/web-python) |
| PHP | Laravel, `composer.json` | [PHP](/docs/web-php) |
| Other languages | Go, Ruby on Rails, Rust, Deno | [Go](/docs/web-go) |

If your repository contains a `Dockerfile`, it always takes precedence over automatic detection (see [Docker](/docs/docker)).

## What's common to all stacks

- Your application must read the `PORT` variable and listen on `0.0.0.0`, never on `localhost`.
- Any key, password, or connection URL is configured via [environment variables](/docs/variables-environnement), never hardcoded in the repository.
- A web service's filesystem is ephemeral. Any data that needs to be kept must go through a [database](/docs/bases-de-donnees).
- The start command can always be manually overridden, see [Custom start command](/docs/commande-demarrage).

Each stack guide above details the exact commands run by the auto builder and the environment variables specific to the framework.