Welcome to Minify!
Minify is an HTTP server for JS and CSS assets. It compresses and combines files and serves it with appropriate headers, allowing conditional GET or long-Expires.
The stats above are from a brief walkthrough which shows how easy it is to set up Minify on an existing site. It eliminated 5 HTTP requests and reduced JS/CSS bandwidth by 70%.
Relative URLs in CSS files are rewritten to compensate for being served from a different directory.
Consider instead using a dedicated WordPress plugin for more deep integration and simpler installation. E.g.:
Unfortunately we can't support the WordPress plugins here.
Installation requires PHP 5.3+, SSH access, and access to tools like
composer or the privileges to install them.
cd /path/to/public_html git clone https://github.com/mrclay/minify.git min cd min composer install --no-dev
What this does:
- Inside your DOCUMENT_ROOT directory, we clone this repo. Otherwise you may download and extract the zip file.
- We rename this directory
min. E.g. You will have something like:
cdinto it and run
composer installto install the dependencies.
You can verify that it is working by visiting these two URLs:
* http://example.org/min/?f=min/quick-test.js * http://example.org/min/?f=min/quick-test.css
If your server supports mod_rewrite, this URL should also work:
Configuration & Usage
See the user guide!
Minify also comes with a URI Builder application that can help you write URLs for use with Minify or configure groups of files.
See the cookbook for more advanced options for minification.
More docs are available.
- Install dev deps via Composer:
- Minify is designed for efficiency, but, for very high traffic sites, it will probably serve files slower than your HTTPd due to the CGI overhead of PHP. See the FAQ and CookBook for more info.
- If you combine a lot of CSS, watch out for IE's 4096 selectors-per-file limit, affects IE 6 through 9.
- Minify should work fine with files encoded in UTF-8 or other 8-bit encodings like ISO 8859/Windows-1252. By default Minify appends ";charset=utf-8" to the Content-Type headers it sends.