Using adb, create a backup of the app using the following command:
adb backup -f freeotp-backup.ab -apk org.fedorahosted.freeotp
# Documentation: https://docs.brew.sh/Formula-Cookbook | |
# https://rubydoc.brew.sh/Formula | |
# PLEASE REMOVE ALL GENERATED COMMENTS BEFORE SUBMITTING YOUR PULL REQUEST! | |
class Sdrangel < Formula | |
desc "" | |
homepage "" | |
url "https://github.com/f4exb/sdrangel/archive/refs/tags/v7.15.4.tar.gz" | |
sha256 "990528f539c8e21f9af88c4c41adc69135ce6fc04298ac6dd4406a417ebd485d" | |
license "" |
#!/usr/bin/env bash | |
source .env | |
# export PROJECT_ID=<from .env> | |
# export AUTH_NETWORK=<from .env> | |
export GCP_REGION=us-central1 | |
export GCP_ZONE=us-central1-b | |
export CLUSTER_VERSION="1.16.13-gke.1" |
blueprint: | |
name: HA start Notify Telegram | |
description: Notify telegram that Home Assistant has successfully started | |
domain: automation | |
source_url: https://gist.github.com/ask0n/ece5696165f95346d8683dd86ced4071 | |
input: | |
notification_title: | |
name: Notification title (Optional) | |
description: 'Default: "My Home Assistant"' | |
default: My Home Assistant |
# Advanced Bash :: Array slicing and compaction in bash | |
# TL;DR | |
X=(something 'whatever' "i have more S P A C E S than i can give away. arent you jealous?") | |
# ${X[@]} the usual whole array | |
# ${X[@]:index:length} slice from index to index+length-1 inclusive | |
# ${X[@]::length} slice from 0 to length-1 inclusive | |
# ${X[@]:index} slice from index to end of array inclusive |
# setup go | |
curl -sS https://storage.googleapis.com/golang/go1.8.1.linux-amd64.tar.gz | tar zxf - -C /usr/local | |
export PATH=/usr/local/go/bin:$HOME/go/bin:$PATH | |
yum install -y make git | |
# setup go-carbon | |
go get -d github.com/lomik/go-carbon | |
cd $HOME/go/src/github.com/lomik/go-carbon |
Using adb, create a backup of the app using the following command:
adb backup -f freeotp-backup.ab -apk org.fedorahosted.freeotp
# Notes: | |
# You'll need to update any references to 'module.vpc' with your VPC's info (subnets, security groups, etc) | |
# If you define your subnets as a map, this will deploy different replicas across availabity zones. Note | |
# that the master and first replica will be in the same AZ. | |
# | |
# Look through the 'connection' fields and update with your bastion_host/key combos | |
# | |
# Number of IPA Replica(s) to deploy | |
variable "ipa_replicas" { |
# ssh key generator data source expects the below 3 inputs, and produces 3 outputs for use: | |
# "${data.external.ssh_key_generator.result.public_key}" (contents) | |
# "${data.external.ssh_key_generator.result.private_key}" (contents) | |
# "${data.external.ssh_key_generator.result.private_key_file}" (path) | |
data "external" "ssh_key_generator" { | |
program = ["bash", "${path.root}/../ssh_key_generator.sh"] | |
query = { | |
customer_name = "${var.customer_name}" | |
customer_group = "${var.customer_group}" |
brew install git bash-completion
Configure things:
git config --global user.name "Your Name"
git config --global user.email "you@example.com"
To make use of the Nginx ingress controller your Kubernetes environment must be configured to have the Rancher ingress controller disabled (Enable Rancher Ingress Controller
should be false).
The Nginx ingress controller must be deployed before launching any ingresses. The recommended way of doing this is via Helm.
helm install stable/nginx-ingress