But Assetic supports a number of other filters. This means you can: Also, re-run the assets: In fact, Assetic has a long list of available filters. It also allows you to maintain the files more easily by splitting them into manageable parts.
Instead, each time you use your app in the prod environment and therefore, each time you deployyou should run the following task: For details on using Assetic in the cssrewrite assetic environment, see Dumping Asset Files. The cssrewrite filter dynamically changes the url so that things still work.
The great advantage of using Assetic to invoke these libraries as opposed to using them directly is that instead of having to run them manually after you work on the files, Assetic will take care of this for you and remove this step altogether from your development and deployment processes.
See the note in the above section for details. Cssrewrite assetic has the strangest syntax, but should include the path to our 3 CSS files, a filter called cssrewrite, and an actual link tag.
If you cssrewrite assetic back at the stylesheets tag, you can see that we do have one filter called cssrewrite. This is on purpose - letting Symfony generate these files dynamically in a production environment is just too slow. You can use either, except that there is a known issue that causes the cssrewrite filter to fail when using the AcmeFooBundle syntax for CSS Stylesheets.
This kind of dynamic serving of processed assets is great because it means that you can immediately see the new state of any asset files you change.
To fix this, make sure to use the cssrewrite filter with your stylesheets tag. Huh, the paths are a bit different! This is on purpose. Let me know if that helps! You can also use Assetic to combine third party assets, such as jQuery, with your own into a single file: There are also tools like RequireJS, really the list goes on and on.
Now view the source. For example, Assetic has a less filter that processes your less files into CSS before returning them. This is done from the template and is relative to the public document root: This parses your CSS files and corrects the paths internally to reflect the new location.
This filter is less of a cool feature and more of a necessity. Fortunately, Assetic provides a way to dump your assets to real files, instead of being generated dynamically.
The files do not need to be stored where they are served from and can be drawn from various sources such as from within a bundle. This has no disadvantage you can see your changes immediatelyexcept that assets can load noticeably slow.
The actual rendered tag might simply look like: This will cause problems with CSS files that reference images by their relative path. But the magic is coming First, tell Symfony to stop trying to process these files dynamically.I am using bower to manage many common assets and have run into an issue.
I am trying to use mint-body.com to have a rotating carousel and I'm running it all through Assetic to combine and minify assets. cssrewrite is used to correct relative paths into the CSS since the Assetic serves them from different URLs than the intial sources exist.
uglifyjs2 is used to minify. Can you provide more details about how you're using Assetic and what you expect it to do?
Also, can you debug to see if the target path in the CssRewriteFilter includes _controller/? The cssrewrite filter produces wrong urls after the rewrite: i have my bundle which contains mint-body.com file located in Resources/public/less/mint-body.com I also have.