title: Right way to deploy project and compile assets
body: <p>I save laravel project on <code>github</code> repo and when I have some changes in development I push it to the repo and then deploy it on production server in this way:</p>
  
  <pre><code>1) git pull
  ...
  n) gulp --production
  </code></pre>
  
  <p>After a while the project's <code>css/js</code> start grow in size and compiling the assets start take about 30 sec. So I guess maybe I use not suit deployment process because after <code>git pull</code> command the project still use old assets and only after 30 sec it gets new static. Can you advise me right way how to deploy project to production server without delays.
  I have read a lot about this but couldn't find good solution.</p>
  
  <ul>
  <li>Some people recomment to save compiled assets in repo: it's good because you don't need to install <code>nodejs</code>, <code>gulp</code> on production but there are a lot of minus to do so;</li>
  <li>Also there exists different CI systems like <code>jenkins</code>,<code>circleCI</code>, <code>Travis CI</code> but I didn't use them before and I don't know if they can help to resolve the problem.</li>
  </ul>