xat

  var last = function(fn, l) {
    return function() {
      var args = Array.prototype.slice.call(arguments);
      args.push(l);
      return l = fn.apply(null, args);
    };
  };

Unitech

  app.all('*', function (req, res, next) {

    res.header("Access-Control-Allow-Origin", req.headers.origin);
    res.header("Access-Control-Allow-Credentials", true);
    res.header('Access-Control-Allow-Methods', 'GET,PUT,POST,DELETE,OPTIONS');
    res.header("Access-Control-Allow-Headers", "X-Requested-With, Content-Type, Authorization, Content-Length");

    if (req.method == 'OPTIONS') {
      return res.send(200);
    }

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

LeCoupa

/* *******************************************************************************************
 * THE UPDATED VERSION IS AVAILABLE AT
 * https://github.com/LeCoupa/awesome-cheatsheets
 * ******************************************************************************************* */


// 0. Synopsis.
// http://nodejs.org/api/synopsis.html

agendor

This tutorial uses the "Sample hapi.js REST API" project.

Take a look at: https://github.com/agendor/sample-hapi-rest-api/

##Topics

• Introduction
• Installing Node.js
• Installing MySQL
• Setting-up the project

LeCoupa

# Note: if you want to run multiple meteor apps on the same server,
# make sure to define a separate port for each.

# Upstreams
upstream gentlenode {  
    server 127.0.0.1:58080;
}

# HTTP Server
server {  

rnewson

# Bind SSL port with PFS-enabling cipher suite
bind :443 ssl crt path_to_certificate no-tls-tickets ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA384:AES128-SHA256:AES128-SHA:AES256-SHA256:AES256-SHA:!MD5:!aNULL:!DH:!RC4

# Distinguish between secure and insecure requests
acl secure dst_port eq 443

# Mark all cookies as secure if sent over SSL
rsprep ^Set-Cookie:\ (.*) Set-Cookie:\ \1;\ Secure if secure

# Add the HSTS header with a 1 year max-age

pid

• Github
• Intro to the React Framework
• Why did we build React?
• Thinking in React
• Another Level of Indirection
• Video: React: Rethinking best practices by Pete Hunt
• Video: Intro to React Screencast by Pete Hunt
• Video: Super VanJS 2013 by Steven Luscher
• Video: Stoyan Stefanov - Introduction to React
• The Future of JavaScript MVC Frameworks

0xabad1dea

Sorry, RSA, I'm just not buying it

I want to be extremely clear about three things. First, this is my personal opinion – insert full standard disclaimer. Second, this is not a condemnation of everyone at RSA, present and past. I assume most of them are pretty okay, and that the problem is confined to a few specific points in the company. However, “unknown problem people making major decisions at RSA” is a bit unwieldy, so I will just say RSA. Third, I'm not calling for a total boycott on RSA. I work almost literally across the street from them and I don’t want to get beat up by roving gangs of cryptographers at the local Chipotle.

RSA's denial published last night is utter codswallop that denies pretty much everything in the world except the actual allegations put forth by Reuters and hinted at for months by [other sources](http://li

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions