| llmc() { | |
| local system_prompt='Output a command that I can run in a ZSH terminal on macOS to accomplish the following task. Try to make the command self-documenting, using the long version of flags where possible. Output the command first enclosed in a "```zsh" codeblock followed by a concise explanation of how it accomplishes it.' | |
| local temp_file=$(mktemp) | |
| local capturing=true | |
| local command_buffer="" | |
| local first_line=true | |
| local cleaned_up=false # Flag to indicate whether cleanup has been run | |
| cleanup() { | |
| # Only run cleanup if it hasn't been done yet |
| #!/bin/bash | |
| # Setting Up OpenWRT on a Virtual Machine with Proxmox | |
| # Based on: https://community.bigbeartechworld.com/t/setting-up-openwrt-on-a-virtual-machine-with-proxmox/257 | |
| # Set your wished version: | |
| export VER="23.05" | |
| export ARCH="amd64" | |
| export INDEX_URL="https://images.linuxcontainers.org/images/openwrt/$VER/$ARCH/default" | |
| #export BUILDDATE=$(date -d "yesterday" '+%Y%m%d') |
| blueprint: | |
| name: Frigate Notifications (0.12.0.3-2) | |
| description: | | |
| ## Frigate Notifications | |
| This blueprint will send a notification to your device when a Frigate event for the selected camera is fired. The notification will initially include the thumbnail of the detection, but include an actionable notification allowing you to view the clip and snapshot. | |
| With this blueprint, you may send the notification to multiple devices by leaving "Device" blank and instead use a [notification group][1]. | |
| ### Software Version Requirements |
| #!/usr/bin/env bash | |
| CLIENT_DB="$HOME/Library/Application Support/CloudDocs/session/db/client.db" | |
| [[ -e $CLIENT_DB ]] || { echo "db not found"; exit 1; } | |
| mapfile -t ITEM_IDS < <(sqlite3 "$CLIENT_DB" <<-EOS | |
| SELECT throttle_id | |
| FROM client_sync_up | |
| EOS | |
| ) |
Part of collection: Hyper-converged Homelab with Proxmox
Keepalived is a Loadbalancer to add ‘high availability` to Linux systemen. See the Keepalived documentatie for more background information.
This setup build on High Available Pi-hole failover cluster using Keepalived and Orbital Sync.
This is me documenting my journey moving my Homelab from a Qnap NAS and a Single host Proxmox server to a Hyper-converged multi-node Proxmox Cluster.
The reason to document it here is twofold:
It's written 'first to scratch my own itch' but hopefully it benefits others too, or even better, that others improve upon my implementations. Feel free to comment or share improvements and insights!
Part of collection: Hyper-converged Homelab with Proxmox
15-04-2025: Seems Proxmox added this now to the GUI; see Using VirtioFS backed by CephFS for bind mounts how to use it.
Virtio-fs is a shared file system that lets virtual machines access a directory tree on the host. Unlike existing approaches, it is designed to offer local file system semantics and performance. The new virtiofsd-rs Rust daemon Proxmox 8 uses, is receiving the most attention for new feature development.
Performance is very good (while testing, almost the same as on the Proxmox host)
Part of collection: Hyper-converged Homelab with Proxmox
Update 09-10-2024: I have moved on to a setup with Docker LXC on Proxmox, with bind-mounts (without VirtioFS) as described in Gist Docker Swarm in Vm's with CephFS.
Update 07-03-2025: The Dockge LXC does this even better, eliminating most issues, with the Docker LXC](https://community-scripts.github.io/ProxmoxVE/scripts?id=docker)!
| #!/usr/bin/osascript | |
| # Required parameters: | |
| # @raycast.schemaVersion 1 | |
| # @raycast.title Screenshot resize | |
| # @raycast.mode silent | |
| # Optional parameters: | |
| # @raycast.icon 📸 | |
| # @raycast.packageName Utilities |
