Disabling specific recipes for custom skeleton

[alexander-schranz]

We in sulu have a custom skeleton where the some bundles are preconfigured for the way we need them. How can I disabled that it will execute recipes for this exist installed dependencies?

[nicolas-grekas]

You can commit a symfony.lock with the right content.

[alexander-schranz]

@nicolas-grekas but the dependencies version are related to the php version so providing a symfony.lock will force to provide also a composer.lock and force that user to use the same php version as this file are created for or?

Or could i just create a symfony.lock without versions to avoid this recipes? e.g.:

{
    "symfony/framework-bundle": {},
    "doctrine/doctrine-bundle": {}
}

[dunglas]

In API Platform, we use a shell script editing the files generated by the recipes after their installation. As we provide a Docker setup, composer.lock and symfony.lock in our skeleton, we don't have the problem regarding the PHP version. However, this idea could maybe be generalized: you can maybe provide a Composer script (in your skeleton) that will be executed after Flex and will tweak the files generated by the recipes?

[esserj]

Yeah, we also have similar issues, where we have created packages and these packages have a set of bundles together with specific configuration to their use case, like a package with multi-lingual support one that hes config for none multi-lingual support, etc... this allows us to craft recipes without having to use skeleton applications, unfortunately at the moment we always have to force install their recipes because flex first installs the bundle's recipes and only then the package, preventing of from predefining config for bundles in the package, this might be by design though, but would be a great addition to flex if we could have 3 packages all with the same bundles, but with different configurations. The main raison skeletons dont work is because you may want to combine 2 packages like this and you can only do create project once

[nicolas-grekas]

Or could i just create a symfony.lock without versions to avoid this recipes? e.g.:

We could support something like this yes: entries in symfony.lock that would tell "always skip recipes for this package".

Anyone up to give it a try?

[nicolas-grekas]

I'm closing here because I think #803 provides a solution for that: define your own flex endpoint.