This blog post shows how to create a token:
Enable developer mode:
- User Settings
- Advanced
- Enable Developer Mode
Get the channel id:
This blog post shows how to create a token:
Enable developer mode:
Get the channel id:
#!groovy | |
node { | |
def err = null | |
def environment = "Development" | |
currentBuild.result = "SUCCESS" | |
load "$JENKINS_HOME/.envvars/.env.groovy" | |
try { |
#!/usr/bin/env bash | |
set -e | |
for full_name in $(kubectl get all -o name | grep -vE replicaset\|pod); do | |
name="$(echo "$full_name" | sed -e "s/.*\///g")"; | |
type="$(echo "$full_name" | sed -e "s/\/.*//g")"; | |
case "${type}" in | |
deployment*) | |
type=Deployment | |
;; | |
"service") |
-- PostgreSQL cheat sheet | |
--postgres is set up to use local.6 which is syslog'd to sflog001 | |
--slow query log is /var/log/localmessages | |
--config files are always in /data/friend/*.conf | |
--vacuums are set via cfengine, we use both manual and auto. vacuums/analyze help with frozen id's being recouped, and thus TX'id's not going over 2b thus causing massing shutdown/reset. Fix it to exp/imp high TX tables. | |
--to log into psql: psql -U postgres -d <DB> (usually friend) |
This is a collection of the most common commands I run while administering Postgres databases. The variables shown between the open and closed tags, "<" and ">", should be replaced with a name you choose. Postgres has multiple shortcut functions, starting with a forward slash, "". Any SQL command that is not a shortcut, must end with a semicolon, ";". You can use the keyboard UP and DOWN keys to scroll the history of previous commands you've run.
http://www.postgresql.org/download/linux/ubuntu/ https://help.ubuntu.com/community/PostgreSQL
#!/usr/bin/env python | |
import sys, subprocess, os | |
TOOLS = ['bcompare', 'meld'] | |
HEAD = 'HEAD' | |
TMP = '/tmp/' | |
execute = lambda command: subprocess.check_output(command) | |
which = lambda tool: execute(['which', tool]).strip() |
Magic words:
psql -U postgres
Some interesting flags (to see all, use -h
or --help
depending on your psql version):
-E
: will describe the underlaying queries of the \
commands (cool for learning!)-l
: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)This is intended as a quick reference and showcase. For more complete info, see [John Gruber's original spec](http://daringfireball.net/projects/markdown/) and the [Github-flavored Markdown info page](http://github.github.com/github-flavored-markdown/). | |
This cheatsheet is specifically *Markdown Here's* version of Github-flavored Markdown. This differs slightly in styling and syntax from what Github uses, so what you see below might vary a little from what you get in a *Markdown Here* email, but it should be pretty close. | |
You can play around with Markdown on our [live demo page](http://www.markdown-here.com/livedemo.html). | |
##### Table of Contents | |
[Headers](#headers) | |
[Emphasis](#emphasis) | |
[Lists](#lists) |
source <(kubectl completion bash) | |
__start_kubectl_cust() | |
{ | |
local cur prev words cword | |
declare -A flaghash 2>/dev/null || : | |
if declare -F _init_completion >/dev/null 2>&1; then | |
_init_completion -s || return | |
else | |
__kubectl_init_completion -n "=" || return | |
fi |