Duplicate executions

[kingcrunch]

Some tasks do stuff, that is already (usually) covered by composer scripthandlers and shouldn't run by default.

See also: https://github.com/symfony/symfony-standard/blob/master/composer.json

• cache warm up

  {
      "scripts": {
          "post-install-cmd": [
              "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache"
          ],
          "post-update-cmd": [
              "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache"
          ]
      },
      "extra": {
          "symfony-cache-warmup": "true"
      }
  }
  

  in composer.json

• built-bootstrap

  {
      "scripts": {
          "post-install-cmd": [
              "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::buildBootstrap"
          ],
          "post-update-cmd": [
              "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::buildBootstrap"
          ]
      }
  }
  

• install assets

  {
      "scripts": {
          "post-install-cmd": [
              "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installAssets"
          ],
          "post-update-cmd": [
              "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installAssets"
          ]
      }
  }
  

I am not entirely sure, if it's useful to drop them at completely (they are not too complicated to write in ones Capfile, or deploy.rb themself), but at least it should be possible to avoid them.

Update: After I played around with different scenarios, I must admit, that it looks more useful to remove the corresponding script handlers from the dependency resolver (composer), but let the deployment tool (capistrano) do the job

[peterjmit]

This is related to #1

I feel like it makes it easier to manage if the deployment tool handle the steps that the app needs to be ready, rather than the dependency resolver (this is why we have a build_bootstrap task, and composer is run with --no-scripts)

[kingcrunch]

@peterjmit I partly agree. I see, that it is better to let the deployment tool handle the mentioned stuff. However, you cannot assure, that not other tasks are handled via composers script handlers, so --no-scripts is actually not a good idea (and btw: composer doesn't use the --no-scripts-flag anymore).

So I for myself removed most script handlers except the ParameterHandlers-handler and I am fine with it (except, that it doesn't generate the assets, see #10 😉 ). So at the end it is somehow up to you if you give users the possibility. Or of course you can await a PR about that 😄

[blaugueux]

@kingcrunch now #17 have been merged you can close this issue :)