paolorossi

/*
 * Inspired by: http://stackoverflow.com/questions/4360060/video-streaming-with-html-5-via-node-js
 */

var http = require('http'),
    fs = require('fs'),
    util = require('util');

http.createServer(function (req, res) {
  var path = 'video.mp4';

andreyvit

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

1wErt3r

;SMBDIS.ASM - A COMPREHENSIVE SUPER MARIO BROS. DISASSEMBLY
;by doppelganger ([email protected])

;This file is provided for your own use as-is.  It will require the character rom data
;and an iNES file header to get it to work.

;There are so many people I have to thank for this, that taking all the credit for
;myself would be an unforgivable act of arrogance. Without their help this would
;probably not be possible.  So I thank all the peeps in the nesdev scene whose insight into
;the 6502 and the NES helped me learn how it works (you guys know who you are, there's no 

rwjblue

• Data Down / Actions Up

  • http://emberjs.jsbin.com/nayaho/edit?html,js - Interdependent select boxes. No observers.
  • http://ember-twiddle.com/2d7246875098d0dbb4a4 - One Way Input

• Plain JSBin's

  • http://rwjblue.jsbin.com/pixeki/edit?html,js,output

• Ember Version Base JSBin's

  • 1.0 - http://emberjs.jsbin.com/juluje/edit?html,js,output

• 1.1 - http://emberjs.jsbin.com/cofufo/edit?html,js,output

joyrexus

Demo of multipart form/file uploading with hapi.js.

Usage

npm install
npm run setup
npm run server

Then ...

sebastienblanc

Add a new platform in the UnifiedPush Server

This is simple checklist for those who would like to add a new Push Platform support to UPS (like Blackberry hint for the community hint).

Adapt the Model

• Start by updating the Variant Enum class by adding your platform

• Create a subclass of the Variant base class , add any properties that are specific to this platform (like API keys, secrets etc ...)

matzew

        Map<String, Object> criteria = new LinkedHashMap<>();
        criteria.put("categories", Arrays.asList("feedhenry"));
        Map<String, Object> jsonContainer = new LinkedHashMap<>();
        jsonContainer.put("alert", "Hello Luke, This is from MQTT");
        jsonContainer.put("criteria", criteria);

        String jsonPayload = new Gson().toJson(jsonContainer);

wei-lee

{
  "name": "dev",
  "description": "Development role",
  "json_class": "Chef::Role",
  "default_attributes": {
"host_src_dir": "/Users/weili/work/fh/eng/",
    "feedhenry_common": {
"src": "/mnt/src"
    },
    "vm": {

paoloantinori

#!/bin/bash

export TKN=$(curl -X POST 'http://localhost:8080/auth/realms/master/protocol/openid-connect/token' \
 -H "Content-Type: application/x-www-form-urlencoded" \
 -d "username=admin" \
 -d 'password=admin' \
 -d 'grant_type=password' \
 -d 'client_id=admin-cli' | jq -r '.access_token')

curl -X GET 'http://localhost:8080/auth/admin/realms' \

Rich-Harris

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.