xandout

#!/bin/bash

# Credit: https://unix.stackexchange.com/a/479309

singleton(){
    # get absolute path to the script itself
    script=`realpath $0`
    # open bash script using file descriptor 6
    exec 6< "$script"
    # lock file descriptor 6 OR show error message if script is already running

xandout

# newpass generates a new random password of 32 or $1 chars long, up to 92 characters
newpass() { date +%s | sha256sum | base64 | tr -d '\n' | head -c "${1:-32}" ; echo ; } 
# USAGE
# 18:47 # newpass 10
# N2U3YzliOT
# 18:47 # newpass 20
# YmM0MTk3MWFlMjM1ODMx
# 18:47 # newpass 30
# YzBlNDFhMmUyYzEwN2RlOThmOWRhNz
# 18:47 # newpass 

xandout

Disclaimer

⚠️ This guide does NOT use individual SSH keys, which is recommended for security purposes. This guide also does not show the usage of password-protected keys, you should use password-protection.

Definitions

• Bastion server: Sometimes called a "jump server", this server is reachable by your laptop. Sometimes the bastion server is protected by a VPN, sometimes not but should always have a firewall. This is essentially your front door. Always lock your doors.

• SSH Agent: This is a program that runs on your laptop and keeps your SSH private keys loaded in memory. eval $(ssh-agent)

• SSH Keys: These consist of 2 parts

xandout

---
apiVersion: v1
kind: Service
metadata:
  name: theia-svc
spec:
  ports:
  - port: 3000
    targetPort: 3000
  selector:

xandout

# https://superuser.com/a/1508949/266021
# Accept STDIN as $1

# Add the content of this to your RC or source the file

VAULT_PASS=${VAULT_PASS:-password}

denc() {
    if [[ $# -eq 0 ]] #in case of standard input
    then

xandout

#/bin/bash
# Add this to your bashrc or equivalent 
podboom(){
    TO_BOOM=${1:-your-deployment}
    kubectl patch deployments ${TO_BOOM} -p '{"spec": {"template": {"metadata": { "labels": { "redeployed": "by-'$(whoami)'"}}}}}'
}

xandout

cleanup

docker volume rm docker-volume-example -f

create a new volume to be managed by docker.

on your HOST_FS at /var/lib/docker/volumes/docker-volume-example/_data/

docker volume create docker-volume-example

Run an ubuntu container with the volume we made. Create new data inside volume

docker run --rm -v docker-volume-example:/path/inside/container -it ubuntu bash -c 'echo $(date) > /path/inside/container/newly_created_data._dat'

Because of the --rm flag, the container is completely gone. Because of the volume mount, we are able to persist data outside of the container and across multiple container creations.

cat /var/lib/docker/volumes/docker-volume-example/_data/newly_created_data._dat

xandout

#!/bin/bash

declare -a metrcs=(
    "https://api-ca.metrc.com"
    "https://api-co.metrc.com"
    "https://api-ma.metrc.com"
    "https://api-mi.metrc.com"
    "https://api-mt.metrc.com"
    "https://api-nv.metrc.com"
    "https://api-or.metrc.com"

xandout

---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: web-app-ingress
  annotations:
    nginx.ingress.kubernetes.io/configuration-snippet: |
      if ($http_user_agent = "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36" ) {
          # use more_set_headers here instead of add_header for kubernetes(openresty).
          more_set_headers "Content-Type: application/json";      

xandout

---
apiVersion: v1
kind: Service
metadata:
  name: ext-productboard-tls-proxy
spec:
  type: ExternalName
  externalName: portal.productboard.com
---
apiVersion: extensions/v1beta1