How To on My Random Docs

Adding Authentication to Azure Static Web Apps (Hugo)

Mon, 01 Jan 0001 00:00:00 +0000

Adding Authentication to Azure Static Web Apps (Hugo)#

This guide covers how to lock your Hugo site behind a login using Azure Static Web Apps (SWA) built-in authentication, and restrict access to selected users only.

Prerequisites#

Hugo site deployed to Azure Static Web Apps via GitHub Actions
Azure account with your Static Web App resource provisioned
static/staticwebapp.config.json file in your Hugo project

How It Works#

Azure SWA handles authentication at the infrastructure level — no backend code required. The staticwebapp.config.json file controls which routes are protected and which identity provider handles login.

Keep Track of Mac Installation

Mon, 01 Jan 0001 00:00:00 +0000

Mac Installation Logging Guide#

A simple reference for tracking everything installed on your Mac, saved to a plain text file.

1. Script-Based Logging (Recommended)#

Wrap your package managers with a logging function. Add this to your ~/.zshrc or ~/.bashrc:

# Installation Logger
INSTALL_LOG="$HOME/install_log.txt"

log_install() {
 echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*" >> "$INSTALL_LOG"
}

# Wrap brew
brew() {
 command brew "$@"
 if [[ "$1" == "install" ]]; then
 log_install "brew install ${@:2}"
 fi
}

# Wrap pip
pip() {
 command pip "$@"
 if [[ "$1" == "install" ]]; then
 log_install "pip install ${@:2}"
 fi
}

# Wrap pip3
pip3() {
 command pip3 "$@"
 if [[ "$1" == "install" ]]; then
 log_install "pip3 install ${@:2}"
 fi
}

# Wrap npm global installs
npm() {
 command npm "$@"
 if [[ "$1" == "install" && ("$2" == "-g" || "$2" == "--global") ]]; then
 log_install "npm install ${@:2}"
 fi
}

After adding, run source ~/.zshrc. Every install will append to ~/install_log.txt like:

KubeEdge Setup Guide

Mon, 01 Jan 0001 00:00:00 +0000

KubeEdge Setup Guide#

A complete hands-on guide to setting up a KubeEdge cloud-edge environment, managing IoT devices, and troubleshooting common issues.

Prerequisites#

Ensure you have the required tools installed before starting:

# Verify required tools
docker --version
kubectl version --client
go version # Optional, for building from source

You will need:

A Kubernetes cluster (cloud side)
Ubuntu/CentOS machines for edge nodes
Network connectivity between cloud and edge

Step 1: Prepare Your Environment#

# Set up environment variables
export KUBEEDGE_VERSION=v1.18.0
export CLOUD_MASTER_IP=<your-k8s-master-ip>
export EDGE_NODE_NAME=edge-node-01

# Clean up any previous installations
sudo systemctl stop edgecore 2>/dev/null || true
sudo systemctl stop cloudcore 2>/dev/null || true

Step 2: Install CloudCore (Cloud Side)#

# Download and install keadm
curl -L https://github.com/kubeedge/kubeedge/releases/download/${KUBEEDGE_VERSION}/keadm-${KUBEEDGE_VERSION}-linux-amd64.tar.gz | tar xz
sudo mv keadm-${KUBEEDGE_VERSION}-linux-amd64/keadm/keadm /usr/local/bin/

# Initialize CloudCore on your Kubernetes cluster
sudo keadm init \
 --advertise-address=${CLOUD_MASTER_IP} \
 --kubeedge-version=${KUBEEDGE_VERSION}

# Verify CloudCore is running
kubectl get pods -n kubeedge

Step 3: Get Token for Edge Nodes#

# Generate token for edge node registration
sudo keadm gettoken

# Output will look like:
# 27a37ef16159f7d3be8fae95d588b79b3adaaf92727b72659eb89758c66ffda2.eyJh...

Step 4: Join Edge Node#

Run the following on your edge machine:

Write a How-To Guide

Mon, 01 Jan 0001 00:00:00 +0000

Write a How-To Guide#

Use this template whenever you want to document a task you may need to repeat.

Goal#

Describe the result in one sentence.

Example:

Install a tool, confirm it runs, and record the commands needed to update it later.

Requirements#

List anything needed before starting:

Operating system or device
Required app or CLI tool
Account access
Existing files or configuration
Network or permission requirements

Steps#

Write the steps in the order you would actually run them.