MicroSymfony is a Symfony 7.2 application skeleton on steroids, ready to use.
I have made a long blog post explaining the philosophy behind and how to use it:
If you want to use the last Symfony 6.4 LTS version in your composer.json
file, replace all occurrences of 7.1
with 6.4
and run composer up
.
- About
- Demos
- Quick-start
- Requirements
- Stack
- Features
- Feature branches
- Notes
- Other good practices
- References
- Contributing
- Security
- Credits
- License
Because a live demo is always better than all explanations:
- Live demo at https://microsymfony.ovh
- Live demo powered by FrankenPHP at https://frankenphp.microsymfony.ovh
You must have the Symfony binary and composer installed locally.
To create a new project from the GitHub template, run:
composer create-project strangebuzz/microsymfony && cd microsymfony
Then start the PHP server with make:
make start
Or with Castor:
castor start
Open https://127.0.0.1:8000 (considering your 8000 port is free) and enjoy! π
We can also use FrankenPHP to run MicroSymfony. You must have Docker installed locally.
Create a new project from the GitHub template, run:
docker run --rm -it -v $PWD:/app composer:latest create-project strangebuzz/microsymfony && cd microsymfony
Install the FrankenPHP Symfony runtime:
docker run --rm -it -v $PWD:/app composer:latest require runtime/frankenphp-symfony
Then run:
docker run \
-e FRANKENPHP_CONFIG="worker ./public/index.php" \
-e APP_RUNTIME=Runtime\\FrankenPhpSymfony\\Runtime \
-v $PWD:/app \
-p 80:80 -p 443:443 \
-d \
dunglas/frankenphp
Open https://localhost and enjoy! π
PS: On Windows, replace $PWD
with "%cd%"
.
You can also directly use the FrankenPHP branch.
- PHP 8.2 (also works with PHP 8.3 and PHP 8.4)
- The Symfony CLI
- The Xdebug PHP extension if you want to run the code coverage report
- Castor task runner if you don't want to use Make and its Makefile
- Symfony 7.2
- Twig 3.8
- Hotwired stimulus 3.2 and Turbo 8.0
- PHPUnit 11.0
- The Pico CSS framework
MicroSymfony ships these features, ready to use:
- Two task runners
- Static analysis with PHPStan 2
- Coding standards with php-cs-fixer
- Tests (demo)
- Code coverage at 100% (configurable threshold)
- GitHub CI (actions)
- Asset mapper+Stimulus (documentation)
- A custom error template
Feature branches
are not merged in the main branch but are used to test the integration of a new
vendor library or make a POC.
For example, have you ever dreamed of testing Eloquent,
the Laravel ORM, on a Symfony project?
Then clone the eloquent
branch, and run composer install && make load-fixtures
.
These Β« database Β» branches aim to display a list of records from a SQLite database.
- Taskfile (PR, branch, rebased on 2024-11-17)
- TwigStan (PR, branch, rebased on 2024-11-17)
- Twig-CS-Fixer (PR, branch, rebased on 2024-11-21)
One will rebase those branches regularly so they are always up to date.
Turbo forms are disabled in assets/app.js.
To enable the feature for a given form, add the data-turbo="true"
attribute to it.
Or change the parameter Turbo.setFormMode
to on
to activate the feature globally.
In both cases, your controller code has to be modified accordingly.
If you install a new Symfony library, the flex recipes can add YAML files to your
project.
These YAML files are loaded, but you can convert them to PHP like the other configuration
files.
For example, to convert the messenger
YAML configuration to PHP with Simplify,
run:
vendor/bin/config-transformer convert config/packages/messenger.yaml
- Using PHP configuration files instead of YAML (source)
- Using strict types in all PHP files (source)
- Using the ADR pattern in an action controller (source) (doc)
- The composer.json file is normalized with ergebnis/composer-normalize
- Use of the composer bin plugin to install and run php-cs-fixer
- How to Switch from YAML Configs to PHP Today with Symplify (tomasvotruba.com)
- PHPStan 2.0 Released With Level 10 and Elephpants! (phpstan.org)
- A better ADR pattern for your Symfony controllers (strangebuzz.com)
- My Taskfile configuration for Symfony (jmsche.fr)
- You should be using PHPStans bleeding edge (backendtea.com)
- A Good Naming Convention for Routes, Controllers and Templates? (jolicode.com)
- Front-end application development, Symfony-style(s) (dunglas.dev)
- Automated Test Coverage Checks with Travis, PHPUnit for Github Pull Requests (ocramius.github.io)
- Installing and using php-cs-fixer (strangebuzz.com)
- Castor, a journey across the sea of task runners (jolicode.com)
- Initializing your Symfony project with solid foundations (strangebuzz.com)
- Organizing your Symfony project tests (strangebuzz.com)
- What are your Symfony best practices? (strangebuzz.com)
- Setting a CI/CD workflow for a Symfony project thanks to the GitHub actions (strangebuzz.com)
- The Symfony Framework Best Practices (symfony.com)
Please see CONTRIBUTING and CODE_OF_CONDUCT for details.
Please see SECURITY for details.
The MIT License (MIT). Please see License File for more information.