tralston

After updating pg_hba.conf or postgresql.conf, the server needs the config needs to be reloaded. The easiest way to do this is by restarting the postgres service:

service postgresql restart

When the service command is not available (no upstart on Synology NAS, for example), there are some more creative ways to reload the config. Note this first one needs to be done under the user that runs postgres (usually the user=postgres).

user#  sudo su postgres
postgres#  pg_ctl reload

porjo

Retrieve hosted zones with aws route53 list-hosted-zones then enter the zone Id below:

aws route53 list-resource-record-sets --hosted-zone-id "/hostedzone/xxxxxxxxxxx" | \
   jq -r '.ResourceRecordSets[] | [.Name, .Type, (.ResourceRecords[]? | .Value), .AliasTarget.DNSName?]  | @tsv'

MichaelLawton

function deleteSavedItems() {
	var query = document.querySelectorAll("#sc-saved-cart input[value=Delete]")
	if (query.length) {
		query[0].click();
	}
	if (query.length > 1) {
		setTimeout(deleteSavedItems,100);
	}
	else {
		console.log('Finished');

mgoodness

AWS Service annotations

• service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval (in minutes)
• service.beta.kubernetes.io/aws-load-balancer-access-log-enabled (true|false)
• service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name
• service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix
• service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags (comma-separated list of key=value)
• service.beta.kubernetes.io/aws-load-balancer-backend-protocol (http|https|ssl|tcp)
• service.beta.kubernetes.io/aws-load-balancer-connection-draining-enabled (true|false)

mlafeldt

First of all, install Homebrew itself.

As the tap is a private Git repo, you need to generate a GitHub token with repo scope and then add this token to your ~/.netrc file like this:

machine github.com
  login <your GitHub user>
  password <your GitHub token>

andyshinn

{
    "require": {
        "mfacenet/hello-world": "v1.*"
    }
}

zhujunsan

What / Why

Deploy key is a SSH key set in your repo to grant client read-only (as well as r/w, if you want) access to your repo.

As the name says, its primary function is to be used in the deploy process in replace of username/password, where only read access is needed. Therefore keep the repo safe from the attack, in case the server side is fallen.

How to

1. Generate a ssh key

tessus

#!/bin/bash

TMUX_VERSION=2.3
NCURSES_VERSION=6.0
LIBEVENT_VERSION=2.0.22

BASEDIR=${HOME}/work/tmux-static
TMUXTARGET=${BASEDIR}/local
mkdir -p $TMUXTARGET
cd $BASEDIR

kurokikaze

(new-object System.Net.WebClient).DownloadFile('http://dl.google.com/chrome/install/375.126/chrome_installer.exe', 'c:/temp/chrome.exe');. c:/temp/chrome.exe /silent /install;rm c:/temp -rec

magnetikonline

AWS S3 bucket and IAM policy recipes

• Recipes
  • Anonymous GET access
  • Anonymous GET access - match HTTP referrer
  • Full access for specific IAM user/role
  • GET/PUT/DELETE access to specific path within a bucket
  • Restricted LIST & PUT/DELETE access to specific path within a bucket
  • Full access (and S3 console) for specific IAM users
  • Bucket and object delete deny