StevenACoffman

#!/bin/bash
# call this with normal curl arguments, especially url argument, e.g.
# safecurl.sh "http://example.com:8080/something/"
# separating the (verbose) curl options into an array for readability
curl_args=(
  -H 'Accept:application/json'
  -H 'Content-Type:application/json'
  --write '\n%{http_code}\n'
  --fail
  --silent

StevenACoffman

#!/bin/bash

usage() {
	echo "
Usage: wti [-h?] [-l LOGIN] ISSUE...

wti = \"(W)hat (T)he (I)ssue?\". Script tries to get description of the specified 
ISSUE(es) from jira. For each ISSUE in list script will ouput the line in 
the following format: ISSUE_ID — ISSUE_DESC

StevenACoffman

#!/bin/bash
JIRA_URL="https://jira.mydomain.org"
JIRA_AUTH_URI="/rest/auth/2/session"
JIRA_API_URI="/rest/api/2/"
curl -D - -u $JIRA_LOGIN:$JIRA_PASSWORD -X GET -H "Content-Type: application/json" -s ${JIRA_URL}${JIRA_API_URI/issue/$1

StevenACoffman

#!/bin/bash
#This script requires an up-to-date version of the aws cli tool

profile=$1
environment=$2

region=us-east-1
service_name=com.amazonaws.$region.s3

get_env_vpc_id () {

StevenACoffman

From Why Client Side Rendering Won:

• No Full Page Reload Required
• Lazy Loading
• Rich Interactions
• Cheap Hosting
• Use a CDN
• Easy Deployments
• Enforced Separation of Concerns
• Learn Once, Write Everywhere
• Same UI Technology for Web, Native Mobile, and Desktop

StevenACoffman

Erik Meier -- The Four Fundamental Effects

	One	Many
Sync	T	Enumerable[T]
Async	Future[T]	Observable[T]

• future = promise
• observable = rxjs/baconjs/cyclejs/kefirjs observable

StevenACoffman

Two methods:

how-do-i-install-from-a-local-cache-with-pip

First Method

PIP_DOWNLOAD_CACHE has some serious problems. Most importantly, it encodes the hostname of the download into the cache, so using mirrors becomes impossible.

The better way to manage a cache of pip downloads is to separate the "download the package" step from the "install the package" step. The downloaded files are commonly referred to as "sdist files" (source distributions) and I'm going to store them in a directory $SDIST_CACHE.

The two steps end up being:

StevenACoffman

{
  "method": "$context.httpMethod",
  "resourcePath": "$context.resourcePath",
  "querystring": {
    #foreach($key in $input.params().querystring.keySet())
    "$key": "$input.params().querystring.get($key)"#if($foreach.hasNext),#end
    #end
  },
  "path": {
    #foreach($key in $input.params().path.keySet())

StevenACoffman

# This is a "Managed Script" in Jenkins
COMMIT=`aws lambda get-alias --region $AWS_REGION --function-name $FUNCTION_NAME --name $PUBLISH_FROM_ALIAS | grep "Description" | cut -d'"' -f4`
VERSION=`aws lambda publish-version --region $AWS_REGION --function-name $FUNCTION_NAME --description $COMMIT | grep "Version" | cut -d'"' -f4`
aws lambda update-alias --region $AWS_REGION --function-name $FUNCTION_NAME --function-version $VERSION --name $PUBLISH_TO_ALIAS --description $COMMIT

StevenACoffman

AWS IoT Workflow

From Some more on AWS IoT. It’s a little difficult to simplify what’s going on, but I think this is pretty good. At the highest level, think of it this way: AWS IoT recieves messages and routes them based on rules to other AWS services

Here’s the basic workflow of AWS IoT. It’s a simplification and leaves out a number of important services, but this is the core of it. Understanding this is to understand what AWS IOT can do … and what it can do for you.

Here’s the workflow:

• your Things send messages
• the Device Gateway receives and authenticates the messages
• the Rules Engine authorizes the messages and then routes them to other AWS services