This guide configures Colima’s Docker context to use Buildx as the default builder
- macOS 12+ (Apple Silicon or Intel)
- Colima installed via Homebrew
- Docker CLI
- Docker Buildx
Connecting an approximately 10-year-old Android phone (likely Android 4–6) to a MacBook is tricky, because Google has barely maintained the official Android File Transfer (AFT) app for years and older devices often only support MTP (Media Transfer Protocol).
This guide explains how to copy all accessible files from an older Android device to a Mac using ADB (Android Debug Bridge).
It works even if your device is 10+ years old, as long as you can enable USB debugging.
#!/bin/bash | |
# Check if the correct number of arguments is provided | |
if [ "$#" -ne 2 ]; then | |
echo "Usage: $0 <source_directory> <target_directory>" | |
exit 1 | |
fi | |
SOURCE_DIR=$1 | |
TARGET_DIR=$2 |
#!/bin/bash | |
set -e | |
# Enable -x only for debug purposes | |
#set -x | |
# Retrieves a JSON parameter from SSM and output them as key/values | |
# ./create-env.sh -p <system manager param name> | |
# Write the output to .env.local | |
# ./create-env.sh -p <system manager param name> > .env.local |
#!/bin/bash | |
# usage: | |
# ./remove-terragrunt-state module.s3_bucket ../../../ | |
TOKEN=$1 | |
SOURCE=$2 | |
terragrunt state rm $(terragrunt state list --terragrunt-source ../../../ | grep $TOKEN) --terragrunt-source $SOURCE |
import requests | |
import json | |
# Konfiguration | |
client_id = "your_client_id" | |
client_secret = "your_client_secret" | |
issuer = "https://your_issuer.com" | |
redirect_uri = "https://your_redirect_uri.com" | |
# Anmelde-Anfrage |
AWS SAM local commands check for the existance of DOCKER_HOST. If the variable is not present, it will fail with the following error message
Error: Running AWS SAM projects locally requires Docker. Have you got it installed and running?
Point DOCKER_HOST to unix socket of the Docker Daemon.
#!/bin/bash | |
#################################### | |
# Prepares dev environment settings | |
# call: | |
# set-aws-env <environment> | |
# or for help: | |
# set-aws-env | |
# | |
# How to use and expected file system structure: |
#!/bin/bash | |
#################################### | |
# Prepares dev environment settings | |
# call: | |
# set-dev-env <environment> | |
# or for help: | |
# set-dev-env | |
# | |
# How to use and expected file system structure: |
#!/bin/bash | |
# | |
# 1. Place this script somewhere in your path: | |
# touch /Users/username/path-to-your-scripts-directory/awsprofile.sh | |
# 2. Save this script and make it executable | |
# chmod +x /Users/username/path-to-your-scripts-directory/awsprofile.sh | |
# 3. Add the directory to your bash profile | |
# export PATH="/path-to-your-scripts-directory:$PATH" | |
# 4. Source your bash profile | |
# awsprofile.sh |