justintv

# If you work with git, you've probably had that nagging sensation of not knowing what branch you are on. Worry no longer!

export PS1="\\w:\$(git branch 2>/dev/null | grep '^*' | colrm 1 2)\$ "

# This will change your prompt to display not only your working directory but also your current git branch, if you have one. Pretty nifty!

# ~/code/web:beta_directory$ git checkout master
# Switched to branch "master"
# ~/code/web:master$ git checkout beta_directory
# Switched to branch "beta_directory"

isaacs

echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
. ~/.bashrc
mkdir ~/local
mkdir ~/node-latest-install
cd ~/node-latest-install
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1
./configure --prefix=~/local
make install # ok, fine, this step probably takes more than 30 seconds...
curl https://www.npmjs.org/install.sh | sh

treffynnon

var http = require('http');
http.createServer(function (req, http_res) {
  http_res.writeHead(200, {'Content-Type': 'text/plain'});
  var response = '';

  var cradle = require('cradle');
  var connection = new(cradle.Connection)('https://subdomain.iriscouch.com', 443, {
      auth: { username: 'username', password: 'password' }
  });

takezoe

import scala.util.parsing.json._

val result = JSON.parseFull("""
  {"name": "Naoki",  "lang": ["Java", "Scala"]}
""")

result match {
  case Some(e) => println(e) // => Map(name -> Naoki, lang -> List(Java, Scala))
  case None => println("Failed.")
}

wfarr

› git show i-herd-u-liek-chef:foo
bar

› git show i-herd-u-liek-chef~1:foo
fatal: Path 'foo' exists on disk, but not in 'i-herd-u-liek-chef~1'.

lavallee

/*

If you want more control over impress.js, the first thing is to change the way you call it. The demo
 initializes impress.js like this:

<script src="js/impress.js"></script> 
<script>impress().init();</script>

You want to change this to the following:

paulmillr

Most active GitHub users (git.io/top)

The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 21 Sep 2022 till Thu, 21 Sep 2023.

Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:

githubUsers
 .filter(user => user.followers > 1000)

domenic

Node.js core does its best to treat every platform equally. Even if most Node developers use OS X day to day, some use Windows, and most everyone deploys to Linux or Solaris. So it's important to keep your code portable between platforms, whether you're writing a library or an application.

Predictably, most cross-platform issues come from Windows. Things just work differently there! But if you're careful, and follow some simple best practices, your code can run just as well on Windows systems.

Paths and URLs

On Windows, paths are constructed with backslashes instead of forward slashes. So if you do your directory manipulation

earthgecko

#!/bin/bash
# bash generate random alphanumeric string
#

# bash generate random 32 character alphanumeric string (upper and lowercase) and 
NEW_UUID=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)

# bash generate random 32 character alphanumeric string (lowercase only)
cat /dev/urandom | tr -dc 'a-z0-9' | fold -w 32 | head -n 1

dergachev

Vagrant Setup

This tutorial guides you through creating your first Vagrant project.

We start with a generic Ubuntu VM, and use the Chef provisioning tool to:

• install packages for vim, git
• create user accounts, as specified in included JSON config files
• install specified user dotfiles (.bashrc, .vimrc, etc) from a git repository

Afterwards, we'll see how easy it is to package our newly provisioned VM