This runs provides an .optim job for dragonfly and also adds the .optim job into .thumb
This requires you have the 'image_optim' gem and it's dependencies.
| # Nginx+Unicorn best-practices congifuration guide. Heartbleed fixed. | |
| # We use latest stable nginx with fresh **openssl**, **zlib** and **pcre** dependencies. | |
| # Some extra handy modules to use: --with-http_stub_status_module --with-http_gzip_static_module | |
| # | |
| # Deployment structure | |
| # | |
| # SERVER: | |
| # /etc/init.d/nginx (1. nginx) | |
| # /home/app/public_html/app_production/current (Capistrano directory) | |
| # |
This runs provides an .optim job for dragonfly and also adds the .optim job into .thumb
This requires you have the 'image_optim' gem and it's dependencies.
| <script type="text/javascript"> | |
| // | |
| // Requires Modernizr, jquery, and columnizer.js | |
| // http://modernizr.com (Requires a production version, demo doesn't include yep/nope) | |
| // http://jquery.com | |
| // http://welcome.totheinter.net/columnizer-jquery-plugin/ | |
| // | |
| // Replace [url], [target], and [options] w/ your specific needs | |
| // |
| @media only screen and (min-width: 320px) { | |
| /* Small screen, non-retina */ | |
| } | |
| @media | |
| only screen and (-webkit-min-device-pixel-ratio: 2) and (min-width: 320px), | |
| only screen and ( min--moz-device-pixel-ratio: 2) and (min-width: 320px), | |
| only screen and ( -o-min-device-pixel-ratio: 2/1) and (min-width: 320px), |
sudo apt-get install ghostscriptiapi.h etc) which are required but don't come with the default Ghostscript package: sudo apt-get install libgs-devsudo apt-get install gs-espsudo apt-get --purge remove imagemagickcd ImageMagick-xx./configure --with-gslib=yes [and what else you need]gslib yes yes and not gslib yes nomakemake installconvert -list configure | grep DELEGATES => DELEGATES bzlib djvu freetype gs jpeg jng jp2 lcms png tiff x11 xml zlib| @include handhelds { | |
| table.responsive { | |
| width: 100%; | |
| thead { | |
| display: none; | |
| } | |
| tr { | |
| display: block; | |
| } | |
| td, th { |
I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.
From Require.js - Why AMD:
The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"
I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.
| # Stick this in lib/tasks/assets.rake or similar | |
| # | |
| # A bug was introduced in rails in 7f1a666d causing the whole application cache | |
| # to be cleared everytime a precompile is run, but it is not neccesary and just | |
| # slows down precompiling. | |
| # | |
| # Secondary consequences are the clearing of the whole cache, which if using | |
| # the default file cache could cause an application level performance hit. | |
| # | |
| # This is already fixed in sprockets-rails for rails 4, but we patch here for |