so0k

Function Get-FileName {   
    [System.Reflection.Assembly]::LoadWithPartialName("System.windows.forms") | Out-Null
    $OpenFileDialog = New-Object System.Windows.Forms.OpenFileDialog
    $OpenFileDialog.initialDirectory = $initialDirectory
    $OpenFileDialog.filter = "Comma Separated files (*.csv)| *.csv"
    $OpenFileDialog.ShowDialog() | Out-Null
    $OpenFileDialog.filename
}

$Input  = Get-FileName

so0k

function getS3Config() {
    return Restangular.one(URLS.GET_S3_CONFIG).get();
}

//function with s3Config & angular $upload module injected
$upload.upload({
    url: protocol + '://' + s3config.bucket + '/',
    method: method.POST,
    data: {
        'key': funcs[i],

so0k

# Eraser Bot chat data
#
#	Thanks to Meanstryk for the additions
#	->	http://www.planetquake.com/ramshackle
#	Also thanks to Shawn "Benighted1" Lisk for more additions
#	->  kclisk@bright.net
#
# OK, here's the deal. Bot's can say one of the following things:
#
# 1. Greetings

so0k

#!/bin/bash
set -e

shopt -s nocasematch #For case insensitive string matching, for the first parameter

SELF=`which $0`

case "$1" in
  create) # sshcommand create <user> <command>
    if [[ $# -ne 3 ]]; then

so0k

Digital Ocean recently released private networking support in their NYC2 Data center.

They also published a blog post on how to setup a new droplet with private networking. But one thing the post doesn't do is tell you how to scale your private network for many boxes. One approach is obviously to edit /etc/hosts (but this gets annoying when you add a new box). A better way is to create an internal DNS zone (via the digital ocean web interface) and have your droplets use it:

Steps

setup the internal DNS zone file

1. Login to digital ocean
2. Click "DNS" on the right hand menu

so0k

Docker Tallinn Demo script

Ensure swarm cluster is started before start of demo script

Docker CLI

Using Beta Docker for Windows

so0k

Orig AWS Documentation:

url

You can enable query logging for your PostgreSQL DB instance by setting two parameters in the DB parameter group associated with your DB instance: log_statement and log_min_duration_statement. The log_statement parameter controls which SQL statements are logged. We recommend setting this parameter to all to log all statements; the default value is none. Alternatively, you can set this value to ddl to log all data definition language (DDL) statements (CREATE, ALTER, DROP, etc.) or to mod to log all DDL and data modification language (DML) statements (INSERT, UPDATE, DELETE, etc.).

The log_min_duration_statement parameter sets the limit in milliseconds of a statement to be logged. All SQL statements that run longer than the parameter setting are logged. This parameter is disabled and set to minus 1 (-1) by default. Enabling this parameter can help you find unoptimized queries.

so0k

unbindall
bind "0" "slot10"
bind "1" "slot1"
bind "2" "slot2"
bind "3" "slot3"
bind "4" "slot4"
bind "5" "slot5"
bind "9" "slot9"
bind "a" "+duck"
bind "b" "slot8"

so0k

Powerline

http://powerline.readthedocs.io

 mkdir powerlineFonts
 cd powerlineFonts/
 git init
 git remote add origin https://github.com/powerline/fonts.git
 git remote -v

so0k

 @echo off

   :: BatchGotAdmin
:-------------------------------------
REM  --> Check for permissions
>nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system"

REM --> If error flag set, we do not have admin.
if '%errorlevel%' NEQ '0' (
echo Requesting administrative privileges...