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
Site types
Section titled “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 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
Section titled “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
/publicby 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
.envfile instead ofwp-config.php. You edit it from the Environment page. See Environment variables. - 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.
Trial servers only offer WordPress site types, so you need a regular server to create these sites.
Where to start
Section titled “Where to start”- Create a Laravel, Symfony or PHP site.
- Edit the environment variables the app needs.
- Deploy the code. Later pushes can deploy automatically if you enabled Push to deploy.
- For Laravel, set up the scheduler, queue workers, Inertia SSR, and maintenance mode.
Related guides
Section titled “Related guides”Still stuck? How can we help?
View as Markdown