title: Clean application deployment when using Composer
body: <p>I have started to use Composer for a new PHP application (it uses a few frameworks and APIs such as Laravel, Smarty etc.) and all is good with it in development.</p>
  
  <p>However, I am not too sure about how do I go about deploying this on a live production server. The sub-directories of the respective modules under the <code>/vendor</code> directory seem to include a lot of stuff which I would not normally include with an app, (such as Demo files, installation readmes, documentation etc.). Is this normal, or is it that the creators of those packages got the wrong idea of how to create a Composer package?</p>
  
  <p>Is there a standard approach to create a clean app deployment that only includes the necessary distribution files and not the rest of the stuff which is not related and should not even be there (even for security reasons)? </p>
  
  <p>I am asking about the most common workflow used, or maybe a specific command or configuration in <code>composer.json</code> I should be looking at to achieve this.</p>