symfony/flex

symfony/flex is a Composer plugin that revolutionizes the way Symfony applications are built and managed. Its primary goal is to simplify the management of dependencies (bundles and packages), automate common configuration tasks, and streamline the project setup process.

Here's how symfony/flex works and its key features:

1. Recipes: When you install a new Symfony package or bundle using Composer (e.g., `composer require symfony/twig-bundle`), Flex looks for a corresponding 'recipe'. A recipe is a small set of instructions (often YAML files and PHP files) that tells Flex how to integrate that package into your application. These instructions include:
* Registering bundles in `config/bundles.php`.
* Creating configuration files (e.g., `config/packages/twig.yaml`).
* Adding routing entries.
* Setting up environment variables.
* Sometimes, generating basic directory structures or controller stubs.

2. Recipe Repositories: Recipes are stored in centralized repositories:
* `symfony/recipes`: For official Symfony core bundles.
* `symfony/recipes-contrib`: For popular third-party bundles.
You can also create your own private recipe repositories.

3. Automatic Configuration: Flex eliminates the need for manual configuration steps for most packages. It ensures that services are properly wired, bundles are registered, and configuration files are placed in the correct locations, following Symfony best practices.

4. Directory Structure: Flex enforces a lean and standardized directory structure for new projects created with `symfony/skeleton` or `symfony/website-skeleton`, keeping your application clean and easy to navigate.

5. Environment-Specific Configuration: Recipes often include different configuration options for various environments (e.g., `dev`, `prod`, `test`), which Flex applies appropriately.

6. `composer require` and `composer remove` Enhancement: Flex extends these Composer commands. When you `require` a package, Flex applies its recipe. When you `remove` a package, Flex attempts to undo the changes made by its recipe, keeping your codebase clean.

7. Minimalist Approach: Flex promotes a minimalist approach. When you create a new Symfony project with `symfony/skeleton`, you start with a very barebones application. You then add features and bundles as needed using `composer require`, and Flex integrates them seamlessly.

In essence, symfony/flex acts as an intelligent assistant for your Symfony development, automating repetitive tasks and ensuring consistency across your projects, allowing developers to focus on writing application logic rather than boilerplate configuration.

<?php

// File: config/bundles.php
// This file is automatically managed by symfony/flex.
// When you run 'composer require some-bundle', Flex adds an entry here.
// When you run 'composer remove some-bundle', Flex removes its entry.

return [
    Symfony\Bundle\FrameworkBundle\FrameworkBundle::class => ['all' => true],
    Symfony\Bundle\TwigBundle\TwigBundle::class => ['all' => true],
    // Example of a bundle added by symfony/flex when running 'composer require web-profiler --dev'
    Symfony\Bundle\WebProfilerBundle\WebProfilerBundle::class => ['dev' => true, 'test' => true],
    // Example of a bundle added by symfony/flex when running 'composer require doctrine/orm symfony/doctrine-bundle'
    Doctrine\Bundle\DoctrineBundle\DoctrineBundle::class => ['all' => true],
    Doctrine\Bundle\MigrationsBundle\DoctrineMigrationsBundle::class => ['all' => true],
    // ... other bundles managed by symfony/flex for your application
];