Munee’s Heart is its Caching
All files are cached client- as well as server-side. On demand, Munee will check the up-to-dateness of the cache. New versions will only be created if Munee detects more recent changes than the local caches reflect.
In regard to images, Munee offers even more flexibility. It is possible to scale pictures using different criteria and cache them for later use. Besides scaling it is even possible to invoke several of the most popular effect-filters on any given image. If you are still building your online presence and have no pictures available yet, Munee has you covered with its integration of several placeholder-services.
Munee: How it Works
Once installed and with the correct rewrite-rule added, Munee is available server-wide. Its functionality is invoked using several parameters. If you’d want Munee to process a SCSS, output the CSS and minify it, you’d use the following parameter:
<link rel="stylesheet" href="/css/site.scss?minify=true"/>
Parameters can be combined, as this example of a scaled down and filtered image shows:
Combining several CSS-files or LESS/SCSS or mixes even, is achieved, adding all files into one single stylesheet-value like this:
<link rel="stylesheet" href="/css/libs/bootstrap.min.css,/css/site.less"/>
As I already mentioned, it is absolutely commendable to use Munee per rewrite via .htaccess. If you don’t want it that way or are not able to set the preconditions, you can as well add Munee to any given function-call. This could look like so:
<link rel="stylesheet" href="/pfad/zu/munee.php?files=/css/libs/bootstrap.min.css,/css/site.css&minify=true"/>
Munee is freely available under MIT license and can be downloaded from Github. The MIT license allows for commercial use.
Munee: the Target
So far, so good. Lundquist’s PHP tool comes equipped with a nice feature-set. Yet, it is not without alternatives.
The typical small to average website will not see regular or even frequent changes to these files. This usually is job done once or twice a year, at most. Of course, Munee promises to cache server-side and only deliver the cache while nothing changes. This will result in a one-time compilation in most cases, too. Yet, by instinct, I would always prefer the manual method in my own smaller projects.
Speaking of resizing, mainly in responsive designs, there are several better, standards-compliant alternatives. In this field, Munee is no recommendation, simply due to the fact, that it is not able to work fully responsive. In this regard, I see no advantages in the usage of Munee, besides the caching..
Now what’s left? There are use-cases for Munee. I personally operate one. It is a bigger website with five different sections, maintained by five different designers and developers who don’t even know each other.
In this case, an automated accumulation of all the latest efforts via Munee would save a lot of work. Without Munee someone would need to keep track of all changes and care for manually updating the central files. Munee would simply detect the need for changes and process them without anyone even having to think nor communicate about it.
What are your thoughts? Would you try and give Munee a chance in one of your projects?
- Standalone PHP 5.3 Asset Optimisation & Manipulation | Munee
- Munee | Github Repository
- Cody Lundquist | Github Profile
Dieter Petereit is Noupe's Editor-In-Chief and a veteran of the web with over 25 years of experience in the world of IT. As soon as Netscape became available he started to do what already at that time was called webdesign and has carried on ever since. Almost a decade ago he started writing for several online publications, some well, some lesser known. Dieter is a heavy G-Plusser, so why not meet him over there?