bard86

Restore intentionally deleted commits in Git (remote)

Situation

1. You own a Git repository server and the developers do not have access to it (i.e. they can only read & write to the repo, but not gc it).
2. You had a developer that wrote a project for you.
3. He got angry for whatever reason and deleted all branches from the remote repo. He also push -fed the master branch leaving only one silly commit there.
4. He escaped from the country leaving you without any code at all (at least this is what he believe in).
5. You have never cloned the repo to other machine. There were only two copies of it: the developer's one and the server's one.

bard86

docker images --format "{{.Repository}}:{{.Tag}}" | grep -v "none"

bard86

alias dc='docker-compose'

bard86

apt update
apt install git
apt install iputils-ping
apt install net-tools
apt install telnet

curl -L "https://github.com/docker/compose/releases/download/1.25.5/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose
ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose

bard86

docker volume create --name squidVolume
docker run --name squid -d -p 3128:3128 -v squidVolume:/var/spool/squid Datadog/squid

bard86

# Find process running on port 8080
lsof -i:8080

# Just kill it
kill -9 $(lsof -t -i:8080)


# find process listening on port 9200
lsof -nP -i4TCP:$PORT | grep LISTEN

bard86

#!/bin/bash
set -e
set -o pipefail

# Add user to k8s using service account, no RBAC (must create RBAC after this script)
if [[ -z "$1" ]] || [[ -z "$2" ]]; then
 echo "usage: $0 <service_account_name> <namespace>"
 exit 1
fi

bard86

Про токены, JSON Web Tokens (JWT), аутентификацию и авторизацию. Token-Based Authentication

Last major update: 25.08.2020

• Что такое авторизация/аутентификация
• Где хранить токены
• Как ставить куки ?
• Процесс логина
• Процесс рефреш токенов
• Кража токенов/Механизм контроля токенов

bard86

OpenJDK 11+ on MacOS X

Manually downloading, extracting and configuring the installation of OpenJDK 11+ is a high-maintenance exercise. Particularly if you need to install and switch between multiple versions of the JDK.

The following options for installing OpenJDK 11+ and switching between versions make the job easier..

Install with Jabba

Jabba is a Java version manager inspired by nvm (Node.js) written in Go.

bard86

Built-in

diskutil erasevolume HFS+ 'RAM Disk' `hdiutil attach -nobrowse -nomount ram://XXXXX`

where XXXXX is the size of the RAM disk in terms of memory blocks.

Notes: