Configure Git (Note: This is a one-time setup.):
mkdir -p ~/.config/git
touch ~/.config/git/config
# syntax=docker/dockerfile:1 | |
FROM public.ecr.aws/amazonlinux/amazonlinux:2023 as build | |
RUN \ | |
set -ex ; \ | |
sed -i '/tsflags=nodocs/d' /etc/dnf/dnf.conf ; \ | |
dnf --releasever=$(rpm -q system-release --qf '%{VERSION}') \ | |
-y \ | |
--allowerasing \ | |
--setopt=install_weak_deps=False \ |
[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" } |
[Distribution] | |
Distribution=arch | |
[Content] | |
Autologin=true | |
Bootloader=none | |
KernelCommandLine=rw | |
Keymap=us | |
Locale=en_US.UTF-8 | |
MakeInitrd=no |
#!/bin/bash | |
set -euo pipefail | |
# ./get_docker_run.sh c56975e847b4 | |
# docker run -d -e "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" -v /root:/data public.ecr.aws/docker/library/amazonlinux:2023 /bin/bash | |
if [[ "$#" -ne 1 ]]; then | |
echo "Usage: $0 <container_name_or_id>" | |
exit 1 | |
fi |
#!/bin/bash | |
#set -x | |
#set -o verbose | |
export LANG=C | |
SOS_OUTPUT_DIR="/tmp/sos" | |
"${ERROR_LOGFILE}"FILE="error.log" | |
[[ -d "${SOS_OUTPUT_DIR}" ]] && rm -rf "${SOS_OUTPUT_DIR}" |
#!/bin/sh | |
CODE_BASE=/path/to/Storyboard | |
SCRIPT_PATH=$(dirname "$0") | |
DEPLOY_ROOT_PATH="${SCRIPT_PATH}/.." | |
LOG_PATH="${DEPLOY_ROOT_PATH}/logs" | |
BUILD_PATH="${DEPLOY_ROOT_PATH}/build/macos" | |
VERSION= | |
STATUS= | |
REQUEST_UUID= |
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.
If your system is running slowly, perhaps a process is using too much CPU time and won't let other processes run smoothly. To find out which processes are taking up a lot of CPU time, you can use Apple's Activity Monitor.
The CPU pane shows how processes are affecting CPU (processor) activity: