This is not a problem. Once you finished working an iteration/feature you generally want to deploy on staging for client tests or into production.
That server should not regenerate scss/less files into css for every pageview. For that purpose I use scripts to minify and compress javascript, less/scss and my html point to them. Now about CDN. In that case I would push my assets - css, - images, - minified javascripts, - minified and combined original libraries, and - my own js separated by contexts On my own CDN. I would also suggest you generate a few different hostnames so you can point your addresses (and multiply the simultaneous assets download). This, of course cannot be done with a vanilla version of bootstrap a public CDN offers. Because they will not host your own files. The goal of a CDN is to give the redundancy and speed up download time. You should optimize your assets to have the least possible to download. Hope this was helpful. Renoir -- You received this message because you are subscribed to the Google Groups "twitter-bootstrap" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
