Asraful's Docs 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.

AI Tool Adoption Governance

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

AI Tool Adoption Governance#

Process, Policy & Standards Document — Version 1.0#

Field	Value
Document Owner	[CTO / Head of Engineering / AI Governance Lead]
Classification	Internal — Not for External Distribution
Version	1.0 — Initial Release
Effective Date	[DATE]
Review Frequency	Quarterly
Last Reviewed	[DATE]

Purpose: This document establishes the organization’s end-to-end process for evaluating, approving, deploying, and continuously governing artificial intelligence (AI) tools. It applies to all AI-powered software — including coding assistants, generative content tools, data-analysis platforms, and autonomous agents — used by employees, contractors, and third parties on behalf of the organization.

Architecture

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

Architecture#

New Mac Setup

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

New Mac Setup#

Use this workflow to configure a new Mac from scratch with the tools and shell environment needed for development and daily work.

Trigger#

Use this when setting up a new Mac or rebuilding a machine after a wipe.

Inputs#

Before starting, have:

A Mac with macOS up to date
An Apple ID signed in
Internet access
Your Microsoft 365 licence or account credentials
Your GitHub username and email address

1. Install Homebrew#

Homebrew is the package manager for everything else. Install it first.

With ToC

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

Caput vino delphine in tamen vias#

Cognita laeva illo fracta#

Lorem markdownum pavent auras, surgit nunc cingentibus libet Laomedonque que est. Pastor An arbor filia foedat, ne fugit aliter, per. Helicona illas et callida neptem est Oresitrophos caput, dentibus est venit. Tenet reddite famuli praesentem fortibus, quaeque vis foret si frondes gelidos gravidae circumtulit inpulit armenta nativum.

Te at cruciabere vides rubentis manebo
Maturuit in praetemptat ruborem ignara postquam habitasse
Subitarum supplevit quoque fontesque venabula spretis modo
Montis tot est mali quasque gravis
Quinquennem domus arsit ipse
Pellem turis pugnabant locavit

Natus quaerere#

Pectora et sine mulcere, coniuge dum tincta incurvae. Quis iam; est dextra Peneosque, metuis a verba, primo. Illa sed colloque suis: magno: gramen, aera excutiunt concipit.

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:

LLM Gateway

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

LLM Gateway#

Purpose#

Build a gateway layer that sits in front of one or more large language model APIs, providing a unified interface for routing, authentication, rate limiting, logging, and cost control.

Status#

Active

Goals#

Provide a single endpoint that abstracts multiple LLM providers (OpenAI, Anthropic, etc.)
Enforce API key management and per-consumer authentication
Track usage, costs, and latency per consumer and model
Support request routing rules (e.g. route by model name, fallback on error)
Enable rate limiting and budget caps per consumer

Scope#

Included#

HTTP proxy layer that accepts OpenAI-compatible requests
Provider adapters for at least Anthropic and OpenAI
Request and response logging with token counts
Per-consumer API key issuance and validation
Rate limiting and monthly spend caps
Admin interface or config file for managing consumers and rules

Not included#

Fine-tuning or model hosting
Training data management
End-user chat UI
Multi-region deployment (deferred)

Tasks#

Define the API contract (request/response schema)
Stand up a basic HTTP proxy that forwards to one provider
Add provider adapters (Anthropic, OpenAI)
Implement consumer key management
Add request logging with token and cost tracking
Add rate limiting per consumer
Add budget cap enforcement
Write admin config or dashboard
Document the setup and deployment steps
Test with real traffic

Links and files#

Repository: https://github.com/asrafuli/gato
Docs:
Notes:
Related workflow:
Related how-to:

Decisions#

Date	Decision	Reason
2026-05-10	Start with OpenAI-compatible request schema	Maximises compatibility with existing tooling

Outcome#

A running gateway service that proxies LLM requests
Per-consumer usage reports
Documentation covering setup, configuration, and adding new providers

Notes#

Capture rough notes, lessons, and things to remember.

Security Considerations

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

Security Considerations#

Without ToC

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

At me ipso nepotibus nunc celebratior genus#

Tanto oblite#

Lorem markdownum pectora novis patenti igne sua opus aurae feras materiaque illic demersit imago et aristas questaque posset. Vomit quoque suo inhaesuro clara. Esse cumque, per referri triste. Ut exponit solisque communis in tendens vincetis agisque iamque huic bene ante vetat omina Thebae rates. Aeacus servat admonitu concidit, ad resimas vultus et rugas vultu dignamque Siphnon.

Quam iugulum regia simulacra, plus meruit humo pecorumque haesit, ab discedunt dixit: ritu pharetramque. Exul Laurenti orantem modo, per densum missisque labor manibus non colla unum, obiectat. Tu pervia collo, fessus quae Cretenque Myconon crate! Tegumenque quae invisi sudore per vocari quaque plus ventis fluidos. Nodo perque, fugisse pectora sorores.

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:

Static Website to GitHub and Azure

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

Static Website to GitHub and Azure#

Use this workflow to start a new static website on a Mac, create a GitHub repository, push the code, and deploy it to Azure from GitHub.

Trigger#

Use this when starting a small website, documentation site, landing page, or static frontend that should be hosted online.

Inputs#

Before starting, have:

A Mac with Terminal access
A GitHub account
An Azure account
A project name
A rough idea of the first page

Recommended tools:

Automated Note Publishing Workflow

Sat, 16 May 2026 00:00:00 +0000

Overview#

An end-to-end pipeline that takes meeting notes from Granola and publishes them as dated markdown entries to a static website — with minimal manual effort.

Integration chain: Granola → Telegram → OpenClaw → GitHub → Azure

How It Works#

Step	Tool	Role
1	Granola	Generates meeting summaries from transcripts
2	Telegram	Receives notes with a processing instruction
3	OpenClaw	Watches the channel, creates dated markdown files
4	GitHub	Stores the generated files in a repository
5	Azure Static Website	Auto-deploys on every repository push

Technical Implementation#

OpenClaw#

Monitors a specific Telegram channel
Triggers on the instruction phrase: "go ahead and create an entry"
Generates markdown files with date stamps
Pushes directly to the connected GitHub repository

GitHub + Azure#

Repository is linked to an Azure Static Website deployment
Every push triggers an automatic redeploy
No manual publishing step required

Version 1 Scope#

This first iteration keeps things simple and focused on getting the pipeline working end-to-end:

I Let an AI Agent Loose on My Mac. Here's What Happened.

Sat, 16 May 2026 00:00:00 +0000

A cautionary tale, a second chance, and a 13-year-old iMac that found its purpose.

I didn’t do much research. A friend said it was good, built by a single developer, and worth trying. So I downloaded OpenClaw, clicked through a security warning that I probably should have taken more seriously, and installed it directly on my main Mac.

My first question was simple: “What can you do?”

It told me it could manage email, calendars, and system settings. Impressive. So I pushed a little further — “Can you update Docker?”

OpenClaw

Fri, 01 May 2026 00:00:00 +0000

My OpenClaw Journey: From Friction to Flow#

When I started using OpenClaw seriously, I wanted one thing: an assistant that could actually do work with me, not just talk about it.

Real Problems, Real Fixes#

One of my most practical wins was fixing Wi‑Fi on an older 2013 Intel Mac running Linux. I hit a nasty Broadcom + DKMS dependency conflict, tracked it down to a repo/version mismatch, and got Wi‑Fi working again by pinning the right kernel (6.8.0-111-generic) and locking the driver/toolchain to prevent future breakage.

AI Hackathon Facilitation Guide

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

AI Hackathon Facilitation Guide#

An internal AI hackathon is one of the most effective ways to generate practical use cases, upskill employees, encourage cross-functional collaboration, identify prototypes worth production investment, and build excitement around AI adoption.

Process#

1. Define the Purpose#

Start by answering one question: What outcome do we want from this hackathon?

Focus	Goals
Innovation	Discover new AI-powered product ideas, explore internal process automation
Learning	Teach employees how to use LLMs and AI tools
Business Impact	Reduce costs, improve productivity, enhance customer experience
Talent	Identify employees with strong AI skills

Recommended goal:

Capture a Workflow

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

Capture a Workflow#

Use this template when documenting how you handle a repeatable activity.

Workflow name#

Give the workflow a clear name.

Examples:

Publish a new blog post
Debug a broken local dev server
Review AI tool subscriptions
Plan a weekly work session

Trigger#

Describe when this workflow starts.

Example:

I use this workflow when I need to turn scattered notes into a published document.

Inputs#

List what you need before starting:

Project Template

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

Project Template#

Use this page as a starting point for new projects.

Purpose#

Describe why this project exists.

Example:

Build a repeatable documentation system for personal tools, workflows, and technical notes.

Status#

Choose one:

Planned
Active
Paused
Completed
Archived

Current status:

Active

Goals#

List the outcomes that matter most.

Goal 1
Goal 2
Goal 3

Scope#

Included#

What this project will cover
What files, tools, or systems are involved
What success looks like

Not included#

Work that belongs somewhere else
Ideas to save for later
Things that are intentionally out of scope

Tasks#

Use this as the working checklist.

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.

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

Asciinema#

Asciinema shortcode integrates asciinema player into the markdown page.

{{< asciinema
 cast="asciinema-627097.cast"
 or
 cast="https://asciinema.org/a/vJNKUQFjuh7qKI2j3OoaKs8Jk.cast"
 loop=true
 autoplay=true
 speed=2 >}}

Parameters#

All parameters added to the shortcode will be transformed to options for Asciinema player, expect cast parameter that is used to locate cast file. Cast file follows same rules as portable image, it could be site resource, page resource or remote file URL.

List of Asciinema options

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

Buttons#

Buttons are styled links that can lead to local page or external link.

Example#

{{< button relref="/" [class="..."] >}}Get Home{{< /button >}}
{{< button href="https://github.com/alex-shpak/hugo-book" >}}Contribute{{< /button >}}

Get Home Contribute

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

Caesorum illa tu sentit micat vestes papyriferi#

Inde aderam facti; Theseus vis de tauri illa peream. Oculos uberaque non regisque vobis cursuque, opus venit quam vulnera. Et maiora necemque, lege modo; gestanda nitidi, vero? Dum ne pectoraque testantur.

Venasque repulsa Samos qui, exspectatum eram animosque hinc, aut manes, Assyrii. Cupiens auctoribus pariter rubet, profana magni super nocens. Vos ius sibilat inpar turba visae iusto! Sedes ante dum superest extrema.

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

Columns#

Columns help organize shorter pieces of content horizontally for readability. columns shortcode styles markdown list as up to 3 columns.

Example#

{{% columns [ratio="1:1"] [class="..."] %}}
- ### Left Content
 Lorem markdownum insigne...

- ### Mid Content
 Lorem markdownum insigne...

- ### Right Content
 Lorem markdownum insigne...
{{% /columns %}}

Left Content#

Lorem markdownum insigne. Olympo signis Delphis! Retexi Nereius nova develat stringit, frustra Saturnius uteroque inter! Oculis non ritibus Telethusa protulit, sed sed aere valvis inhaesuro Pallas animam: qui quid, ignes. Miseratus fonte Ditis conubia.

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

Details#

Details shortcode is a helper for details html5 element. To collapse the details either omit the open keyword when using positional arguments or set open=false when using parameters.

Example with positional arguments#

{{% details "Title" [open] %}}
## Markdown content
Lorem markdownum insigne...
{{% /details %}}

Markdown content#

Lorem markdownum insigne…

Example with parameters#

{{% details title="Title" open=true %}}
## Markdown content
Lorem markdownum insigne...
{{% /details %}}

Markdown content#

Lorem markdownum insigne…

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

Badges#

Experimental, could change in the future or be removed

Badges can be used to annotate your pages with additional information or mark specific places in markdown content.

TitleValue Hugo0.147.6 BuildPassing Coverage25% Issues120

Examples#

Shortcode	Output
`{{< badge style="info" title="hugo" value="0.147.6" >}}`	Hugo0.147.6
`{{< badge style="success" title="Build" value="Passing" >}}`	BuildPassing
`{{< badge style="warning" title="Coverage" value="25%" >}}`	Coverage25%
`{{< badge style="danger" title="Issues" value="120" >}}`	Issues120

`{{< badge style="info" title="Title" >}}`	Title
`{{< badge style="info" value="Value" >}}`	Value
`{{< badge title="Default" >}}`	Default

Use in links#

A badge can be wrapped in markdown link producing following result: Hugo0.147.6

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

Cards#

Experimental, could change in the future or be removed

Example#

Line 1#

Line 2
This is tab MacOS content.

Markdown
Suspendisse sed congue orci, eu congue metus. Nullam feugiat urna massa.

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

Images#

Experimental, could change in the future or be removed

Image shortcode produces an image that can be clicked to expand.

Example#

{{< image src="placeholder.svg" alt="A placeholder" title="A placeholder" loading="lazy" >}}

Parameters#

src Required: The link to the image
class Optional: An optional CSS class name that will be applied to the img element
alt Optional: An optional alternate text for the image
title Optional: An optional title for the image
loading Optional: Sets loading control for the image: lazy, eager or auto

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

Quondam non pater est dignior ille Eurotas#

Latent te facies#

Lorem markdownum arma ignoscas vocavit quoque ille texit mandata mentis ultimus, frementes, qui in vel. Hippotades Peleus pennas conscia cuiquam Caeneus quas.

Pater demittere evincitque reddunt
Maxime adhuc pressit huc Danaas quid freta
Soror ego
Luctus linguam saxa ultroque prior Tatiumque inquit
Saepe liquitur subita superata dederat Anius sudor

Cum honorum Latona#

O fallor in sustinui iussorum equidem. Nymphae operi oris alii fronde parens dumque, in auro ait mox ingenti proxima iamdudum maius?

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

Hints#

Hint shortcode can be used as a hint/alert/notification block.

{{% hint [info|success|warning|danger] %}}
**Markdown content** 
Lorem markdownum insigne. Olympo signis Delphis! Retexi Nereius nova develat
stringit, frustra Saturnius uteroque inter! Oculis non ritibus Telethusa
{{% /hint %}}

> [!NOTE|TIP|IMPORTANT|WARNING|CAUTION]
> **Markdown content** 
> Lorem markdownum insigne. Olympo signis Delphis! Retexi Nereius nova develat
> stringit, frustra Saturnius uteroque inter! Oculis non ritibus Telethusa

Example#

Markdown content
Lorem markdownum insigne. Olympo signis Delphis! Retexi Nereius nova develat stringit, frustra Saturnius uteroque inter! Oculis non ritibus Telethusa

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

Mermaid Chart#

MermaidJS is library for generating svg charts and diagrams from text.

Override Mermaid initialization config
To override the initialization config for Mermaid, create a mermaid.json file in your assets folder!

Example#

```mermaid
stateDiagram-v2
 State1: The state with a note
 note right of State1
 Important information! You can write
 notes.
 end note
 State1 --> State2
 note left of State2 : This is the note to the left.
```

stateDiagram-v2
 State1: The state with a note
 note right of State1
 Important information! You can write
 notes.
 end note
 State1 --> State2
 note left of State2 : This is the note to the left.

{{< mermaid [class="..."] >}}
stateDiagram-v2
 State1: The state with a note
 note right of State1
 Important information! You can write
 notes.
 end note
 State1 --> State2
 note left of State2 : This is the note to the left.
{{< /mermaid >}}

Diagrams#

Explore more diagrams and syntax on Mermaid documentation page.

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

First page#

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

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

Second Page#

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

Steps#

Steps shortcode styles numbered list as series of points for better content organization.

{{% steps %}}
1. ## Suspendisse sed congue orci.
 ...

2. ## Maecenas scelerisque sem.
 ...

3. ## Etiam risus purus.
 ...

4. ## Curabitur sed lacinia velit.
 ...
{{% /steps %}}

Example#

Suspendisse sed congue orci.#

Suspendisse sed congue orci, eu congue metus. Nullam feugiat urna massa, et fringilla metus consectetur molestie. Curabitur pellentesque sodales ipsum, sed efficitur libero euismod ac. Donec sit amet erat nunc. Suspendisse porta nisl velit, quis auctor massa commodo nec. Donec sollicitudin tellus sit amet massa condimentum luctus. Etiam molestie at ante et convallis.

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

Tabs#

Tabs let you organize content by context, for example installation instructions for each supported platform.

{{< tabs >}}
{{% tab "MacOS" %}} # MacOS Content {{% /tab %}}
{{% tab "Linux" %}} # Linux Content {{% /tab %}}
{{% tab "Windows" %}} # Windows Content {{% /tab %}}
{{< /tabs >}}

Example#

MacOS

MacOS#

This is tab MacOS content.

Lorem markdownum insigne. Olympo signis Delphis! Retexi Nereius nova develat stringit, frustra Saturnius uteroque inter! Oculis non ritibus Telethusa protulit, sed sed aere valvis inhaesuro Pallas animam: qui quid, ignes. Miseratus fonte Ditis conubia.

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

Asciinema#
Badge#

TitleValue
Button#

A Button
Card#

Markdown
Suspendisse sed congue orci, eu congue metus. Nullam feugiat urna massa.
Details#

Markdown content#

Lorem markdownum insigne…

Installation

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

OpenClaw Setup on Ubuntu#

This guide covers the simplest supported way to install OpenClaw on Ubuntu.

Recommended Ubuntu versions#

Ubuntu 22.04 LTS

A clean Ubuntu LTS install is preferred.

Requirements#

Internet access
A user account with sudo access
curl installed

OpenClaw requires Node 24 (recommended) or Node 22.14+, but the installer handles Node automatically.

Option 1: Recommended installer script#

Run:

curl -fsSL https://openclaw.ai/install.sh | bash

What this does:

Detects your OS
Installs Node if needed
Installs OpenClaw
Launches onboarding

If you want to install without starting onboarding immediately:

KaTeX

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

KaTeX#

KaTeX shortcode let you render math typesetting in markdown document. See KaTeX

Override KaTeX initialization config
To override the initialization config for KaTeX, create a katex.json file in your assets folder!

Example#

Activation#

KaTeX is activated on the page by first use of the shortcode or render block. you can force activation with empty {{< katex />}} and use delimiters defined in configuration in assets/katex.json.

Showcases

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

At the moment this page is empty#