### Download Pocket ID Environment File

Source: https://pocket-id.org/docs/setup/installation

Downloads the example environment configuration file (.env) for Pocket ID from the GitHub repository.

```bash
curl -o .env https://raw.githubusercontent.com/pocket-id/pocket-id/main/.env.example
```

--------------------------------

### Start Pocket ID Portal Development Server

Source: https://github.com/pocket-id/pocket-id-portal

Runs the SvelteKit development server for the Pocket ID Portal. This command starts the local server, making the application accessible for development and testing, typically at http://localhost:5173.

```Shell
npm run dev
```

--------------------------------

### Create Environment Configuration File

Source: https://github.com/pocket-id/pocket-id-portal

Copies the example environment file (.env.example) to create a new .env file. This file will be used to store sensitive configuration details and API keys for the application.

```shell
cp .env.example .env
```

--------------------------------

### Start Pocket ID Portal Development Server

Source: https://github.com/pocket-id/pocket-id-portal

This command initiates the development server for the Pocket ID Portal, making it accessible locally. The portal will typically be available at http://localhost:5173. It's a standard npm script for starting web applications.

```shell
npm run dev
```

--------------------------------

### Install kubelogin via Package Managers

Source: https://github.com/int128/kubelogin

Instructions for installing the `kubelogin` plugin using various package managers like Homebrew (macOS/Linux), Krew (Kubernetes plugin manager for macOS/Linux/Windows/ARM), and Chocolatey (Windows). These commands simplify the setup process.

```shell
brew install kubelogin
```

```shell
kubectl krew install oidc-login
```

```shell
choco install kubelogin
```

--------------------------------

### Run Pocket ID from Source Build

Source: https://pocket-id.org/docs/setup/installation

Executes the Pocket ID binary after building it from source.

```bash
./pocket-id
```

--------------------------------

### Build Pocket ID from Source

Source: https://pocket-id.org/docs/setup/installation

Comprehensive steps to clone, checkout, build the frontend (Node.js/npm), build the backend (Go), and prepare the environment file for Pocket ID from its source code.

```bash
# Clone the repo
git clone https://github.com/pocket-id/pocket-id
cd pocket-id
# Checkout latest version
git fetch --tags && git checkout $(git describe --tags `git rev-list --tags --max-count=1`)
# Build the frontend
cd frontend
npm ci
npm run build
# Build the backend
cd ../backend/cmd
go build -o ../../pocket-id
# Create the .env file
cd ../../
cp .env.example .env
```

--------------------------------

### Run Stand-alone Pocket ID Binary

Source: https://pocket-id.org/docs/setup/installation

Executes the Pocket ID binary after stand-alone installation and configuration.

```bash
./pocket-id
```

--------------------------------

### Run Uptime Kuma directly with Node.js

Source: https://github.com/louislam/uptime-kuma

This command starts the Uptime Kuma server directly using Node.js. It's suitable for quick testing but not recommended for production environments as it doesn't run in the background.

```Shell
node server/server.js
```

--------------------------------

### Download Pocket ID Binary via cURL

Source: https://pocket-id.org/docs/setup/installation

Downloads the latest Pocket ID binary for a specific operating system and architecture directly from the GitHub releases page using cURL.

```bash
curl -L -o pocket-id-linux-amd64 https://github.com/pocket-id/pocket-id/releases/latest/download/pocket-id-linux-amd64
```

--------------------------------

### Run Uptime Kuma in background with PM2

Source: https://github.com/louislam/uptime-kuma

This recommended method installs PM2, a process manager, and then starts Uptime Kuma as a background service. PM2 ensures the application restarts automatically and manages logs.

```Shell
npm install pm2 -g && pm2 install pm2-logrotate
```

```Shell
pm2 start server/server.js --name uptime-kuma
```

--------------------------------

### Configure FileBrowser Quantum Media Integration with FFmpeg

Source: https://github.com/gtsteffaniak/filebrowser/wiki/Configuration-And-Examples

This YAML configuration specifies the installation path for FFmpeg and FFprobe binaries within FileBrowser Quantum. Correctly setting this path enables the application to utilize these tools for media processing and playback functionalities.

```YAML
integrations:
  media:
    ffmpegPath: "/usr/local/bin" # wherever you have both ffmpeg and ffprobe installed at
```

--------------------------------

### Clone and Navigate Pocket ID Portal Repository

Source: https://github.com/pocket-id/pocket-id-portal

Clones the Pocket ID Portal repository from GitHub and navigates into the newly created project directory, preparing for dependency installation.

```Shell
git clone https://github.com/kmendell/pocket-id-portal.git
cd pocket-id-portal
```

--------------------------------

### Install Uptime Kuma with Docker

Source: https://github.com/louislam/uptime-kuma

This snippet provides commands to install Uptime Kuma using Docker. It includes options for standard port exposure and limiting exposure to localhost, suitable for reverse proxy setups. Note that NFS is not supported for data volumes.

```Shell
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
```

```Shell
docker run -d --restart=always -p 127.0.0.1:3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
```

--------------------------------

### Install kubelogin via Package Managers

Source: https://github.com/int128/kubelogin

Commands to install kubelogin on macOS, Linux, and Windows using common package managers. Homebrew is used for macOS and Linux, Krew for kubectl plugin installation across platforms, and Chocolatey for Windows.

```Shell
# Homebrew (macOS and Linux)
brew install kubelogin

# Krew (macOS, Linux, Windows and ARM)
kubectl krew install oidc-login

# Chocolatey (Windows)
choco install kubelogin
```

--------------------------------

### Execute kubectl and Manage Token Cache

Source: https://github.com/int128/kubelogin

Demonstrates how to run `kubectl` commands after `kubelogin` setup, triggering the interactive authentication flow via a browser. It also includes the command to explicitly clean the stored OIDC token cache, forcing re-authentication.

```shell
kubectl get pods
```

```shell
kubectl oidc-login clean
```

--------------------------------

### Configure Kubeconfig with Verbose Logging

Source: https://github.com/int128/kubelogin

An example `kubeconfig` snippet showing how to enable verbose logging (`-v1`) for `kubelogin` when it's executed by `kubectl`. This increased log level provides more detailed output, which is helpful for troubleshooting authentication problems.

```yaml
users:
  - name: oidc
    user:
      exec:
        apiVersion: client.authentication.k8s.io/v1
        command: kubectl
        args:
          - oidc-login
          - get-token
          - -v1
```

--------------------------------

### List Kubernetes Pods

Source: https://github.com/int128/kubelogin

Executes the `kubectl get pods` command to display a list of all pods running in the current Kubernetes context. This is a fundamental command for checking the status of deployed applications.

```shell
kubectl get pods
```

--------------------------------

### Create Environment Configuration File

Source: https://github.com/pocket-id/pocket-id-portal

Creates a new .env file by copying the provided .env.example template. This file must then be updated with specific OIDC provider details and other sensitive configurations.

```Shell
cp .env.example .env
```

--------------------------------

### Manage Uptime Kuma with PM2

Source: https://github.com/louislam/uptime-kuma

These commands provide utilities for monitoring the Uptime Kuma process running under PM2, including viewing live console output and configuring PM2 to start Uptime Kuma automatically on system boot.

```Shell
pm2 monit
```

```Shell
pm2 save && pm2 startup
```

--------------------------------

### Start Caddy with a Specified Configuration File

Source: https://pocket-id.org/docs/guides/proxy-services

This shell command initiates the Caddy server, instructing it to load its configuration from the specified `Caddyfile`. This is the standard way to run Caddy with a custom setup.

```Shell
caddy run --config Caddyfile
```

--------------------------------

### Install OAuth2 Proxy using Go

Source: https://oauth2-proxy.github.io/oauth2-proxy/installation

This command installs the latest stable version of the OAuth2 Proxy binary directly from its Go module. The binary will be placed in your `$GOPATH/bin` directory. Ensure that `$GOPATH` is correctly set and included in your system's `$PATH` environment variable for the binary to be executable from any location.

```Shell
$ go install github.com/oauth2-proxy/oauth2-proxy/v7@latest
```

--------------------------------

### Set up Uptime Kuma without Docker

Source: https://github.com/louislam/uptime-kuma

This command sequence prepares the Uptime Kuma application for execution by cloning the repository and installing its dependencies via npm. Requires Node.js 18/20.4, npm 9, and Git.

```Shell
git clone https://github.com/louislam/uptime-kuma.git
cd uptime-kuma
npm run setup
```

--------------------------------

### Inspect OIDC ID Token Claims

Source: https://github.com/int128/kubelogin

Shows how to use the `kubectl oidc-login setup` command to initiate an authentication flow and then dump the claims of the obtained ID token from the OIDC provider. This is useful for verifying token contents and debugging authentication issues.

```shell
kubectl oidc-login setup --oidc-issuer-url=ISSUER_URL --oidc-client-id=REDACTED
```

--------------------------------

### Example Server Color Mode Configuration

Source: https://github.com/louislam/uptime-kuma

A small JSON object representing a server-side configuration setting for resolving the UI's color mode. This snippet demonstrates a common pattern for passing simple configuration data, often used in web applications to manage themes or display preferences.

```JSON
{"resolvedServerColorMode":"day"}
```

--------------------------------

### Run Traefik OIDC plugin with Keycloak

Source: https://plugins.traefik.io/plugins/66b63d12d29fd1c421b503f5/oidc-authentication

This command starts the Traefik OIDC plugin configured with a pre-set Keycloak instance. It is the easiest way to get started with local development and testing, requiring Docker to be installed and running.

```Shell
task run:keycloak
```

--------------------------------

### Configure PM2 for System Startup

Source: https://github.com/louislam/uptime-kuma

This command saves the current PM2 process list and configures PM2 to automatically start these processes on system boot. It ensures that applications managed by PM2 persist across reboots, providing continuous operation.

```Shell
pm2 save && pm2 startup
```

--------------------------------

### Manage Uptime Kuma with PM2

Source: https://github.com/louislam/uptime-kuma

These commands are essential for monitoring and managing the Uptime Kuma process when it's running under PM2. They allow users to view real-time console output and configure PM2 to automatically start Uptime Kuma on system boot.

```shell
# If you want to see the current console output
pm2 monit

# If you want to add it to startup
pm2 save && pm2 startup
```

--------------------------------

### Setting up the Pocket ID Frontend

Source: https://context7_llms

Instructions for setting up the Pocket ID frontend, which is built with SvelteKit and TypeScript. This involves installing project dependencies and starting the development server for local development.

```Shell
npm install
npm run dev
```

--------------------------------

### Install Devbox and Node.js

Source: https://nodejs.org/en/download/

Installs Devbox, initializes it in a project, adds Node.js, and opens a Devbox shell to verify the Node.js version.

```bash
# Download and install Devbox
curl -fsSL https://get.jetify.com/devbox | bash

# Initialize Devbox in your project
devbox init

# Download and install Node.js:
devbox add node@12

# Open a Devbox shell
devbox shell

# Verify the Node.js version:
node -v # Should print "v0.12.18".

```

--------------------------------

### Download Docker Compose Configuration Files for Pocket ID

Source: https://pocket-id.org/docs/setup/installation

This command downloads the essential `docker-compose.yml` and `.env.example` files directly from the Pocket ID GitHub repository. These files are crucial for setting up and configuring Pocket ID using Docker Compose, defining the services and environment variables required for operation.

```Shell
curl -O https://raw.githubusercontent.com/pocket-id/pocket-id/main/docker-compose.yml \
curl -o .env https://raw.githubusercontent.com/pocket-id/pocket-id/main/.env.example
```

--------------------------------

### Execute Pocket ID Proxmox Helper Script

Source: https://pocket-id.org/docs/setup/installation

Runs the community-maintained helper script for installing Pocket ID on Proxmox VE, typically as a root user.

```bash
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/pocketid.sh)"
```

--------------------------------

### Install Uptime Kuma without Docker (Node.js & PM2)

Source: https://github.com/louislam/uptime-kuma

This section outlines the process for installing Uptime Kuma directly on a system. It involves cloning the repository, installing Node.js dependencies, and provides options for either a temporary run or a persistent background service using PM2, which requires prior installation.

```shell
git clone https://github.com/louislam/uptime-kuma.git
cd uptime-kuma
npm run setup

# Option 1. Try it
node server/server.js

# (Recommended) Option 2. Run in the background using PM2
# Install PM2 if you don't have it:
npm install pm2 -g && pm2 install pm2-logrotate

# Start Server
pm2 start server/server.js --name uptime-kuma
```

--------------------------------

### Start Pocket ID Services with Docker Compose

Source: https://pocket-id.org/docs/setup/installation

This command initiates the Pocket ID services defined in the `docker-compose.yml` file. The `-d` flag runs the containers in detached mode, allowing them to operate in the background. After execution, Pocket ID will be accessible via the configured application URL.

```Shell
docker compose up -d
```

--------------------------------

### Install Grafana Plugin

Source: https://grafana.com/docs/grafana/latest/cli/

Example command to install the latest version of a specified Grafana plugin using the `plugins install` command.

```bash
grafana cli plugins install <plugin-id>
```

--------------------------------

### Initial Self-Hosting Setup Commands

Source: https://support.rallly.co/self-hosting/installation/docker

These shell commands are used for the initial setup of the self-hosted application. The first command extracts the application archive, and the second navigates into the extracted directory to prepare for further configuration.

```shellscript
tar -xz
cd rallly-selfhosted-main
```

--------------------------------

### Configure Kubeconfig for OIDC Authentication

Source: https://github.com/int128/kubelogin

An example `kubeconfig` snippet demonstrating how to configure `kubectl` to use `kubelogin` as an `exec` plugin for OIDC authentication. It specifies the API version, command, and arguments including the OIDC issuer URL and client ID.

```yaml
users:
  - name: oidc
    user:
      exec:
        apiVersion: client.authentication.k8s.io/v1
        command: kubectl
        args:
          - oidc-login
          - get-token
          - --oidc-issuer-url=ISSUER_URL
          - --oidc-client-id=YOUR_CLIENT_ID
```

--------------------------------

### Verify Go Installation

Source: https://golang.org/doc/install

This command is used across all operating systems (Linux, macOS, Windows) to verify that Go has been successfully installed and is accessible via the system's PATH. It should print the installed Go version if successful, confirming that the installation process was completed correctly.

```Shell
$ go version
```

--------------------------------

### Clone and Navigate to Pocket ID Portal Repository

Source: https://github.com/pocket-id/pocket-id-portal

Clones the Pocket ID portal repository from GitHub to your local machine and then changes the current working directory into the newly cloned repository folder.

```shell
git clone https://github.com/kmendell/pocket-id-portal.git
cd pocket-id-portal
```

--------------------------------

### Install Node.js Dependencies for Pocket ID Portal

Source: https://github.com/pocket-id/pocket-id-portal

Installs all required Node.js packages and project dependencies for the Pocket ID Portal using npm, ensuring all necessary modules are available for development and runtime.

```Shell
npm install
```

--------------------------------

### Clone VSCode Configuration for Development

Source: https://github.com/9p4/jellyfin-plugin-sso

This command clones an example VSCode configuration repository into the current repository's `.vscode` directory. This provides a pre-configured development environment for the Jellyfin SSO plugin, streamlining setup for contributors.

```Shell
git clone https://github.com/strazto/jellyfin-plugin-sso-vscode .vscode
```

--------------------------------

### Inspect ID Token Claims with Kubectl OIDC Login Setup

Source: https://github.com/int128/kubelogin

This command initiates the OIDC authentication flow and, upon successful login, displays the claims contained within the obtained ID token. It requires specifying the OIDC issuer URL and client ID. This is valuable for verifying the token's contents and debugging OIDC configurations.

```shell
% kubectl oidc-login setup --oidc-issuer-url=ISSUER_URL --oidc-client-id=REDACTED
...
You got a token with the following claims:

{
 "sub": "********",
 "iss": "https://accounts.google.com",
 "aud": "********",
 ...
}
```

--------------------------------

### Install Node.js Dependencies for Pocket ID Portal

Source: https://github.com/pocket-id/pocket-id-portal

Installs all necessary Node.js packages and project dependencies listed in the package.json file using npm, which are required for the Pocket ID portal to function correctly.

```shell
npm install
```

--------------------------------

### Build and Install RDP Gateway from Source

Source: https://github.com/bolkedebruin/rdpgw

Provides shell commands to compile and install the RDP Gateway from its source repository. Prerequisites include `make` (from standard build tools), Go (version 1.19 or above), and development files for PAM (`libpam0g-dev` on Debian).

```Shell
cd rdpgw
make
make install
```

--------------------------------

### Caddy CLI and REST Admin API Interaction Examples

Source: https://caddyserver.com/

These shell commands illustrate how to interact with Caddy using its command-line interface and RESTful admin API. Examples include starting Caddy with a JSON configuration, patching a handler via `curl`, and retrieving the full configuration.

```Shell
$ caddy start --config caddy.json
$ curl localhost:2019/id/my_handler \
 -X PATCH \
 -H "Content-Type: application/json" \
 -d '{ "handler": "static_response", "body": "Work smarter, not harder." }'
$ curl localhost:2019/config/ | jq
```

--------------------------------

### Start Rallly Server with Docker Compose

Source: https://support.rallly.co/self-hosting/installation/docker

This command initializes and starts the Rallly application using Docker Compose. It sets up a PostgreSQL database, runs necessary migrations to configure the database schema, and launches the Next.js server, which will be accessible on port 3000 by default. For production, consider using a reverse proxy and binding to localhost.

```shell
docker compose up -d
```

--------------------------------

### Build and Install RDP Gateway from Source

Source: https://github.com/bolkedebruin/rdpgw

This shell script provides the necessary commands to compile and install the RDP Gateway application. It assumes the user has navigated into the project's root directory and has required build tools like 'make', 'go' (version 1.19 or higher), and PAM development files installed.

```Shell
cd rdpgw
make
make install
```

--------------------------------

### Configure Traefik OIDC Middleware with File Provider

Source: https://traefik-oidc-auth.sevensolutions.cc/docs/getting-started

This example illustrates how to configure the Traefik OIDC authentication middleware using a YAML file provider. It sets up a `whoami` service, defines the `oidc-auth` middleware with a secret, provider URL, client ID, client secret, and scopes, and then applies this middleware to a router.

```YAML
http:  services:    whoami:      loadBalancer:        servers:          - url: http://whoami:80  middlewares:    oidc-auth:      plugin:        traefik-oidc-auth:          Secret: "MLFs4TT99kOOq8h3UAVRtYoCTDYXiRcZ" # Please change this secret for your setup          Provider:            Url: "https://<YourIdentityProviderUrl>"            ClientId: "<YourClientId>"            ClientSecret: "<YourClientSecret>"            #UsePkce: true # Or use PKCE if your Provider supports this          Scopes: ["openid", "profile", "email"]  routers:    whoami:      entryPoints: ["web"]      rule: "HostRegexp(`.+`)"      service: whoami      middlewares: ["oidc-auth"]
```

--------------------------------

### Install Pocket ID with Docker Compose

Source: https://context7_llms

Instructions to set up Pocket ID using Docker Compose, including downloading the necessary configuration files (`docker-compose.yml` and `.env.example`) and starting the services in detached mode. Ensure to edit the `.env` file after download.

```bash
curl -O https://raw.githubusercontent.com/pocket-id/pocket-id/main/docker-compose.yml
curl -o .env https://raw.githubusercontent.com/pocket-id/pocket-id/main/.env.example
```

```bash
docker compose up -d
```

--------------------------------

### Start Docker Compose server

Source: https://support.rallly.co/self-hosting/installation/docker

This command initiates the Rallly server using Docker Compose. It performs several actions including creating a PostgreSQL database, running necessary migrations to set up the database schema, and starting the Next.js server, which will be accessible on port 3000.

```text
docker compose up -d

```

--------------------------------

### Rename and Make Pocket ID Binary Executable

Source: https://pocket-id.org/docs/setup/installation

Renames the downloaded Pocket ID binary to a generic name and grants it executable permissions.

```bash
mv pocket-id-<operating-system>-<architecture> pocket-id
chmod +x pocket-id
```

--------------------------------

### Example JSON Response for Get Statistics API

Source: https://github.com/pocket-id/analytics

Illustrates the structure of the JSON response returned by the Get Statistics API endpoint, showing activity counts per date.

```JSON
{
 "daily_counts": [
 {
 "date": "2025-05-23",
 "count": 1
 },
 {
 "date": "2025-05-24",
 "count": 3
 },
 {
 "date": "2025-05-25",
 "count": 5
 }
 ]
}
```

--------------------------------

### Install n and Node.js

Source: https://nodejs.org/en/download/

Installs the 'n' Node.js version management tool and Node.js itself. It then verifies the installed Node.js version.

```bash
# Download and install n and Node.js:
curl -fsSL https://raw.githubusercontent.com/mklement0/n-install/stable/bin/n-install | bash -s 12

# Node.js already installs during n-install, but you can also install it manually:
# n install 12

# Verify the Node.js version:
node -v # Should print "v0.12.18".

```

--------------------------------

### Clone Rallly Self-Hosted Repository

Source: https://support.rallly.co/self-hosting/installation/docker

Instructions to clone the Rallly self-hosted repository from GitHub using Git, or alternatively, download and extract it using cURL if Git is not installed. These commands prepare the local environment for further installation steps.

```Bash
git clone https://github.com/lukevella/rallly-selfhosted.git
cd rallly-selfhosted
```

```Bash
curl -L https://github.com/lukevella/rallly-selfhosted/archive/master.tar.gz | tar -xz
cd rallly-selfhosted-main
```

--------------------------------

### Initialize VitePress Global Data

Source: https://www.beszel.dev/guide/oauth

This JavaScript snippet initializes two global `window` variables, `__VP_HASH_MAP__` and `__VP_SITE_DATA__`, by parsing pre-defined JSON strings. `__VP_HASH_MAP__` appears to store a mapping of guide file paths to unique hashes, while `__VP_SITE_DATA__` contains general site configuration like language, title, description, and theme settings for a VitePress site. This setup is typical for static site generators to provide client-side access to build-time metadata.

```javascript
window.__VP_HASH_MAP__=JSON.parse("{\"guide_additional-disks.md\":\"Dd-UbQSv\",\"guide_advanced-deployment.md\":\"D7Px048l\",\"guide_agent-installation.md\":\"HlgZu4-r\",\"guide_common-issues.md\":\"D466rB6u\",\"guide_compiling.md\":\"C5Nb6C7_\",\"guide_contributing.md\":\"CZ2WcuUC\",\"guide_developer-guide.md\":\"C3g5uc6Z\",\"guide_docker-shell.md\":\"6u14Rj8J\",\"guide_environment-variables.md\":\"QxFGigAf\",\"guide_getting-started.md\":\"CrgmkgYp\",\"guide_gpu.md\":\"BVtpKg0W\",\"guide_healthchecks.md\":\"iBbbC0Kn\",\"guide_home-assistant.md\":\"DGQmX8Nx\",\"guide_hub-installation.md\":\"u35acuSA\",\"guide_multlingual-and-localization.md\":\"CSrY2EJc\",\"guide_notifications_bark.md\":\"DkFkYxlI\",\"guide_notifications_discord.md\":\"rzuWsyCy\",\"guide_notifications_generic.md\":\"CIRoixB6\",\"guide_notifications_googlechat.md\":\"DpbXFR1b\",\"guide_notifications_gotify.md\":\"S0sGzyS_\",\"guide_notifications_ifttt.md\":\"z0MQpKXl\",\"guide_notifications_index.md\":\"B_JkcIkQ\",\"guide_notifications_join.md\":\"UmJsec7p\",\"guide_notifications_lark.md\":\"CyUbCViF\",\"guide_notifications_matrix.md\":\"YO_D_q0p\",\"guide_notifications_mattermost.md\":\"cz48Dwz3\",\"guide_notifications_ntfy.md\":\"CGFb5ARu\",\"guide_notifications_opsgenie.md\":\"DWyuA8zr\",\"guide_notifications_pushbullet.md\":\"ComZYiHu\",\"guide_notifications_pushover.md\":\"C_yWpFRM\",\"guide_notifications_rocketchat.md\":\"Dbw-khbZ\",\"guide_notifications_slack.md\":\"DPh4iFq-\",\"guide_notifications_teams.md\":\"BI9m6XXg\",\"guide_notifications_telegram.md\":\"ZqqXK94o\",\"guide_notifications_zulip.md\":\"qYm8Jnby\",\"guide_oauth.md\":\"Dv6mB67T\",\"guide_parts_hub-docker-instructions.md\":\"CAIHD4c8\",\"guide_podman.md\":\"BnvdqX-4\",\"guide_rest-api.md\":\"CJkHQvae\",\"guide_security.md\":\"CgrwgGXr\",\"guide_serve-on-subpath.md\":\"Ds5HtV_U\",\"guide_support-discussion.md\":\"DvELRqFa\",\"guide_user-accounts.md\":\"ByHEi26t\",\"guide_what-is-beszel.md\":\"L-p5HqY8\",\"index.md\":\"DuWQr23h\",\"readme.md\":\"CjgHkCoh\",\"zh_guide_additional-disks.md\":\"DwULapSJ\",\"zh_guide_advanced-deployment.md\":\"BImsmb8H\",\"zh_guide_agent-installation.md\":\"GQh45nDJ\",\"zh_guide_common-issues.md\":\"B32E0s3p\",\"zh_guide_compiling.md\":\"Ce7CwrIY\",\"zh_guide_contributing.md\":\"ByS-A03P\",\"zh_guide_developer-guide.md\":\"fBY6d1Pk\",\"zh_guide_docker-shell.md\":\"a10rOI-L\",\"zh_guide_environment-variables.md\":\"CjzJko7p\",\"zh_guide_getting-started.md\":\"C35qO6dR\",\"zh_guide_gpu.md\":\"BHzHv1T-\",\"zh_guide_healthchecks.md\":\"Bzb1998T\",\"zh_guide_home-assistant.md\":\"Bd9uORA4\",\"zh_guide_hub-installation.md\":\"vm2MWaH4\",\"zh_guide_multlingual-and-localization.md\":\"DKFe6vO9\",\"zh_guide_notifications_bark.md\":\"CphM9DA7\",\"zh_guide_notifications_discord.md\":\"BuN7LMsh\",\"zh_guide_notifications_generic.md\":\"ClzwXZoH\",\"zh_guide_notifications_googlechat.md\":\"CqJBjESn\",\"zh_guide_notifications_gotify.md\":\"B_lN9_uL\",\"zh_guide_notifications_ifttt.md\":\"BQmyVj9c\",\"zh_guide_notifications_index.md\":\"DofYj42h\",\"zh_guide_notifications_join.md\":\"Qp6RNaQE\",\"zh_guide_notifications_lark.md\":\"B9haEkfo\",\"zh_guide_notifications_matrix.md\":\"CMD2m6HW\",\"zh_guide_notifications_mattermost.md\":\"DrWY2mrI\",\"zh_guide_notifications_ntfy.md\":\"DivuCaZP\",\"zh_guide_notifications_opsgenie.md\":\"B0HwJesW\",\"zh_guide_notifications_pushbullet.md\":\"lzuUF7ZW\",\"zh_guide_notifications_pushover.md\":\"G6Ah_IId\",\"zh_guide_notifications_rocketchat.md\":\"pcsuRIrK\",\"zh_guide_notifications_slack.md\":\"DJI3UtrP\",\"zh_guide_notifications_teams.md\":\"CteWApqj\",\"zh_guide_notifications_telegram.md\":\"xFddQNRi\",\"zh_guide_notifications_zulip.md\":\"BUuRGcAF\",\"zh_guide_oauth.md\":\"B7REIQgy\",\"zh_guide_parts_hub-docker-instructions.md\":\"C69DvLsf\",\"zh_guide_podman.md\":\"Jc4jbS_l\",\"zh_guide_rest-api.md\":\"BUSVEfOX\",\"zh_guide_security.md\":\"B97QUHSJ\",\"zh_guide_serve-on-subpath.md\":\"Ck5L2as4\",\"zh_guide_support-discussion.md\":\"BuvGdp-M\",\"zh_guide_user-accounts.md\":\"Bs-BwmGH\",\"zh_guide_what-is-beszel.md\":\"CT8K6Pzt\",\"zh_index.md\":\"Su7VnKBV\"}");window.__VP_SITE_DATA__=JSON.parse("{\"lang\":\"en-US\",\"dir\":\"ltr\",\"title\":\"Beszel\",\"description\":\"A VitePress site\",\"base\":\"/\",\"head\":[],\"router\":{\"prefetchLinks\":true},\"appearance\":\"dark\",\"themeConfig\":{\"search\":{\"provider\":\"local\"}"
)
```

--------------------------------

### Remove Previous Go Installation and Extract Archive (Linux)

Source: https://golang.org/doc/install

This shell command sequence is used on Linux to first remove any existing Go installation directory at `/usr/local/go` and then extract a new Go archive into the same location, ensuring a clean installation. This step is crucial to avoid broken Go installations.

```Shell
$ rm -rf /usr/local/go && tar -C /usr/local -xzf go1.14.3.linux-amd64.tar.gz
```

--------------------------------

### Kubectl Pod Listing with OIDC Authentication Flow

Source: https://github.com/int128/kubelogin

Demonstrates the interactive authentication flow when `kubectl` is used with `kubelogin` for OIDC. The command prompts the user to open a browser for authentication, and upon successful login, it proceeds to list Kubernetes pods, showing their status and age.

```shell
% kubectl get pods
Open http://localhost:8000 for authentication
NAME READY STATUS RESTARTS AGE
echoserver-86c78fdccd-nzmd5 1/1 Running 0 26d
```

--------------------------------

### Basic devcontainer.json Configuration with Image and Extensions

Source: https://code.visualstudio.com/docs/remote/containers

This example demonstrates a fundamental `devcontainer.json` file. It specifies a base Docker image for the development environment, configures port forwarding, and includes VS Code-specific customizations such as automatically installing a particular extension upon container creation.

```JSON
{
  "image": "mcr.microsoft.com/devcontainers/typescript-node",
  "forwardPorts": [3000],
  "customizations": {
    // Configure properties specific to VS Code.
    "vscode": {
      // Add the IDs of extensions you want installed when the container is created.
      "extensions": ["streetsidesoftware.code-spell-checker"]
    }
  }
}
```

--------------------------------

### Enable Pocket ID Module in NixOS

Source: https://pocket-id.org/docs/setup/installation

Enables the Pocket ID service module within a NixOS configuration, making it available for further customization.

```Nix
services.pocket-id.enable = true;
```

--------------------------------

### Add Go Bin Directory to PATH Environment Variable

Source: https://golang.org/doc/install

This shell command adds the `/usr/local/go/bin` directory to the system's `PATH` environment variable. This allows Go commands (like `go build`, `go run`) to be executed from any directory in the terminal. This step is typically required for Linux and macOS manual installations and should be added to a profile file like `$HOME/.profile` or `/etc/profile`.

```Shell
export PATH=$PATH:/usr/local/go/bin
```

--------------------------------

### Enable Traefik OIDC Authentication Plugin

Source: https://traefik-oidc-auth.sevensolutions.cc/docs/getting-started

This configuration snippet demonstrates how to enable the `traefik-oidc-auth` plugin within your Traefik static configuration. It specifies the plugin's module name and its required version, making it available for use in dynamic configurations.

```YAML
experimental:  plugins:    traefik-oidc-auth:      moduleName: "github.com/sevensolutions/traefik-oidc-auth"      version: "v0.13.0"
```

--------------------------------

### Start Caddy Server with Configuration

Source: https://context7_llms

This command initiates the Caddy server, loading its configuration from the specified `Caddyfile`. Ensure the Caddyfile is correctly set up for your proxy and authentication needs.

```bash
caddy run --config Caddyfile
```

--------------------------------

### Install Uptime Kuma with Docker

Source: https://github.com/louislam/uptime-kuma

This Docker command deploys the Uptime Kuma monitoring tool as a detached container. It configures the container to restart automatically, maps host port 3001 to container port 3001, and persists application data using a named Docker volume ('uptime-kuma') to ensure data is retained across container restarts or removals.

```shell
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
```

--------------------------------

### Install Volta and Node.js

Source: https://nodejs.org/en/download/

Installs Volta, a JavaScript toolchain manager, and then uses it to install a specific Node.js version. It also verifies the installed Node.js version.

```bash
# On most Unix systems including macOS, you can install with a single command:
# curl https://get.volta.sh | bash

# Download and install Node.js:
volta install node@12

# Verify the Node.js version:
node -v # Should print "v0.12.18".

```

--------------------------------

### Start Linkding Application with Docker Compose

Source: https://linkding.link/installation

This command initiates the Linkding application using Docker Compose, running it in detached mode. Ensure the `docker-compose.yml` and `.env` files are correctly configured in the current directory before execution.

```shell
docker-compose up -d
```

--------------------------------

### Display Grafana CLI Help

Source: https://grafana.com/docs/grafana/latest/cli/

Example command to display the help information for the Grafana CLI, showing available commands, options, and default paths.

```bash
grafana cli -h
```

--------------------------------

### FileBrowser Frontend Configuration

Source: https://github.com/gtsteffaniak/filebrowser/wiki/Configuration-And-Examples

This YAML snippet demonstrates how to customize the FileBrowser frontend, including setting a display name, disabling default links, and adding external navigation links.

```YAML
frontend:
  name: "My FileBrowser"                  # display name
  disableDefaultLinks: false              # disable default links in the sidebar
  disableUsedPercentage: false            # disable used percentage for the sources in the sidebar
  externalLinks:
    - text: my home page                  # the text to display on the link  validate:required
      title: my home page                 # the title to display on hover
      url: https://domain.com/            # the url to link to  validate:required
  disableNavButtons: false                # disable the nav buttons in the sidebar
```

--------------------------------

### Filebrowser Server Configuration with Multiple Sources

Source: https://github.com/gtsteffaniak/filebrowser/wiki/Configuration-And-Examples

This example illustrates how to configure the filebrowser server to expose multiple file sources. It sets the server port to 80 and defines two distinct paths, which will default to names 'source1' and 'source2' respectively.

```YAML
server:
  port: 80
  sources:
    - path: "/path/to/source1" # defaults with name "source1"
    - path: "/path/to/source2" # defaults with name "source2"
```

--------------------------------

### Hardware Semantic Conventions

Source: https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/

Documentation for semantic conventions related to hardware, providing standardized telemetry for physical and virtual machine resources.

```APIDOC
Hardware: Semantic conventions for hardware
```

--------------------------------

### Install nvm and Node.js

Source: https://nodejs.org/en/download/

Installs Node Version Manager (nvm) and uses it to install a specific Node.js version. It also verifies the installed Node.js and nvm versions.

```bash
# Download and install nvm:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash

# in lieu of restarting the shell

. $HOME/.nvm/nvm.sh

# Download and install Node.js:
nvm install 12

# Verify the Node.js version:
node -v # Should print "v0.12.18".
nvm current # Should print "v0.12.18".

```

--------------------------------

### Configure Kubeconfig for OIDC Authentication

Source: https://github.com/int128/kubelogin

A sample YAML configuration for kubeconfig to enable OIDC authentication using the `kubectl oidc-login` plugin. This configuration specifies the `exec` plugin to dynamically obtain tokens from an OIDC issuer, requiring the issuer URL and client ID.

```YAML
users:
 - name: oidc
 user:
 exec:
 apiVersion: client.authentication.k8s.io/v1
 command: kubectl
 args:
 - oidc-login
 - get-token
 - --oidc-issuer-url=ISSUER_URL
 - --oidc-client-id=YOUR_CLIENT_ID
```

--------------------------------

### Example Kubectl OIDC Configuration Command

Source: https://kubernetes.io/docs/reference/access-authn-authz/authentication/

A concrete example demonstrating how to configure kubectl for OIDC authentication with specific, albeit sample, values. This command sets up a user named 'mmosley' with a given issuer URL, client ID, client secret, refresh token, CA path, and ID token, illustrating a real-world application of the generic command.

```bash
kubectl config set-credentials mmosley  \
            --auth-provider=oidc  \
            --auth-provider-arg=idp-issuer-url=https://oidcidp.tremolo.lan:8443/auth/idp/OidcIdP  \
            --auth-provider-arg=client-id=kubernetes  \
            --auth-provider-arg=client-secret=1db158f6-177d-4d9c-8a8b-d36869918ec5  \
            --auth-provider-arg=refresh-token=q1bKLFOyUiosTfawzA93TzZIDzH2TNa2SMm0zEiPKTUwME6BkEo6Sql5yUWVBSWpKUGphaWpxSVAfekBOZbBhaEW+VlFUeVRGcluyVF5JT4+haZmPsluFoFu5XkpXk5BXqHega4GAXlF+ma+vmYpFcHe5eZR+slBFpZKtQA= \
            --auth-provider-arg=idp-certificate-authority=/root/ca.pem \
            --auth-provider-arg=id-token=eyJraWQiOiJDTj1vaWRjaWRwLnRyZW1vbG8ubGFuLCBPVT1EZW1vLCBPPVRybWVvbG8gU2VjdXJpdHksIEw9QXJsaW5ndG9uLCBTVD1WaXJnaW5pYSwgQz1VUy1DTj1rdWJlLWNhLTEyMDIxNDc5MjEwMzYwNzMyMTUyIiwiYWxnIjoiUlMyNTYifQ.eyJpc3MiOiJodHRwczovL29pZGNpZHAudHJlbW9sby5sYW46ODQ0My9hdXRoL2lkcC9PaWRjSWRQIiwiYXVkIjoia3ViZXJuZXRlcyIsImV4cCI6MTQ4MzU0OTUxMSwianRpIjoiMm96US15TXdFcHV4WDlHZUhQdy1hZyIsImlhdCI6MTQ4MzU0OTQ1MSwibmJmIjoxNDgzNTQ5MzMxLCJzdWIiOiI0YWViMzdiYS1iNjQ1LTQ4ZmQtYWIzMC0xYTAxZWU0MWUyMTgifQ.w6p4J_6qQ1HzTG9nrEOrubxIMb9K5hzcMPxc9IxPx2K4xO9l-oFiUw93daH3m5pluP6K7eOE6txBuRVfEcpJSwlelsOsW8gb8VJcnzMS9EnZpeA0tW_p-mnkFc3VcfyXuhe5R3G7aa5d8uHv70yJ9Y3-UhjiN9EhpMdfPAoEB9fYKKkJRzF7utTTIPGrSaSU6d2pcpfYKaxIwePzEkT4DfcQthoZdy9ucNvvLoi1DIC-UocFD8HLs8LYKEqSxQvOcvnThbObJ9af71EwmuE21fO5KzMW20KtAeget1gnldOosPtz1G5EwvaQ401-RPQzPGMVBld0_zMCAwZttJ4knw
```

--------------------------------

### Kubernetes ExecCredential API Examples for Authentication Plugins

Source: https://kubernetes.io/docs/reference/access-authn-authz/authentication/

Demonstrates the structure of `ExecCredential` objects used by Kubernetes exec plugins. It includes examples for both `v1beta1` and `v1` API versions, showing how to provide a bearer token in the `status` field and how to configure cluster-specific information in the `spec` field for credential acquisition.

```JSON
{
  "apiVersion": "client.authentication.k8s.io/v1beta1",
  "kind": "ExecCredential",
  "status": {
    "token": "my-bearer-token",
    "expirationTimestamp": "2018-03-05T17:30:20-08:00"
  }
}
```

```JSON
{
  "apiVersion": "client.authentication.k8s.io/v1",
  "kind": "ExecCredential",
  "spec": {
    "cluster": {
      "server": "https://172.17.4.100:6443",
      "certificate-authority-data": "LS0t...",
      "config": {
        "arbitrary": "config",
        "this": "can be provided via the KUBERNETES_EXEC_INFO environment variable upon setting provideClusterInfo",
        "you": ["can", "put", "anything", "here"]
      }
    },
    "interactive": true
  }
}
```

```JSON
{
  "apiVersion": "client.authentication.k8s.io/v1beta1",
  "kind": "ExecCredential",
  "spec": {
    "cluster": {
      "server": "https://172.17.4.100:6443",
      "certificate-authority-data": "LS0t...",
      "config": {
        "arbitrary": "config",
        "this": "can be provided via the KUBERNETES_EXEC_INFO environment variable upon setting provideClusterInfo",
        "you": ["can", "put", "anything", "here"]
      }
    },
    "interactive": true
  }
}
```

--------------------------------

### Verify OAuth2 Proxy Prebuilt Binary Checksum

Source: https://oauth2-proxy.github.io/oauth2-proxy/installation

After downloading a prebuilt binary, use this command to verify its integrity against the provided `sha256sum.txt` file. This process ensures that the downloaded file has not been corrupted or tampered with since its release. Replace `oauth2-proxy-x.y.z.linux-amd64` with the actual filename of your downloaded binary.

```Shell
$ sha256sum -c sha256sum.txt
oauth2-proxy-x.y.z.linux-amd64: OK
```

--------------------------------

### Pocket ID Portal Configuration Details

Source: https://github.com/pocket-id/pocket-id-portal

Essential configuration parameters for the Pocket ID Portal, including environment variables for OIDC integration and the designated callback URL. These settings are crucial for connecting to an OIDC provider and ensuring proper application functionality.

```APIDOC
Environment Variables:
  PUBLIC_OIDC_ISSUER: URL of your OIDC provider
  PUBLIC_OIDC_CLIENT_ID: Your client ID
  OIDC_CLIENT_SECRET: Your client secret
  PUBLIC_OIDC_SCOPES: Space-separated list of scopes to request
  POCKET_ID_API_KEY: API key for server-side API calls
  PUBLIC_APP_URL: The external URL this portal will run on

OIDC Callback URL:
  The callback url to use for Pocket ID is `/callback`
```

--------------------------------

### Install Node.js using Package Managers (Chocolatey, Homebrew)

Source: https://nodejs.org/en/download/

This snippet provides commands to install Node.js on Windows using Chocolatey and on macOS/Linux using Homebrew. It includes steps to install the respective package manager if not already present, then install Node.js, and finally verify the installation by checking the Node.js version.

```bash
# Download and install Chocolatey:\npowershell -c \"irm https://community.chocolatey.org/install.ps1|iex\"\n\n# Download and install Node.js:\nchoco install nodejs --version=\"${props.release.version}\"\n\n# Verify the Node.js version:\nnode -v # Should print \"${props.release.versionWithPrefix}\".\n
```

```bash
# Download and install Homebrew\ncurl -o- https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh | bash\n\n# Download and install Node.js:\nbrew install node@${props.release.major}\n\n# Verify the Node.js version:\nnode -v # Should print \"${props.release.versionWithPrefix}\".\n
```