robconery

title	description	author	created	updated
{{title}}	{{description}}	{{author}}	{"DATE:YYYY-MM-DD HH:mm:ss" => nil}	{"DATE:YYYY-MM-DD HH:mm:ss" => nil}

dannberg

---
created: <% tp.file.creation_date() %>
---
tags:: [[+Daily Notes]]

# <% moment(tp.file.title,'YYYY-MM-DD').format("dddd, MMMM DD, YYYY") %>

<< [[Timestamps/<% tp.date.now("YYYY", -1) %>/<% tp.date.now("MM-MMMM", -1) %>/<% tp.date.now("YYYY-MM-DD-dddd", -1) %>|Yesterday]] | [[Timestamps/<% tp.date.now("YYYY", 1) %>/<% tp.date.now("MM-MMMM", 1) %>/<% tp.date.now("YYYY-MM-DD-dddd", 1) %>|Tomorrow]] >>

---

manicminer

Ansible invocation with assumed IAM role

How it works

• boto3 initializes a session using the specified profile, for which it assumes a role as configured in your ~/.aws/config
• Python script with above session initialization prints out shell-compatible environment variables of the temporary credentials
• Wrapper script sets these a la eval
• By the time Ansible runs, the AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SECURITY_TOKEN (for boto2) / AWS_SESSION_TOKEN (for boto3) are all set, and are consumed by boto2 in the inventory script and other boto2-based modules

Notes

yanburman

# This hosts file is brought to you by Dan Pollock and can be found at
# http://someonewhocares.org/hosts/
# You are free to copy and distribute this file for non-commercial uses,
# as long the original URL and attribution is included.

#<localhost>
127.0.0.1	localhost
127.0.0.1	localhost.localdomain
255.255.255.255	broadcasthost
::1		localhost

dwilkie

Build docker image

$ cd /path/to/Dockerfile
$ sudo docker build .

View running processes

perbu

sub vcl_hit {
    if (obj.ttl >= 0s) {
        # normal hit
        return (deliver);
    }
    # We have no fresh fish. Lets look at the stale ones.
    if (std.healthy(req.backend_hint)) {
        # Backend is healthy. Limit age to 10s.
        if (obj.ttl + 10s > 0s) {
            set req.http.grace = "normal(limited)";

thisismitch

global
	log /dev/log	local0
	log /dev/log	local1 notice
	chroot /var/lib/haproxy
	stats socket /run/haproxy/admin.sock mode 660 level admin
	stats timeout 30s
	user haproxy
	group haproxy
	daemon
	maxconn 2048

bfleming-ciena

#list metrics
aws --profile dev --region us-east-1 cloudwatch list-metrics --namespace "AWS/Billing"

# Estimated charges
aws --region us-east-1 cloudwatch get-metric-statistics  --namespace "AWS/Billing"  --metric-name "EstimatedCharges"  --dimension "Name=Currency,Value=USD"  --start-time $(gdate +"%Y-%m-%dT%H:%M:00" --date="-12 hours")  --end-time $(gdate +"%Y-%m-%dT%H:%M:00")  --statistic Maximum  --period 60  --output text | sort -r -k 3 | head -n 1 | cut -f 2

# Marketplace Charges
aws --profile dev --region us-east-1 cloudwatch get-metric-statistics  --namespace "AWS/Billing"  --metric-name "EstimatedCharges"  --dimensions Name=ServiceName,Value=AWSMarketplace Name=Currency,Value=USD   --start-time $(gdate +"%Y-%m-%dT%H:%M:00" --date="-12 hours")  --end-time $(gdate +"%Y-%m-%dT%H:%M:00")  --statistic Maximum  --period 60  --output text

# Redshift

tahmidsadik

How to Completely Remove Android Studio


Execute these commands from the terminal

rm -Rf /Applications/Android\ Studio.app
rm -Rf ~/Library/Preferences/AndroidStudio*
rm ~/Library/Preferences/com.google.android.studio.plist
rm -Rf ~/Library/Application\ Support/AndroidStudio*
rm -Rf ~/Library/Logs/AndroidStudio*

outro56

progrium/bashstyle

Bash is the JavaScript of systems programming. Although in some cases it's better to use a systems language like C or Go, Bash is an ideal systems language for smaller POSIX-oriented or command line tasks. Here's three quick reasons why:

• It's everywhere. Like JavaScript for the web, Bash is already there ready for systems programming.
• It's neutral. Unlike Ruby, Python, JavaScript, or PHP, Bash offends equally across all communities. ;)
• It's made to be glue. Write complex parts in C or Go (or whatever!), and glue them together with Bash.

This document is how I write Bash and how I'd like collaborators to write Bash with me in my open source projects. It's based on a lot of experience and time collecting best practices. Most of them come from these two articles, but here integrated, slightly modified, and focusing on the most bang for buck items. Plus some ne