mattbaker

This example expects to have d3.min.js and d3.layout.min.js in the same directory as pie.js and pie_serv.js.

Run with node pie_serv.js

seeekr

## !! This snippet has been updated, but not tested in practice. It should work, please check / leave comments in case it doesn't. !! ##

# originally from https://groups.google.com/a/webmproject.org/group/webp-discuss/browse_thread/thread/196ac4ea705688d8
<IfModule mod_rewrite.c>

  # TODO: don't forget to put
  # AddType image/webp .webp
  # in your mods-available/mime.conf
  # (though this is optional because we're setting
  # the mime type manually in the RewriteRule)

killercup

String.prototype.capitalize = ->
  @charAt(0).toUpperCase() + @slice(1)

parse_shit_to_date = (shit) ->
  # shit in form of "2012-05-23"
  parts = shit.match(/(\d+)/g)
  new Date(parts[0], parts[1]-1, parts[2])

jQuery(document).ready ($) ->
  return unless $("body.admin_dashboard").length

kevinelliott

Mac OS X 10.9 Mavericks

Custom recipe to get OS X 10.9 Mavericks running from scratch, setup applications and developer environment. I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install.

Install Software

The software selected is software that is "tried and true" --- software I need after any fresh install. I often install other software not listed here, but is handled in a case-by-case basis.

Install from App Store

roine

/* normal flexbox */
.flexbox .flex-container {
        display: -webkit-flex;
	display: -moz-flex;
	display: -ms-flex;
	display: flex;
}
.flexbox .flex-container.vertical {
	display: -webkit-flex;
	display: -moz-flex;

abteilung

lib {
  parseFunc_RTE {
    nonTypoTagStdWrap.encapsLines { 
      ### entfernt "class=bodytext" aus p-Tags
      addAttributes.P.class =
    }
  }
  stdheader {
    ### entfernt div-Tag um Headlines
    stdWrap.dataWrap = | 

jpetazzo

Unionize: network superpowers for your docker containers

Unionize lets you connect together docker containers in arbitrarily complex scenarios.

Note: I recommend to use https://github.com/jpetazzo/pipework instead.

• pipework is a better name than unionize
• it's hosted on a "real" github repo instead of a small gist :-)

Now if you want Unionize, it's still here. Just check those examples.

AlekseyKorzun

#!/bin/bash

################################################################
# Pre commit hook for git
#
# @package: utilities
# @subpackage: utilities\git
# @author: Aleksey Korzun <al.ko@webfoundation.net>
################################################################

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

konklone

# Basically the nginx configuration I use at konklone.com. 
# I check it using https://www.ssllabs.com/ssltest/analyze.html?d=konklone.com
# 
# To provide feedback, please tweet at @konklone or email eric@konklone.com.
# Comments on gists don't notify the author. 
# 
# Thanks to WubTheCaptain (https://wubthecaptain.eu) for his help and ciphersuites.
# Thanks to Ilya Grigorik (https://www.igvita.com) for constant inspiration.

server {