kovetskiy

#!/bin/bash
###
### my-script — does one thing well
###
### Usage:
###   my-script <input> <output>
###
### Options:
###   <input>   Input file to read.
###   <output>  Output file to write. Use '-' for stdout.

simpsoka

Do I want to die on this hill?

• Pass: This is morally good and if not handled has long term consequences
• Fail: This if self serving

Am I including everyone?

• Pass: My ego is not driving this conversation
• Fail: The people in this conversation will only tell me I'm right and not push back

miguelmota

package main

import (
	"fmt"
	"reflect"
)

func main() {
	var v *string
	fmt.Println(isNil(v)) // true

laggardkernel

Comparison of ZSH frameworks and plugin managers

Changelog

• update 1: add a FAQ section
• update 2: benchmark chart and feature comparison table
• update 3:
  • improve the table with missing features for antigen
  • new zplg times result

TLDR

bojand

Just documenting docs, articles, and discussion related to gRPC and load balancing.

https://github.com/grpc/grpc/blob/master/doc/load-balancing.md

Seems gRPC prefers thin client-side load balancing where a client gets a list of connected clients and a load balancing policy from a "load balancer" and then performs client-side load balancing based on the information. However, this could be useful for traditional load banaling approaches in clound deployments.

https://groups.google.com/forum/#!topic/grpc-io/8s7UHY_Q1po

gRPC "works" in AWS. That is, you can run gRPC services on EC2 nodes and have them connect to other nodes, and everything is fine. If you are using AWS for easy access to hardware then all is fine. What doesn't work is ELB (aka CLB), and ALBs. Neither of these support HTTP/2 (h2c) in a way that gRPC needs.

brianredbeard

About

AWS provides a mechanism for temporarily assuming another role within their API system. While it is not a technically hard process it can be convoluted and hard to understand. This document aims to both make it easier to follow along with as well as give an in depth explanation of some of the underpinnings of the Bourne Again Shell (aka BASH) which can make this easier to utilize on a day to day basis.

Explanation

Below is an overexplained version of the following process:

1. Using credentials stored in ~/.aws/credentials as a "profile" which are then understood by the AWS command line tools
2. Using those AWS credentials, temporarily assume a role using the AWS Security Token Service (STS) to get temporary

jbochi

miglen

List of Linux networking tools

netstat (ss)

Displays contents of /proc/net files. It works with the Linux Network Subsystem, it will tell you what the status of ports are ie. open, closed, waiting, masquerade connections. It will also display various other things. It has many different options. Netstat (Network Statistic) command display connection info, routing table information etc. To displays routing table information use option as -r.

Sample output:

Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)    
tcp4 0 0 127.0.0.1.62132 127.0.0.1.http ESTABLISHED

vcastellm

#!/usr/bin/env bash
set -e

function usage() {
    set -e
    cat <<EOM
    ##### ecs-run #####
    Simple script for running tasks on Amazon Elastic Container Service
    One of the following is required:
    Required arguments:

jeffjohnson9046

## I just ran into this after initializing a Visual Studio project _before_ adding a .gitignore file (like an idiot).  
## I felt real dumb commiting a bunch of files I didn't need to, so the commands below should do the trick.  The first two commands
## came from the second answer on this post:  http://stackoverflow.com/questions/7527982/applying-gitignore-to-committed-files

# See the unwanted files:
git ls-files -ci --exclude-standard

# Remove the unwanted files: 
git ls-files -ci --exclude-standard -z | xargs -0 git rm --cached