tbranyen

//
// README:
// - Listens for PUSH events
// - Fetches the ref pushed via the given remote
// - Sets the repositories HEAD to latest ref
// - Checks out the new HEAD (--force)
// - Install dependencies from package.json
// - Calls `npm run reload` (My app uses this)
// - Calls `nginx -s reload` (My app also uses this)
//

lierdakil

{-# LANGUAGE OverloadedStrings #-}
import Text.Pandoc.JSON
import System.Directory
import System.FilePath ((</>))
import qualified Data.Hash.MD5 as MD5
import qualified Data.Text as T
import System.IO.Temp
import System.Process
import Control.Monad (unless)

wincent

2015-01-29 Unofficial Relay FAQ

Compilation of questions and answers about Relay from React.js Conf.

Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.

What is Relay?

Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).

christofluethi

brew update
brew link yasm
brew link x264
brew link lame
brew link xvid

brew install ffmpeg

ffmpeg wiki: 
https://trac.ffmpeg.org/wiki/Encode/MP3

max-mapper

Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward discussions repo

io.js - what you need to know

• io is a fork of node v0.12 (the next stable version of node.js, currently unreleased)
• io.js will be totally compatible with node.js
• the people who created io.js are node core contributors who have different ideas on how to run the project
• it is not a zero-sum game. many core contributors will help maintain both node.js and io.js

kevinelliott

Mac OS X 10.10 Yosemite

Custom recipe to get OS X 10.10 Yosemite 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. On average, I reinstall each computer from scratch every 6 months, and I do not perform upgrades between distros.

This keeps the system performing at top speeds, clean of trojans, spyware, and ensures that I maintain good organizational practices for my content and backups. I highly recommend this.

You are encouraged to fork this and modify it to your heart's content to match your own needs.

Install Software

dperini

/*
 * How to detect which element is the scrolling element in charge of scrolling the viewport:
 *
 * - in Quirks mode the scrolling element is the "body"
 * - in Standard mode the scrolling element is the "documentElement"
 *
 * webkit based browsers always use the "body" element, disrespectful of the specifications:
 *
 *  http://dev.w3.org/csswg/cssom-view/#dom-element-scrolltop
 *

unicornist

//demo: http://jsfiddle.net/heZ4z/

if (document.addEventListener) { // standard

  document.addEventListener('click', function onclick(e) {
    var r;
    if (document.caretRangeFromPoint) { // standard (WebKit)
      r = document.caretRangeFromPoint(e.pageX, e.pageY);
    } else if (e.rangeParent) { // Mozilla
      r = document.createRange();

nhunzaker

var _        = require('underscore');
var Backbone = require('backbone');
var cheerio  = require('cheerio');
var request  = require('request');

Backbone.ajax = function(options) {
	options.json = true;

	return request(options, function(error, result) {
		if (error) {

sebmarkbage

You're probably getting this warning because you're accessing methods on a component before it gets mounted. This will be soon be an unsupported use case.

The component that gets created by invoking the convenience constructor MyComponent(props, children) or using the JSX syntax <MyComponent /> is not guaranteed to be the instance that actually gets mounted. It's a description of what the actual mounted instance should look like.

Anti-pattern:

The component also doesn't have access to state or other important information such as the final props. As a consequence you shouldn't be calling custom methods on this object.

var MyComponent = React.createClass({