mrflip

Tuning Storm+Trident

Tuning a dataflow system is easy:

The First Rule of Dataflow Tuning:
* Ensure each stage is always ready to accept records, and
* Deliver each processed record promptly to its destination

mikhailov

# 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)
#

rchampourlier

# This Rack middleware helps solving the issue with some Rails versions which do not accept
# a '*/*;q=0.6' and their variants 'Accept' request header. This header is particularly used
# by Google Bot, and if Rails doesn't like it, it will return a 500 or 406 error to Google Bot,
# which is not the best way to get your pages indexed.
#
# References:
#   - http://stackoverflow.com/questions/8881756/googlebot-receiving-missing-template-error-for-an-existing-template
#   - https://github.com/rails/rails/issues/4127
#
class GoogleBotAware

sukima

/**
 * Shamlessly copied from http://snipt.net/boriscy/datetime-jquery-formtastic/
 *
 * This did not function with formtastic version 0.9.10
 * I had to move the live("change") event below the initializing part
 * I also had to adjust the jQuery selections as formtastic uses <ol>'s to
 * seperate every select box.
 */
$(document).ready(function() {