oleg-nenashev

#!/bin/bash -ex

REPO_NAME=${PWD##*/}
TARGET_ORG="jenkinsci"

#TODO: fetch from GitHib API
#TODO: if no, process parameters correctly
GITHUB_PR_NUMBER=${1}
FROM_USER=${2}
BRANCH=${3}

reichert621

// bower dependency: "ng-file-upload"
// npm dependency: "loopback-component-storage"

'use strict';

angular
  .module('app', [
    'ngFileUpload'
  ])
  .controller('UploadController', function(Upload) {

mosabua

/**
 * init.gradle file for development using Nexus as proxy repository
 * 
 * @author Manfred Moser <manfred@simpligility.com
 */

apply plugin:NexusRepositoryPlugin

class NexusRepositoryPlugin implements Plugin<Gradle> {

rmurphey

function multiply(a, b) {
  return a * b;
}

function divide(a, b) {
  if (b === 0) {
    throw "Don't try to divide by zero!";
  }

  return Math.round(a / b);

jbryer

#' Simplified loading and installing of packages
#'
#' This is a wrapper to \code{\link{require}} and \code{\link{install.packages}}.
#' Specifically, this will first try to load the package(s) and if not found
#' it will install then load the packages. Additionally, if the 
#' \code{update=TRUE} parameter is specified it will check the currently 
#' installed package version with what is available on CRAN (or mirror) and 
#' install the newer version.
#' 
#' @param pkgs a character vector with the names of the packages to load.

sumardi

# New repository
mkdir <repo> && cd <repo>
git init
git remote add –f <name> <url>
git config core.sparsecheckout true
echo some/dir/ >> .git/info/sparse-checkout
echo another/sub/tree >> .git/info/sparse-checkout
git pull <remote> <branch>

# Existing repository

tjanczuk

// How to connect 5 publishers with 5 subscribers 
// over TCP using ZeroMQ's XPUB/XSUB proxy.

// sub (connect) 
//   <-8701-> 
// (bind) xpub <---> xsub (bind) 
//   <-8700-> 
// (connect) pub

var zmq = require('zmq');

chrisjacob

Intro

Description: Setup GitHub Pages "gh-pages" branch and "master" branch as subfolders of a parent project folder ("grandmaster").

Author: Chris Jacob @_chrisjacob

Tutorial (Gist): https://gist.github.com/833223

The Result

learncodeacademy

upstream project {
  server 22.22.22.2:3000;
  server 22.22.22.3:3000;
  server 22.22.22.5:3000;
}

server {
  listen 80;

  location / {

joyrexus

Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.

“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data. Otherwise, use application/x-www-form-urlencoded.”

---

Matt Bridges' answer in full:

The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing