Mike Wu nouse

Moved to git repository: https://github.com/denji/golang-tls

Generate private key (.key)

# Key considerations for algorithm "RSA" ≥ 2048-bit
openssl genrsa -out server.key 2048

# Key considerations for algorithm "ECDSA" ≥ secp384r1
# List ECDSA the supported curves (openssl ecparam -list_curves)

EDIT from 2019: Hi folks. I wrote this gist for myself and some friends, and it seems like it's gotten posted somewhere that's generated some (ahem, heated) discussion. ~~The whitespace was correct when it was posted, and since then GitHub changed how it formats <pre> tags. Look at the raw text if you care about this. I'm sure someone could tell me how to fix it, but~~ (thank you @anzdaddy for suggesting a formatting workaround) honestly this is a random throwaway gist from 2015, and someone more knowledgable about this comparison should just write a proper blog post about it. If you comment here I'll hopefully see it and stick a link to it up here. Cheers. @oconnor663

Here's the canonical TOML example from the TOML README, and a YAML version of the same.

title = "TOML Example"

Learning FP the hard way: Experiences on the Elm language

by Ossi Hanhinen, @ohanhi

with the support of Futurice 💚.

Licensed under CC BY 4.0.

Editorial note

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.

	---
	<%
	deployment_name = "cf"
	director_uuid = "CHANGE-ME"
	vip_ip = "CHANGE-ME"
	root_domain = "#{vip_ip}.xip.io"
	common_password = "c1oudc0w"
	%>
	ssl_pem: &ssl_pem \|
	-----BEGIN CERTIFICATE-----

	# Copy that into your ~/.config/fish/config.fish

	function ssh
	set ps_res (ps -p (ps -p %self -o ppid= \| xargs) -o comm=)
	if [ "$ps_res" = "tmux" ]
	tmux rename-window (echo $argv \| cut -d . -f 1)
	command ssh "$argv"
	tmux set-window-option automatic-rename "on" 1>/dev/null
	else
	command ssh "$argv"

	# This file is licensed under the terms of the MIT license https://opensource.org/license/mit
	# Copyright (c) 2021-2025 Marat Reymers

	## Golden config for golangci-lint v2.1.5
	#
	# This is the best config for golangci-lint based on my experience and opinion.
	# It is very strict, but not extremely strict.
	# Feel free to adapt it to suit your needs.
	# If this config helps you, please consider keeping a link to this file (see the next comment).