dgulino

#!/usr/bin/env python

"""
Python script that runs one-liner python scripts similarly to how Perl runs them

portions based on http://code.activestate.com/recipes/437932-pyline-a-grep-like-sed-like-command-line-tool/
(Graham Fawcett, Jacob Oscarson, Mark Eichin)
interface inspired by Perl
"""

danriti

$('.outdated-diff-comment-container').addClass('open');

lalyos

docker-yml() {
  docker inspect -f $'
{{.Name}}
  image: {{.Config.Image}}
  entrypoint: {{json .Config.Entrypoint}}
  environment: {{range .Config.Env}}
    - {{.}}{{end}}
' $1
}

randerzander

# See https://pip.pypa.io/en/latest/installing.html for how to install pip, then:
# pip install simple-salesforce
from simple_salesforce import Salesforce
import string

# To get your SFDC token, see https://help.salesforce.com/apex/HTViewHelpDoc?id=user_security_token.htm
# salesforce_login.txt should contain the following, one per line:
# Your Name
# your_email@sfdc_account.com
# your_password

efrecon

docker run \
  --name {{printf "%q" .Name}} \
    {{- with .HostConfig}}
        {{- if .Privileged}}
  --privileged \
        {{- end}}
        {{- if .AutoRemove}}
  --rm \
        {{- end}}
        {{- if .Runtime}}

teki

#!/usr/bin/python
# use it with https://github.com/matryer/bitbar
import os
import re
import subprocess
import tempfile
import time
import urllib2

TW_URL = 'https://twitter.com/PrimitivePic'

manasthakur

Managing plugins in Vim: The basics

Let's say the plugin is at a GitHub URL https://github.com/manasthakur/foo. First get the plugin by either cloning it (git clone https://github.com/manasthakur.foo.git) or simply downloading it as a zip (from its GitHub page).

Adding a plugin in Vim is equivalent to adding the plugin's code properly into its runtimepath (includes the $HOME/.vim directory by default). For example, if the layout of a plugin foo is as follows:

foo/autoload/foo.vim
foo/plugin/foo.vim

manasthakur

Using git-submodules to version-control Vim plugins

If you work across many computers (and even otherwise!), it's a good idea to keep a copy of your setup on the cloud, preferably in a git repository, and clone it on another machine when you need. Thus, you should keep the .vim directory along with your .vimrc version-controlled.

But when you have plugins installed inside .vim/bundle (if you use pathogen), or inside .vim/pack (if you use Vim 8's packages), keeping a copy where you want to be able to update the plugins (individual git repositories), as well as your vim-configuration as a whole, requires you to use git submodules.

Creating the repository

Initialize a git repository inside your .vim directory, add everything (including the vimrc), commit and push to a GitHub/BitBucket/GitLab repository:

cd ~/.vim

thebsdbox

Docker EE Inline upgrade procedure

This is a guide that details the steps to have in place a duplicate environment to upgrade to, and requires an existing UCP/DTR cluster.

Prerequisites

Ensure that new nodes are all confiured with identical firewall rules and that all of the relevant swarm joins are performed.

• Create a backup from existing UCP Cluster (UCP Will stop during the backup)

Ensure you use the correct tag to see what is running, check in docker images

wsong

package main

import (
	"context"
	"fmt"
	"os"
	"time"

	"github.com/docker/swarmkit/api"
	"github.com/docker/swarmkit/ca"