alexanderdavidsen

#!/usr/bin/env bash

# Colors
BLUE='\033[0;34m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
RED='\033[0;31m'
NC='\033[0m' # No Color
BOLD='\033[1m'

luigiMinardi

Small warning for everyone that are thinking if using Tex colors is a good idea or not

• 2023-05-02 - Since a few days ago \colorbox and \fcolorbox are broken and Github did't talk about if it's a temporary thing or if it will not be added back.
  • 2024-01-04 - Since it has not being added back I deduce that it will never be so I removed all mentions to it on the rest of the gist.
• 2023-09-29 - Tex seems to not work on h1 to h6 anymore (markdown #'s)
  • 2024-01-04 - Now it works again, I'll keep the message for a while to remember that it may change again in the future

As you can se with the above message(s) Tex may not be very stable and may not be an option to you as of the dates expressed above. You can also check other tex problems here.

Github released Tex support and colors* to the markdown and you din't realized

scottrigby

Introduction to GitOps & The Flux Family of Projects

Set up local cluster and Flux CLI

1. Install Flux CLI and Kind:

   $ brew reinstall flux kind
   $ kind --version
   kind version 0.11.1

scottrigby

Hands-On GitOps Patterns for Helm Users

1. Install Flux CLI and Kind:

   $ brew reinstall flux kind
   $ kind --version
   kind version 0.10.0
   $ flux --version
   flux version 0.9.1

diafour

#!/usr/bin/env bash

# A helper for kind to create and delete clusters with untrusted local registry.
# Based on https://kind.sigs.k8s.io/docs/user/local-registry/
#
# Note: kind 0.10.0

# Settings for kind cluster
CLUSTER_NAME="kube-19"
KIND_NODE_IMAGE="kindest/node:v1.19.7"

kmcquade

• chime:CreateApiKey
• codepipeline:PollForJobs
• cognito-identity:GetOpenIdToken
• cognito-identity:GetOpenIdTokenForDeveloperIdentity
• cognito-identity:GetCredentialsForIdentity
• connect:GetFederationToken
• connect:GetFederationTokens
• ecr:GetAuthorizationToken
• [gamelift:RequestUploadCredentials](ht

AlainODea

resource "aws_ami_copy" "ubuntu-18_04-encrypted" {
  name              = "${data.aws_ami.ubuntu-18_04.name}-encrypted"
  description       = "${data.aws_ami.ubuntu-18_04.description} (encrypted)"
  source_ami_id     = "${data.aws_ami.ubuntu-18_04.id}"
  source_ami_region = "${var.region}"
  encrypted         = true

  tags {
    ImageType      = "encrypted-ubuntu-18_04"
  }

mohanpedala

Table of Contents

• set -e, -u, -x, -o pipefail
• set -e
• set -x
• set -u
• set -o pipefail
• Setting IFS
• Original Reference

set -e, -u, -x, -o pipefail

vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

zenorocha

Project Name

TODO: Write a project description

Installation

TODO: Describe the installation process

Usage