Having troubles with Xcode or their Command Line Tools? Follow this guide to reset your Xcode instance on macOS and resolve issues such as "No Xcode or CLT version detected!"
- Alternatively download Xcode directly
xcode-select -print-pathHaving troubles with Xcode or their Command Line Tools? Follow this guide to reset your Xcode instance on macOS and resolve issues such as "No Xcode or CLT version detected!"
xcode-select -print-pathSetting up programming languages can take some time and differs per language. Here are some guides on each one to get you up and running in no time. NOTE: This guide is intended for macOS development.
M1 Macs & Homebrew: You will need to add the following to your path: /opt/homebrew/bin and /opt/homebrew/sbin
Run brew install dotnet to get started. This will install the SDK as well as the CLI runtime.
| #!/bin/bash | |
| # shellcheck disable=SC2104 | |
| # The following script will setup the project for the first time for local dev | |
| # To run the project after setup, use `docker compose up -d` | |
| set -e | |
| REPO_NAME="$1" |
| import os | |
| def main(): | |
| makefile_path = os.path.join(os.getcwd(), "Makefile") | |
| with open(makefile_path, "r") as makefile: | |
| content = makefile.readlines() | |
| new_content = "" |
Use the following commands to setup Hombrew as a standard user getting around needing sudo access for most packages.
NOTE: This still requires an admin to install Homebrew initially. After the ownership change, the standard user can use Homebrew moving forward.
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"| SELECT | |
| table_name AS `Table`, | |
| table_rows AS `Records`, | |
| ROUND((data_length + index_length) / 1024 / 1024, 2) AS `Size (MB)` | |
| FROM | |
| information_schema.tables | |
| WHERE | |
| table_schema = 'your_db_table' | |
| ORDER BY | |
| `Size (MB)` DESC; |
| // Bootstrap 5 Color Palette | |
| // Docs: https://getbootstrap.com/docs/5.3/customize/color | |
| // Theme colors | |
| $primary: #0d6efd; | |
| $secondary: #6c757d; | |
| $success: #198754; | |
| $info: #0dcaf0; | |
| $warning: #ffc107; | |
| $danger: #dc3545; |
| #!/bin/bash | |
| # Copy a set of files to each repo in a dir, create a branch, and push to origin | |
| # Requires GitHub CLI: `brew install gh` and must be logged in with `gh auth login` | |
| # GitHub CLI Docs: https://cli.github.com/manual/ | |
| MAIN_BRANCH="master" | |
| BRANCH_NAME="ignore_cassette_diffs" | |
| COMMIT_MESSAGE="chore: ignore cassette diffs via gitattributes" | |
| PR_TITLE="$COMMIT_MESSAGE" |
| #!/bin/bash | |
| # Start from the current directory or specify the root directory as an argument | |
| start_dir="${1:-.}" | |
| process_config() { | |
| local config_file="$1" | |
| echo "Processing $config_file" | |
| sed -i.bak 's|https://github.com/|git@github.com:|g' "$config_file" | |
| } |
Getting access to SSH inside a Crontab is often a problem for many as the environment in which your cron runs is not the same as your normal shell. Simply running ssh-add will not allow you to use your SSH Agent inside your crontab. Follow the below guide to setup your crontab to use your ssh-agent:
~/.zlogin file which will be invoked on each login. This will allow your crontab (and normal shell) to use your ssh keys and bypass needing to punch in your password each time you need SSH. This will also span across multiple sessions and shells.