# -*- mode: justfile -*- | |
# ============================================================================== | |
# Settings - Control Just's behavior | |
# ============================================================================== | |
# Set the shell used to execute recipes. Array form is recommended. | |
# -u: Treat unset variables as an error. | |
# -c: Read commands from string. | |
set shell := ["bash", "-uc"] |
// Zed settings | |
// | |
// For information on how to configure Zed, see the Zed | |
// documentation: https://zed.dev/docs/configuring-zed | |
// | |
// To see all of Zed's default settings without changing your | |
// custom settings, run `zed: open default settings` from the | |
// command palette | |
{ | |
"edit_predictions": { |
Are you struggling with macOS GUI applications (like IDEs, text editors, or other tools launched from Finder or Spotlight) not finding command-line tools installed via Homebrew (/opt/homebrew/bin
), MacPorts, or in custom directories like ~/bin
or /usr/local/bin
? This happens because GUI applications on macOS do not automatically inherit the PATH
environment variable set by your login shell configuration files (like .zshenv
, .zprofile
, .bash_profile
, or .bashrc
). Your carefully configured shell PATH
works in the Terminal, but GUI apps remain unaware of it.
This Bash script provides a simple, manual way to apply the PATH
from your current Terminal session to the macOS GUI environment. Instead of complex automatic synchronization, you run this script whenever you want to update the PATH
that GUI applications will use.
I'll complete the text with the process management information:
This script performs DNS TXT record lookups once per minute for 24 hours straight. Each lookup uses a unique random name in the format 'delver-xxxxxxxx'.
- Python 3.x
- Your computer must stay awake the entire time (disable sleep/hibernate)
- Internet connection for the full 24 hours
A step-by-step guide to setting up Model Context Protocol (MCP) servers for Claude Desktop on Windows.
- Install Node.js (v18.x or later)
- Download from: https://nodejs.org/
- Verify installation by opening Command Prompt (CMD) and running:
node --version npm --version
{ | |
"HTML document": { | |
"prefix": "html", | |
"body": ["<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n\t<meta charset=\"UTF-8\">\n\t<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n\t<title>Document</title>\n</head>\n<body>\n$1\n</body>\n</html>", "$0"], | |
"description": "HTML document" | |
} | |
} |
- quadlet-exec.sh - exec macro for quadlet containers
UPDATE: This is tested and working on both Linux and Windows 11 used for LlaMa & DeepSeek
Here's a sample README.md
file written by Llama3.2 using this docker-compose.yaml file that explains the purpose and usage of the Docker Compose configuration:
ollama-portal
A multi-container Docker application for serving OLLAMA API.
[project] | |
name = "tool_testing" | |
version = "0.1.0" | |
description = "Ruff Tested Project" | |
authors = [{ name = "", email = "" }] | |
dependencies = [] | |
requires-python = "==3.11.*" | |
readme = "README.md" | |
license = { text = "MIT" } |