Application runtime
Multiple PHP versions per project
Framework solution
Laravel local development environment with FlyEnv
Build and run Laravel with PHP, databases, Redis, local domains, and HTTPS in one native workspace.
What a Laravel project needs locally
A practical Laravel application consists of several components. FlyEnv provides and manages them for you.
Dependencies
Composer
Built-in Composer, easy to use
Database
MySQL or PostgreSQL
Both supported, switch per project
Cache & queues
Start when needed
Web server
Flexible web server support
Frontend assets
Modern frontend toolchain
Scheduled tasks
Manage Laravel scheduler
Local HTTPS
Real local domain with HTTPS
A real Laravel development stack in FlyEnv
A typical Laravel project running on FlyEnv, with a clear architecture and all the services you need.
Project-level PHP version
Use the PHP version required by each Laravel project.
Local domain + HTTPS
Access your project with a trusted certificate.
One-click startup group
Start all required services together and get to work.
Queue workers / scheduler
Run workers and the Laravel scheduler easily.
What it looks like in FlyEnv
A Laravel project with its services and runtime managed in one workspace.
Project-level runtime
Choose the PHP-FPM version required by this Laravel project.
Laravel project group
Keep Nginx, PHP-FPM, MySQL, and Redis in one controlled startup order.
Managed service stack
See the core Laravel services together in one FlyEnv view.
Repeatable startup
Start the project’s Startup Group whenever you return to the app.
Why use FlyEnv for Laravel development
A more predictable and enjoyable local development experience for Laravel.
Use different PHP versions per project
Keep Laravel projects on the versions they require without changing a global runtime.
Laravel 8 → PHP 7.4 · Laravel 11 → PHP 8.2 · Laravel 12 → PHP 8.3+
Run the full stack with one click
Start PHP, the database, Redis, the web server, and more from one Startup Group.
PHP + Nginx + MySQL + Redis → Startup Group
Choose MySQL or PostgreSQL
Use the database that matches the project instead of adapting the project to the tool.
Add Redis only when needed
Enable cache, sessions, or queues without carrying an unused service everywhere.
Use a real local domain and HTTPS
Test cookies, OAuth callbacks, webhooks, and secure browser features locally.
https://shop.test
Run scheduler and queue workers
Keep background work close to the Laravel application during development.
New project or existing project
FlyEnv works for new Laravel apps and projects you already have.
Start a new Laravel project
- 1Open PHP → New Project.
- 2Choose Laravel template, framework version, PHP version, and Composer version.
- 3FlyEnv runs the Composer creation command and shows the terminal output.
- 4Create the matching local site in one click.
- 5Open the new project with a local domain and HTTPS.
Run an existing Laravel project
- 1Import or open the existing Laravel project.
- 2Set the required PHP version.
- 3Configure the database, Redis, and other services if needed.
- 4Add the local site and choose the public directory.
- 5Start the project’s Startup Group and open the site.
Compare local Laravel approaches
Different tools, different approaches. Here is how they compare for local Laravel development.
| Feature | Manual local setup | Container workflow | FlyEnv |
|---|---|---|---|
| Environment model | Single PHP process | Docker containers | Full local environment |
| Database environment | Local or external | Containers | MySQL or PostgreSQL modules |
| Redis support | Manual setup | Container service | Built-in, on demand |
| Local domains | Manual setup | Project-dependent | Managed local sites |
| Multi-stack development | Manual switching | Docker Compose | Project-level runtimes and services |
Laravel FAQ
Common questions about using FlyEnv for Laravel development.
Can I use different PHP versions for different Laravel projects?
Yes. FlyEnv manages multiple PHP versions and lets each project or local site use the version it requires.
Can I use MySQL or PostgreSQL with Laravel?
Yes. Choose the database module that matches the project and start it alongside the Laravel application.
Does FlyEnv support Redis queues?
Yes. Start Redis when the application uses cache, sessions, Horizon, or queue workers, then keep it in the project’s Startup Group.
Can I use a .test domain with HTTPS?
Yes. Create a local site with a readable domain and use FlyEnv’s trusted local HTTPS support.
Can I manage multiple Laravel projects?
Yes. Each project can keep its own PHP version, local site, database choice, Redis usage, and supporting services.
Does FlyEnv replace the Laravel installation guide?
No. The Solution page explains the environment and workflow; the Laravel Guide covers the detailed setup steps and configuration.
Related solutions
Ready to build Laravel locally?
Run PHP, databases, Redis, local domains, and HTTPS in one workspace.
Have questions using FlyEnv?