Keep projects in order
Group applications and sites in one workspace. Choose which server hosts each project and inspect its configuration when you need it.
Create servers, launch projects, and keep your dev workflow organized. Fez brings everything together in one place.
A side project becomes a second project. A quick experiment needs a different stack. Fez gives those projects a consistent home: named servers, repeatable starters and clear commands for the work around your code.
Group applications and sites in one workspace. Choose which server hosts each project and inspect its configuration when you need it.
Pick a supported stack and starter. Fez connects the project, its database and its local address through a single workflow.
Pause projects, retain their data and rehearse restores into fresh destinations. Keep recovery part of your development routine.
Create servers from presets or compatible service selections. Start, stop, inspect and add services with the Fez CLI.
Explore servers →Create static, PHP, Laravel, WordPress and minimal Python WSGI projects. Give each a place in your apps or sites folder.
Choose a starter →Use memorable .test domains through a shared gateway, with local certificate trust and DNS setup.
Set up local access →Add compatible databases, Redis, mail capture and database administration tools. Database-backed starters get their own database credentials.
See supporting services →Enable database queue workers and scheduled tasks for supported Laravel projects, with lifecycle controls and logs.
Run background jobs →Inspect service health, collect project or database backups, and restore into fresh compatible destinations to test recovery.
Plan a recovery →Use the local dashboard to inspect resources, create servers and projects, and run everyday controls. Prefer a terminal? The Fez CLI provides the same underlying workflows, with additional advanced operations. Switch between them as you work.
Available combinations depend on the selected runtime and starter. The guide explains feature requirements and current limits.
Both help you develop locally with Docker. Laradock offers a broad PHP development environment and an extensive service catalog. Fez focuses on a smaller, managed workflow for named servers, project creation and everyday operations within one workspace.
| Consideration | Fez | Laradock |
|---|---|---|
| Main focus | Manage server and project lifecycles through a dedicated CLI. | Configure a PHP development environment from a broad set of Docker services. |
| Service selection | A focused catalog with validated combinations and starter compatibility checks. | An extensive catalog spanning web, databases, queues, search and other development tools. |
| Project organization | Named servers and managed starters, connected by a shared local HTTPS gateway. | Supports a dedicated setup per project or one shared setup for multiple projects. |
| Best fit | You want a consistent workflow for creating projects and handling local operations. | You want broad service choice and flexibility around a PHP development stack. |
| Current scope | Early development, with macOS verified. Wider host testing and public packaging are in progress. | An established project whose site documents Linux, macOS and Windows workflows. |
This comparison describes the projects' focus, not an exhaustive feature audit. Laradock information is based on its official overview. Fez is an independent project.
Fez's public installation packaging is still being prepared. This section will host the release download and final installation instructions when they are available.
Use the source-based setup below. There is no packaged download linked yet.
Check the prerequisites before starting. You need Docker with Compose, Bash, Python 3.9+, Git, curl, OpenSSL and mkcert. macOS is the currently verified environment.
Place the complete Fez source folder in a writable local directory and open a terminal there. On a fresh checkout, copy .env.example to .env and replace its password placeholders. Keep your existing configuration if already installed.
./bin/fez doctor
./bin/fez catalog:checkThe guide explains how to set PATH symlink, which lets you use fez instead of ./bin/fez.
Run ./bin/fez dashboard to open the GUI dashboard. Create a new server and project, then configure local HTTPS.
Note: Initial docker image and framework downloads require internet access.
Fez is ready for hands-on local evaluation. Production deployment and hardening remain thoughts for the future; the current focus is making your local workflow dependable.