chuangbo

替换上你的 API Token，域名ID，记录ID等参数，就可以运行了。 会在后台一直运行，每隔30秒检查一遍IP，如果修改了就更新IP。

获取 API Token 的方式

获得 domain_id 可以用 curl

curl -k https://dnsapi.cn/Domain.List -d "login_token=TOKEN"`

vunb

ffmpeg -i input.mp3 -acodec pcm_s16le -ac 1 -ar 16000 output.wav

# To convert all mp3 files in a directory in Linux:

for f in *.mp3; do ffmpeg -i "$f" -acodec pcm_s16le -ac 1 -ar 16000 "${f%.mp3}.wav"; done

# Or Windows:

for /r %i in (*) do ffmpeg -i %i -acodec pcm_s16le -ac 1 -ar 16000 %i.wav

zsup

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

• Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
• Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
• Once documentation has been written, development should commence, and test-driven development is preferred.
• Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
• When a feature is being modified, it should be modified documentation-first.
• When documentation is modified, so should be the tests.

lunny

package main

import (
	"fmt"
	"syscall"
)

type DiskStatus struct {
	All  uint64 `json:"all"`
	Used uint64 `json:"used"`

julianlam

var	passport = module.parent.require('passport'),
	passportLocal = module.parent.require('passport-local').Strategy,
	plugin = {};

plugin.login = function() {
	winston.info('[login] Registering new local login strategy');
	passport.use(new passportLocal({passReqToCallback: true}, plugin.continueLogin));
};

plugin.continueLogin = function(req, username, password, next) {

dgp

2 - Autos & Vehicles
1 -  Film & Animation
10 - Music
15 - Pets & Animals
17 - Sports
18 - Short Movies
19 - Travel & Events
20 - Gaming
21 - Videoblogging
22 - People & Blogs

taoyuan

# npm using https for git
git config --global url."https://github.com/".insteadOf git@github.com:
git config --global url."https://".insteadOf git://

# npm using git for https
git config --global url."git@github.com:".insteadOf https://github.com/
git config --global url."git://".insteadOf https://

bussiere

package main

import (
	"bytes"
	"compress/gzip"
	"fmt"
	"encoding/base64"
	"io/ioutil"
)

palopezv

/**
 * dwmconfig.h 
 * Hardware multimedia keys
 */
/* Somewhere at the beginning of config.h include: */

/* 
 You obviously need the X11 development packages installed, X11proto in particular, but 
 here is the location of the keysyms header upstream copy if you can't bother 
 using the contents of your own hard drive. ;-P

turbo

Merged from https://github.com/joelparkerhenderson/git_commit_message and https://chris.beams.io/posts/git-commit/

General Rules

• Commit messages must have a subject line and may have body copy. These must be separated by a blank line.
• The subject line must not exceed 50 characters
• The subject line should be capitalized and must not end in a period
• The subject line must be written in imperative mood (Fix, not Fixed / Fixes etc.)
• The body copy must be wrapped at 72 columns
• The body copy must only contain explanations as to what and why, never how. The latter belongs in documentation and implementation.