# Laravel, Symfony & PHP Apps on FlyWP

> Deploy Laravel, Symfony and plain PHP applications from Git on FlyWP, and see how these sites differ from WordPress sites.

Source: https://flywp.com/docs/site/php-apps/

FlyWP can host PHP applications that are not WordPress. You deploy them from a Git repository, and FlyWP builds the site, gives it a database, and runs your code on the server. Use this section when you want to host a Laravel, Symfony, or plain PHP project next to your WordPress sites.

## In this section

- [Create a Site](https://flywp.com/docs/site/php-apps/create-a-site.md): Create a Laravel, Symfony or plain PHP site on FlyWP from a Git repository, add the deploy key, and run the first deployment.
- [Environment (.env)](https://flywp.com/docs/site/php-apps/environment.md): Edit the .env file of a Laravel, Symfony or PHP site from the FlyWP dashboard, and apply the change to the cache and queue workers.
- [Scheduler](https://flywp.com/docs/site/php-apps/laravel-scheduler.md): Run the Laravel task scheduler on a FlyWP site, and change how often it runs from the Laravel page.
- [Queue Workers](https://flywp.com/docs/site/php-apps/laravel-queue-workers.md): Run Laravel queue workers or Horizon on a FlyWP site, and tune connection, queues, processes, tries, timeout and memory.
- [Inertia SSR](https://flywp.com/docs/site/php-apps/laravel-inertia-ssr.md): Run the Inertia server-side rendering server for a Laravel site on FlyWP and make sure your build produces the SSR bundle.
- [Maintenance Mode](https://flywp.com/docs/site/php-apps/laravel-maintenance-mode.md): Put a Laravel site into maintenance mode from the FlyWP dashboard, with an optional secret bypass, and bring it back live.

## Site types

The **PHP / Laravel / Bedrock** option in the site wizard lets you choose an **Application Type**:

| Application Type | What it is |
| --- | --- |
| Laravel | A Laravel application. It also gets the **Laravel** page for the scheduler, queue workers (or Horizon), Inertia SSR, and maintenance mode. |
| PHP | A generic PHP application. |
| Symfony | A Symfony application. |
| Bedrock | A WordPress project built with Bedrock. It is a WordPress site, so it works like other [Git-deployed WordPress sites](https://flywp.com/docs/site/git-deployment/) and is not covered in this section. |

Laravel, PHP, and Symfony sites share the same site menu and the same deployment flow. Only Laravel sites have the extra **Laravel** page.

## How they differ from WordPress sites

- **Git is required.** There is no one-click install. Every site is created from a repository, and you deploy the code from the site page after FlyWP builds the site.
- **Nginx only.** The OpenLiteSpeed server stack is not available for these site types.
- **No WordPress admin.** The wizard asks for a **Site Title** only. There is no WordPress admin user, and WordPress tools do not apply.
- **Web directory is `/public`** by default. You can change it in the wizard.
- **PHP 8.4** is preselected for a new site. You can pick any version from 7.4 to 8.5 in the wizard.
- **A `.env` file instead of `wp-config.php`.** You edit it from the **Environment** page. See [Environment variables](https://flywp.com/docs/site/php-apps/environment/).
- **Database-only backups.** Backups cover the site's database. Your code comes back from your repository, so FlyWP does not archive the files.

These sites do not include the file manager, site-specific SFTP, site cloning or transfers, static site copies, or the WordPress-specific tools (updates, security scans, magic login, and email setup).

Available tools include deployment, SSL, the Nginx config editor, the environment editor, the uptime monitor, Page Speed Insights, redirect rules, backups (database only), PHP settings, and logs. Laravel and Symfony sites show their framework log as **Application Log** under [Logs](https://flywp.com/docs/site/monitoring-and-logs/logs/).

Trial servers only offer WordPress site types, so you need a regular server to create these sites.

## Where to start

1. [Create a Laravel, Symfony or PHP site](https://flywp.com/docs/site/php-apps/create-a-site/).
2. Edit the [environment variables](https://flywp.com/docs/site/php-apps/environment/) the app needs.
3. Deploy the code. Later pushes can deploy automatically if you enabled **Push to deploy**.
4. For Laravel, set up the [scheduler](https://flywp.com/docs/site/php-apps/laravel-scheduler/), [queue workers](https://flywp.com/docs/site/php-apps/laravel-queue-workers/), [Inertia SSR](https://flywp.com/docs/site/php-apps/laravel-inertia-ssr/), and [maintenance mode](https://flywp.com/docs/site/php-apps/laravel-maintenance-mode/).

## Related guides

- [Git Provider Connections](https://flywp.com/docs/deployment/git-provider-connections/)
- [Deploy from Git to FlyWP Servers](https://flywp.com/docs/site/git-deployment/)
- [Next.js, Nuxt & Astro sites](https://flywp.com/docs/site/nodejs-sites/)
