Replies: 1 comment 1 reply
-
I've worked around this by manually building CSS separately. Is there a way to separate AssetPack's processing that "builds" the files vs one that simply uses the built files, so that a separate "build assets" command can be run by developers, versus the application itself parsing assetpack.db and simply using the existing files? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is it possible to use the AssetPack plugin and build Sass (.scss) files into appropriate .css files on a development server, update the caches in a git repo and then run the Mojolicious application on a server without Sass?
In other words, the server should not try and rebuild the CSS files. It should just trust what's in the cache.
Beta Was this translation helpful? Give feedback.
All reactions