rentzsch

USER=rentzsch
PASS=mypassword
REPO=mogenerator

# Delete default labels
curl --user "$USER:$PASS" --include --request DELETE "https://api.github.com/repos/$USER/$REPO/labels/bug"
curl --user "$USER:$PASS" --include --request DELETE "https://api.github.com/repos/$USER/$REPO/labels/duplicate"
curl --user "$USER:$PASS" --include --request DELETE "https://api.github.com/repos/$USER/$REPO/labels/enhancement"
curl --user "$USER:$PASS" --include --request DELETE "https://api.github.com/repos/$USER/$REPO/labels/invalid"
curl --user "$USER:$PASS" --include --request DELETE "https://api.github.com/repos/$USER/$REPO/labels/question"

domenic

module.exports = and ES6 Module Interop in Node.js

The question: how can we use ES6 modules in Node.js, where modules-as-functions is very common? That is, given a future in which V8 supports ES6 modules:

• How can authors of function-modules convert to ES6 export syntax, without breaking consumers that do require("function-module")()?
• How can consumers of function-modules use ES6 import syntax, while not demanding that the module author rewrites his code to ES6 export?

@wycats showed me a solution. It involves hooking into the loader API to do some rewriting, and using a distinguished name for the single export.

This is me eating crow for lots of false statements I've made all over Twitter today. Here it goes.

balupton

Linux

Setup

# If inside vmware install vmware tools (these are just as good as the commercial ones)
sudo apt-get install open-vm-tools open-vm-tools-desktop

# Install git
sudo apt-get install git

praetoriansentry

library("rjson")
library("quantmod")
json_file <- "https://data.mtgox.com/api/2/BTCUSD/money/trades/fetch"
json_data <- fromJSON(paste(readLines(json_file), collapse=""))

mtgox <- json_data$data

trades <-  do.call(rbind.data.frame, mtgox)

aaronpk

Swap out the two URLs (first is source, second is target) then run with curl:

curl -X POST -d @pingback.xml http://example.com/xmlrpc

sandeepshetty

{
	"entries": [
		{
			"type": "post",
			"id": "2013/07/06/4",
			"content": "",
			"published": "",
			"updated": "",
			"response_counts": {
				"comments": 0,

Sharpie

# -*- mode: ruby -*-
# vi: set ft=ruby :

# This configuration requires Vagrant 1.5 or newer and two plugins:
#
#   vagrant plugin install vagrant-hosts        ~> 2.1.4
#   vagrant plugin install vagrant-auto_network ~> 1.0.0
#
# After installation, the following steps will spin up a master and agent that
# can communicate with each other:

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

veganstraightedge

{
  "@context": "http://json-ld.org/contexts/person.jsonld",
  "@id":      "http://dbpedia.org/resource/John_Lennon",
  "name":     "John Lennon",
  "born":     "1940-10-09",
  "spouse":   "http://dbpedia.org/resource/Cynthia_Lennon"
}

barnabywalters

on GET /notes
	fetch the 20 most recent notes filtered by tag
	show as h-feed

on GET /notes/new
	the user must be an admin
	show autofilled note-form

on GET /notes/{id}
	fetch note