Bash#
1 $()#
The $(eval ...) construct in a shell script is used to evaluate a command and then execute it. Here’s a breakdown of what each component does:
$( ... ): This is command substitution. It executes the command inside the parentheses and replaces it with the output of the command. For example,$(echo "Hello")will be replaced byHello.eval ...: Theevalcommand takes a string as an argument and executes it as if it were a command. For example,eval echo "Hello"will executeecho "Hello".
When combined as $(eval ...), it first evaluates the inner command and then executes the resulting string as a command.
For example, consider the following:
SSH_KEY_PATH="~/.ssh/id_rsa"
echo $(eval echo $SSH_KEY_PATH)
Here’s what happens step-by-step:
eval echo $SSH_KEY_PATHis evaluated. SinceSSH_KEY_PATHis set to~/.ssh/id_rsa, it becomeseval echo ~/.ssh/id_rsa.eval echo ~/.ssh/id_rsais executed, which outputs/home/username/.ssh/id_rsa(assuming~expands to/home/username).
This effectively resolves and expands any variables or tilde (~) notation in the path, ensuring that the command receives the correct, fully expanded file path.
In the context of your script, $(eval echo $SSH_KEY_PATH) ensures that the path provided by SSH_KEY_PATH is fully expanded before it’s used in commands like chmod or ssh-add.
2 work/abikesa_jbb_https.sh#
# Create a template Jupyter Book; to be modified later
jb create jb
jb build jb
git clone https://github.com/abikesa/create
# User-defined inputs for abi/abikesa_jbb.sh; substantive edits on 08/14/2023:
read -p "Enter your GitHub username: " GITHUB_USERNAME
read -p "Enter your GitHub repository name: " REPO_NAME
read -p "Enter your email address: " EMAIL_ADDRESS
read -p "Enter your root directory (e.g., ~/Dropbox/1f.ἡἔρις,κ/1.ontology): " ROOT_DIR
read -p "Enter the name of the subdirectory to be built within the root directory: " SUBDIR_NAME
read -p "Enter your commit statement: " COMMIT_THIS
# Build the book with Jupyter Book
git config --local user.name "$GITHUB_USERNAME"
git config --local user.email "$EMAIL_ADDRESS"
cd "$(eval echo $ROOT_DIR)"
# rm -rf $SUBDIR_NAME/_build; cuts runtimes by 90%+;
rm -rf $SUBDIR_NAME/_build
jb build $SUBDIR_NAME
rm -rf $REPO_NAME
if [ -d "$REPO_NAME" ]; then
echo "Directory $REPO_NAME already exists. Choose another directory or delete the existing one."
exit 1
fi
# Cloning
git clone "https://github.com/$GITHUB_USERNAME/$REPO_NAME.git"
if [ ! -d "$REPO_NAME" ]; then
echo "Failed to clone the repository. Check your GitHub username, repository name, and permissions."
exit 1
fi
# Copy files from subdirectory to the current repository directory; restored $REPO_NAME!!!
cp -r $SUBDIR_NAME/* $REPO_NAME
cd $REPO_NAME
git add ./*
git commit -m "$COMMIT_THIS"
git remote -v
git remote set-url origin "https://github.com/$GITHUB_USERNAME/$REPO_NAME.git"
git config --local user.name "$GITHUB_USERNAME"
git config --local user.email "$EMAIL_ADDRESS"
# Checkout the main branch
git checkout main
if [ $? -ne 0 ]; then
echo "Failed to checkout the main branch. Make sure it exists in the repository."
exit 1
fi
# Pushing changes
# git config pull.rebase true
# git pull
git push -u origin main
if [ $? -ne 0 ]; then
echo "Failed to push to the repository. Check your credentials and GitHub permissions."
exit 1
fi
ghp-import -n -p -f _build/html
cd ..
rm -rf $REPO_NAME
echo "Jupyter Book content updated and pushed to $GITHUB_USERNAME/$REPO_NAME repository!"
3 work/abikesa_jbb_ssh.sh#
# User-defined inputs for abi/abikesa_jbb.sh; substantive edits on 08/14/2023:
read -p "Enter your GitHub username: " GITHUB_USERNAME
read -p "Enter your GitHub repository name: " REPO_NAME
read -p "Enter your email address: " EMAIL_ADDRESS
read -p "Enter your root directory (e.g., ~/Dropbox/1f.ἡἔρις,κ/1.ontology): " ROOT_DIR
read -p "Enter the name of the subdirectory to be built within the root directory: " SUBDIR_NAME
read -p "Enter your commit statement " COMMIT_THIS
read -p "Enter your SSH key path (e.g., ~/.ssh/id_nh_projectbetaprojectbeta): " SSH_KEY_PATH
# Ensure ssh-agent is running; https://github.com/jhurepos/projectbeta
eval "$(ssh-agent -s)"
# Remove all identities from the SSH agent
ssh-add -D
# Add your SSH key to the agent
`chmod 600 "$(eval echo $SSH_KEY_PATH)"`
ssh-add "$(eval echo $SSH_KEY_PATH)"
# Build the book with Jupyter Book
git config --local user.name "$GITHUB_USERNAME"
git config --local user.email "$EMAIL_ADDRESS"
cd "$(eval echo $ROOT_DIR)"
# rm -rf $SUBDIR_NAME/_build; cuts runtimes by 90%+;
rm -rf $SUBDIR_NAME/_build
jb build $SUBDIR_NAME
rm -rf $REPO_NAME
if [ -d "$REPO_NAME" ]; then
echo "Directory $REPO_NAME already exists. Choose another directory or delete the existing one."
exit 1
fi
# Cloning
git clone "git@github.com:$GITHUB_USERNAME/$REPO_NAME"
if [ ! -d "$REPO_NAME" ]; then
echo "Failed to clone the repository. Check your GitHub username, repository name, and permissions."
exit 1
fi
# Copy files from subdirectory to the current repository directory; restored $REPO_NAME!!!
cp -r $SUBDIR_NAME/* $REPO_NAME
cd $REPO_NAME
git add ./*
git commit -m "$COMMIT_THIS"
git remote -v
ssh-add -D
# Remove all identities from the SSH agent
chmod 600 "$(eval echo $SSH_KEY_PATH)"
# ls -l ~/.ssh/id_stata0elemental
#chmod 600 "$(eval echo ~/.ssh/id_stata0elemental"
git remote set-url origin "git@github.com:$GITHUB_USERNAME/$REPO_NAME"
ssh-add "$(eval echo $SSH_KEY_PATH)"
git config --local user.name "$GITHUB_USERNAME"
git config --local user.email "$EMAIL_ADDRESS"
# Checkout the main branch
git checkout main
if [ $? -ne 0 ]; then
echo "Failed to checkout the main branch. Make sure it exists in the repository."
exit 1
fi
# Pushing changes
# git config pull.rebase true
# git pull
git push -u origin main
if [ $? -ne 0 ]; then
echo "Failed to push to the repository. Check your SSH key path and GitHub permissions."
exit 1
fi
ghp-import -n -p -f _build/html
cd ..
rm -rf $REPO_NAME
echo "Jupyter Book content updated and pushed to $GITHUB_USERNAME/$REPO_NAME repository!"
4 work/abikesa_jbc.sh#
#!/bin/bash
# Check if required commands are available
for cmd in git ssh-keygen jb ghp-import; do
if ! command -v $cmd &> /dev/null; then
echo "Error: $cmd is not installed."
exit 1
fi
done
# Parameters required by the script
read -p "Enter your GitHub username (e.g., abikesa): " GITHUB_USERNAME
read -p "Enter your GitHub repository name (e.g., nabongo): " REPO_NAME
read -p "Enter your email address (e.g., abikesa.sh@gmail.com): " EMAIL_ADDRESS
read -p "Enter your root directory (e.g., ~/Dropbox/1f.ἡἔρις,κ/1.ontology): " ROOT_DIR
read -p "Enter the name of the subdirectory to be created within the root directory (e.g., charles): " SUBDIR_NAME
read -p "Enter the name of the populate_be.ipynb file in ROOT_DIR (e.g., populate_be.ipynb): " POPULATE_BE
read -p "Enter your git commit message (e.g., automated abikesa_fromfolks.sh script): " GIT_COMMIT_MESSAGE
read -p "Enter the number of acts (e.g., 4): " NUMBER_OF_ACTS
read -p "Enter the number of files per act (e.g., 1): " NUMBER_OF_FILES_PER_ACT
read -p "Enter the number of sub-files per file (e.g., 1): " NUMBER_OF_SUB_FILES_PER_FILE
read -p "Enter the number of notebooks (e.g., 7): " NUMBER_OF_NOTEBOOKS
# Set up directories and paths
git config --local user.name "$GITHUB_USERNAME"
git config --local user.email "$EMAIL_ADDRESS"
cd $(eval echo $ROOT_DIR)
rm -rf $REPO_NAME
mkdir -p $SUBDIR_NAME
cp $POPULATE_BE $SUBDIR_NAME/intro.ipynb
cd $SUBDIR_NAME
# Check if SSH keys already exist, and if not, generate a new one
SSH_KEY_PATH="$HOME/.ssh/id_${SUBDIR_NAME}${REPO_NAME}"
rm -rf $SSH_KEY_PATH*
if [ ! -f "$SSH_KEY_PATH" ]; then
ssh-keygen -t ed25519 -C "$EMAIL_ADDRESS" -f $SSH_KEY_PATH
fi
cat ${SSH_KEY_PATH}.pub
echo "Please manually add the above SSH public key to your GitHub account's SSH keys."
read -p "Once you have added the SSH key to your GitHub account, press Enter to continue..."
eval "$(ssh-agent -s)"
ssh-add --apple-use-keychain $SSH_KEY_PATH
# Create _toc.yml file
toc_file="_toc.yml"
echo "format: jb-book" > $toc_file
echo "root: intro.ipynb" >> $toc_file # Make sure this file exists
echo "title: Play" >> $toc_file
echo "parts:" >> $toc_file
# Iterate through the acts, files per act, and sub-files per file
for ((i=0; i<$NUMBER_OF_ACTS; i++)); do
mkdir -p "act_${i}"
echo " - caption: Part $(($i + 1))" >> $toc_file
echo " chapters:" >> $toc_file
for ((j=0; j<$NUMBER_OF_FILES_PER_ACT; j++)); do
mkdir -p "act_${i}/act_${i}_${j}"
for ((k=0; k<$NUMBER_OF_SUB_FILES_PER_FILE; k++)); do
mkdir -p "act_${i}/act_${i}_${j}/act_${i}_${j}_${k}"
for ((n=1; n<=$NUMBER_OF_NOTEBOOKS; n++)); do
new_file="act_${i}/act_${i}_${j}/act_${i}_${j}_${k}/act_${i}_${j}_${k}_${n}.ipynb"
touch "$new_file"
cp "intro.ipynb" "$new_file" # This line copies the content into the new file
echo " - file: $new_file" >> $toc_file
done
done
done
done
# Create _config.yml file
config_file="_config.yml"
echo "title: Your Book Title" > $config_file
echo "copyright: Mwaka" > $config_file
echo "author: Your Name" >> $config_file
echo "logo: https://github.com/muzaale/muzaale.github.io/blob/main/png/hub_and_spoke.jpg?raw=true" >> $config_file
# Build the book with Jupyter Book
cd ..
jb build $SUBDIR_NAME
git clone "https://github.com/$GITHUB_USERNAME/$REPO_NAME"
cp -r $SUBDIR_NAME/* $REPO_NAME
cd $REPO_NAME
git add ./*
git commit -m "$GIT_COMMIT_MESSAGE"
chmod 600 $SSH_KEY_PATH
# Configure the remote URL with SSH
git remote set-url origin "git@github.com:$GITHUB_USERNAME/$REPO_NAME"
# Push changes
git push -u origin main
ghp-import -n -p -f _build/html
rm -rf $REPO_NAME
echo "Jupyter Book content updated and pushed to $GITHUB_USERNAME/$REPO_NAME repository!"
5 work/abikesa_clone.sh#
# Ensure your SSH agent is running:
eval "$(ssh-agent -s)"
# And that your key is added:
ssh-add ~/.ssh/id_rsa
# Test SSH Connection: Test your SSH connection to GitHub:
ssh -T git@github.com
# Clone your private repo
git clone git@github.com:jhurepos/projectalpha.git
ghp_3YBLxNDurzhkp11AvUazjyNdgem05Hw1txxx
git clone https://ghp_3YBLxNDurzhkp11AvUazjyNdgSm05Hw1txxx@github.com/jhurepos/rdc
#
# was automatically renaming stataone "stataone 2"
mkdir stataone
mv "stataone 2"/* stataone/
rm -r "stataone 2"
# phrase is "work", not "workflow"
6 work/abikesa_csv.sh#
# testing a new workflow
export PATH=$PATH:/applications/stata/statamp.app/contents/macos/
stata-se -b work/abikesa_csv.do
7 work/abikesa_editrepo.sh#
#!/bin/bash
# Usage: ./script.sh
# The script will ask for necessary inputs.
echo "Enter GitHub username:"
read USERNAME
echo "Enter repository name:"
read REPO
echo "Is the repository private? (yes/no)"
read IS_PRIVATE
if [[ "$IS_PRIVATE" == "yes" ]]; then
echo "Enter your GitHub personal access token:"
read TOKEN
URL="https://${TOKEN}@github.com/${USERNAME}/${REPO}.git"
else
URL="https://github.com/${USERNAME}/${REPO}.git"
fi
echo "Enter your email for git config:"
read EMAIL
echo "Enter the filename of your SSH key (e.g., id_rsa):"
read SSHw
echo "Enter the exact name of the file or directory to delete (e.g., obsolete_code.py or 'old folder/'):"
read FILENAME_TO_DELETE
# Clone the repository
git clone "$URL"
cd "$REPO"
# Perform actions on the repository
git checkout main
rm -rf "$FILENAME_TO_DELETE" # Deletes the exact file or directory specified by the user, handling spaces properly
# work/abikesa_remove_duplicates.sh # prompt based deletion of all duplicates in repo, with confirmation for each files
# Stage the deletions
git add -A
# The -u option with git add stages all modifications and deletions, but not new files (if there are any new files you want to commit, use git add <file> or git add . to add everything).
# git add -u
# Commit the deletions
git commit -m "Removed '$FILENAME_TO_DELETE' from the repository"
# Setup SSH (ensure you have configured SSH keys on your GitHub account)
ssh-add -D
chmod 600 "$(eval echo ~/.ssh/$SSH)"
git remote set-url origin "git@github.com:${USERNAME}/${REPO}"
ssh-add "$(eval echo ~/.ssh/$SSH)"
# Set local git configurations
git config --local user.name "$USERNAME"
git config --local user.email "$EMAIL"
# Push the changes
git push -u origin main
# git status
# git log
8 work/abikesa_forked.sh#
#!/bin/bash
# Parameters required by the script
read -p "Enter your GitHub username (e.g., abikesa): " GITHUB_USER
read -p "Enter your GitHub repository name (e.g., nabongo): " GITHUB_REPO
read -p "Enter your email address (e.g., abikesa.sh@gmail.com): " EMAIL_ADDRESS
read -p "Enter your root directory (e.g., ~/Dropbox/1f.ἡἔρις,κ/1.ontology): " ROOT_DIR
read -p "Enter the name of the local directory to be created within the root directory (e.g., charles): " LOCAL_DIR
read -p "Enter the SSH key name (e.g., id_charlesnabongo): " SSH_KEYNAME
read -p "Enter your git commit message (e.g., automated abikesa_fromfolks.sh script): " GIT_COMMIT_MESSAGE
# Folked from some_repo to GITHUB_USER/GITHUB_REPO
cd $(eval echo $ROOT_DIR)
git clone "https://github.com/$GITHUB_USER/$GITHUB_REPO"
cp -r "$GITHUB_REPO/*" "$LOCAL_DIR"
jb build "$LOCAL_DIR"
cp -r "$LOCAL_DIR/*" "$GITHUB_REPO"
cd "$GITHUB_REPO"
git add .
git commit -m "$GIT_COMMIT_MESSAGE"
# Overcoming the error: no sufficient permissions
git remote -v
git remote set-url origin "git@github.com:$GITHUB_USER/$GITHUB_REPO"
git config user.name "$GITHUB_USER"
git config user.email "$EMAIL_ADDRESS"
git checkout main
# Check if SSH keys already exist, and if not, generate a new one
read -p "Enter your SSH key name (e.g., id_charlesnabongo, not ~/.ssh/id_charlesnabongo): " SSH_KEYNAME
SSH_KEYPATH="$HOME/.ssh/$SSH_KEYNAME"
if [ ! -f "$SSH_KEYPATH" ]; then
ssh-keygen -t ed25519 -C "$EMAIL_ADDRESS" -f $SSH_KEYPATH
fi
cat "$SSH_KEYPATH.pub"
echo "Please manually add the above SSH public key to your GitHub account's SSH keys."
read -p "Once you have added the SSH key to your GitHub account, press Enter to continue..."
eval "$(ssh-agent -s)"
ssh-add -D
ssh-add $SSH_KEYPATH
chmod 600 $SSH_KEYPATH
# Configure the remote URL with SSH
git remote set-url origin "git@github.com:$GITHUB_USER/$GITHUB_REPO"
# Push changes
git push -u origin main
ghp-import -n -p -f _build/html
rm -rf "$GITHUB_REPO"
echo "jb content updated & pushed to $GITHUB_USER/$GITHUB_REPO repository!"
9 work/abikesa_key_g.sh#
#!/bin/bash
# Check if required commands are available
for cmd in git ssh-keygen jb ghp-import; do
if ! command -v $cmd &> /dev/null; then
echo "Error: $cmd is not installed."
exit 1
fi
done
# User Inputs
read -p "Enter your GitHub username: " GITHUB_USERNAME
read -p "Enter your GitHub repository name: " REPO_NAME
read -p "Enter your email address: " EMAIL_ADDRESS
read -p "Enter your root directory: e.g. ~/dropbox/1f.ἡἔρις,κ/1.ontology " ROOT_DIR
read -p "Enter the name of the subdirectory: " SUBDIR_NAME
read -p "Enter the .ipynb file name in ROOT_DIR: " POPULATE_BE
read -p "Enter your git commit message: " GIT_COMMIT_MESSAGE
read -p "Enter the number of acts: " NUMBER_OF_ACTS
read -p "Enter the number of files per act: " NUMBER_OF_FILES_PER_ACT
read -p "Enter the number of sub-files per file: " NUMBER_OF_SUB_FILES_PER_FILE
read -p "Enter the number of notebooks: " NUMBER_OF_NOTEBOOKS
# Initialize directory
git config --local user.name "$GITHUB_USERNAME"
git config --local user.email "$EMAIL_ADDRESS"
cd $(eval echo $ROOT_DIR)
rm -rf $REPO_NAME
git clone "https://github.com/$GITHUB_USERNAME/$REPO_NAME.git"
cp -r $REPO_NAME $SUBDIR_NAME
# SSH Setup
# SSH Setup
SSH_KEY_PATH="$HOME/.ssh/id_${SUBDIR_NAME}${REPO_NAME}"
# Check if the SSH key already exists
if [ -f "$SSH_KEY_PATH" ]; then
# Prompt the user for confirmation before deletion
read -p "The SSH key already exists. Do you want to delete it? [y/N] " confirm
if [ "$confirm" == "y" ] || [ "$confirm" == "Y" ]; then
rm -rf $SSH_KEY_PATH*
echo "SSH key deleted."
else
echo "SSH key not deleted."
fi
fi
# Generate a new SSH key if it does not exist
if [ ! -f "$SSH_KEY_PATH" ]; then
ssh-keygen -t ed25519 -C "$EMAIL_ADDRESS" -f $SSH_KEY_PATH
fi
# Copy & paste key to GitHub
echo "Please manually add the SSH public key to GitHub."
read -p "Press Enter to continue..."
eval "$(ssh-agent -s)"
ssh-add --apple-use-keychain $SSH_KEY_PATH
# Jupyter Book Setup
jb build $SUBDIR_NAME
cp -r $SUBDIR_NAME/* $REPO_NAME/
cd $REPO_NAME
git add ./*
git commit -m "$GIT_COMMIT_MESSAGE"
chmod 600 $SSH_KEY_PATH
# Git Operations
git remote set-url origin "git@github.com:$GITHUB_USERNAME/$REPO_NAME.git"
git push -u origin main
ghp-import -n -p -f _build/html
rm -rf $REPO_NAME
echo "Jupyter Book content updated and pushed to $GITHUB_USERNAME/$REPO_NAME repository!"
10 work/abikesa_key.sh#
# Fork/clone then create SSH key
jb build quick
ls -al ~/.ssh
ssh-keygen -t ed25519 -C "abikesa.sh@gmail.com.com" -f ~/.ssh/id_gpt4omni
echo "Please manually add the above SSH public key to your GitHub account's SSH keys."
read -p "Once you have added the SSH key to your GitHub account, press Enter to continue..."
cat ~/.ssh/id_gpt4omni.pub
eval "$(ssh-agent -s)"
ssh-add --apple-use-keychain ~/.ssh/id_gpt4omni
# Build the book with Jupyter Book
jb build gpt4
git clone "https://github.com/abikesa/omni"
cp -r gpt4/* omni
cd omni
git add ./*
git commit -m "gpt4-o, thank you!"
chmod 600 ~/.ssh/id_gpt4omni
# Configure the remote URL with SSH
git remote set-url origin "git@github.com:abikesa/omni"
# Push changes
git push -u origin main
ghp-import -n -p -f _build/html
cd ..
rm -rf deploy
echo "Jupyter Book content updated and pushed to abikesa/got repository!"
# commitment issues!!
11 work/abikesa_ngoma.sh#
#!/bin/bash
# Check if required commands are available
for cmd in git ssh-keygen jb ghp-import; do
if ! command -v $cmd &> /dev/null; then
echo "Error: $cmd is not installed."
exit 1
fi
done
# Input information
read -p "Enter your GitHub username: " GITHUB_USERNAME
read -p "Enter your GitHub repository name: " REPO_NAME
read -p "Enter your email address: " EMAIL_ADDRESS
read -p "Enter your root directory (e.g., ~/Dropbox/1f.ἡἔρις,κ/1.ontology): " ROOT_DIR
read -p "Enter the name of the subdirectory to be created within the root directory: " SUBDIR_NAME
read -p "Enter the name of the populate_be.ipynb file in ROOT_DIR: " POPULATE_BE
read -p "Enter your git commit message: " GIT_COMMIT_MESSAGE
read -p "Enter the number of acts: " NUMBER_OF_ACTS
read -p "Enter the number of files per act: " NUMBER_OF_FILES_PER_ACT
read -p "Enter the number of sub-files per file: " NUMBER_OF_SUB_FILES_PER_FILE
read -p "Enter the number of notebooks: " NUMBER_OF_NOTEBOOKS
# Set up directories and paths
git config --local user.name "$GITHUB_USERNAME"
git config --local user.email "$EMAIL_ADDRESS"
cd $(eval echo $ROOT_DIR)
# Only remove repo if it already exists
if [ -d "$REPO_NAME" ]; then
echo "Repository directory $REPO_NAME already exists. Removing it..."
rm -rf $REPO_NAME
fi
# Only create subdirectory if it does not already exist
if [ ! -d "$SUBDIR_NAME" ]; then
echo "Creating subdirectory $SUBDIR_NAME..."
mkdir -p $SUBDIR_NAME
fi
# Only copy populate_be if the intro notebook does not already exist
if [ ! -f "$SUBDIR_NAME/intro.ipynb" ]; then
echo "Copying $POPULATE_BE into $SUBDIR_NAME/intro.ipynb..."
cp $POPULATE_BE $SUBDIR_NAME/intro.ipynb
fi
cd $SUBDIR_NAME
# Check if SSH keys already exist, and if not, generate a new one
SSH_KEY_PATH="$HOME/.ssh/id_${SUBDIR_NAME}${REPO_NAME}"
if [ ! -f "$SSH_KEY_PATH" ]; then
echo "Generating SSH keys..."
ssh-keygen -t ed25519 -C "$EMAIL_ADDRESS" -f $SSH_KEY_PATH
fi
# ... rest of your script remains unchanged
cat ${SSH_KEY_PATH}.pub
echo "Please manually add the above SSH public key to your GitHub account's SSH keys."
read -p "Once you have added the SSH key to your GitHub account, press Enter to continue..."
eval "$(ssh-agent -s)"
ssh-add --apple-use-keychain $SSH_KEY_PATH
# Create _toc.yml file
toc_file="_toc.yml"
echo "format: jb-book" > $toc_file
echo "root: intro.ipynb" >> $toc_file # Make sure this file exists
echo "title: Play" >> $toc_file
echo "parts:" >> $toc_file
# Iterate through the acts, files per act, and sub-files per file
for ((i=0; i<$NUMBER_OF_ACTS; i++)); do
mkdir -p "act_${i}"
echo " - caption: Part $(($i + 1))" >> $toc_file
echo " chapters:" >> $toc_file
for ((j=0; j<$NUMBER_OF_FILES_PER_ACT; j++)); do
mkdir -p "act_${i}/act_${i}_${j}"
for ((k=0; k<$NUMBER_OF_SUB_FILES_PER_FILE; k++)); do
mkdir -p "act_${i}/act_${i}_${j}/act_${i}_${j}_${k}"
for ((n=1; n<=$NUMBER_OF_NOTEBOOKS; n++)); do
new_file="act_${i}/act_${i}_${j}/act_${i}_${j}_${k}/act_${i}_${j}_${k}_${n}.ipynb"
touch "$new_file"
cp "intro.ipynb" "$new_file" # This line copies the content into the new file
echo " - file: $new_file" >> $toc_file
done
done
done
done
# Create _config.yml file
config_file="_config.yml"
echo "title: Your Book Title" > $config_file
echo "copyright: Mwaka" > $config_file
echo "author: Your Name" >> $config_file
echo "logo: https://github.com/muzaale/muzaale.github.io/blob/main/png/hub_and_spoke.jpg?raw=true" >> $config_file
# Build the book with Jupyter Book
cd ..
jb build $SUBDIR_NAME
git clone "https://github.com/$GITHUB_USERNAME/$REPO_NAME"
cp -r $SUBDIR_NAME/* $REPO_NAME
cd $REPO_NAME
git add ./*
git commit -m "$GIT_COMMIT_MESSAGE"
chmod 600 $SSH_KEY_PATH
# Configure the remote URL with SSH
git remote set-url origin "git@github.com:$GITHUB_USERNAME/$REPO_NAME"
# Push changes
git push -u origin main
ghp-import -n -p -f _build/html
rm -rf $REPO_NAME
echo "Jupyter Book content updated and pushed to $GITHUB_USERNAME/$REPO_NAME repository!"
12 new/rmstuff_https.sh#
Look out for the above program. Thats because work/abikesa_remove_duplicates.sh was discontinued
#!/bin/bash
# Check if a directory path is provided
if [ "$#" -ne 1 ]; then
echo "Usage: $0 <directory_path>"
exit 1
fi
directory_path=$1
# Check if the provided path is a directory
if [ ! -d "$directory_path" ]; then
echo "Error: '$directory_path' is not a valid directory."
exit 1
fi
echo "Scanning for duplicates in $directory_path..."
# Change to the specified directory
cd "$directory_path"
# Loop through all files in the specified directory
for file in *; do
if [[ -f "$file" ]]; then
# Check if a duplicate with a ' 2' suffix exists
duplicate="${file%.*} 2.${file##*.}"
if [[ -f "$duplicate" ]]; then
echo "Duplicate found: $duplicate"
# Ask user if they want to delete the duplicate
read -p "Do you want to delete this file? (y/n) " answer
case $answer in
[Yy]* ) rm "$duplicate"; echo "$duplicate deleted.";;
[Nn]* ) echo "Kept $duplicate.";;
* ) echo "Invalid response. No action taken.";;
esac
fi
fi
done
echo "Duplicate scan complete."
13 work/abikesa_rmdir.sh#
#!/bin/bash
# Variables
TOKEN="$1"
REPO_URL="$2"
DELETE_PATH="$3"
SSH_KEY_PATH="$4"
USERNAME="$5"
EMAIL="$6"
# Clone the repo
git clone "https://$TOKEN@github.com/$REPO_URL.git"
cd "$(basename "$REPO_URL")"
# Switch to the main branch
git checkout main
# Remove the specified path (can be directory, file, or file type)
rm -r $DELETE_PATH
# Stage, commit, and push deletions
git add -A
git commit -m "Removed $DELETE_PATH in main directory"
git remote -v
# Unblock if repo linked to ~/.ssh/id_etc
# ssh-add -D
# chmod 600 "$SSH_KEY_PATH"
git remote set-url origin "git@github.com:$REPO_URL.git"
# ssh-add "$SSH_KEY_PATH"
git config --local user.name "$USERNAME"
git config --local user.email "$EMAIL"
git push -u origin main
# token for stata/intermediate ghp_thisisafaketoken
14 work/abikesa_rmfiles.sh#
# Tokens: Profile photo, Settings, Developer Settings
# ghp_thisisafaketoken
# jhustata/basic
# Delete repo folder
git clone https://token@github.com/abikesa/ssh.git
cd ssh
git checkout main
rm -r ssh*
# Stage the Deletions
git add -A
# Commit the Deletions
git commit -m "Removed ssh in main directory"
# Push the Deletions
git remote -v
ssh-add -D
chmod 600 "$(eval echo ~/.ssh/id_sharessh)"
git remote set-url origin "git@github.com:abikesa/ssh"
ssh-add "$(eval echo ~/.ssh/id_sharessh)"
git config --local user.name "abikesa"
git config --local user.email "abikesa.sh@gmail.com"
git push -u origin main
15 work/abikesa_rmstuff.sh#
# $TOKEN if private repo
# git clone "https://$TOKEN@github.com/$REPO_URL.git"
# https://github.com/jhustata/basic
read -p "Enter your GitHub username: " USERNAME
read -p "Enter your GitHub repo: " REPO
read -p "Enter your GitHub filename: " FILENAME
read -p "Enter your GitHub email: " EMAIL
read -p "Enter your GitHub ssh: " SSH
# Switch to the main branch
git clone "https://github.com/$USERNAME/$REPO"
cd "$(basename "https://github.com/$USERNAME/$REPO")"
# Remove the specified path (can be directory, file, or file type)
rm -rf $FILENAME
# Stage, commit, and push deletions
git add -A
git commit -m "Removed $FILENAME in main directory"
git remote -v
# Permissions for access
chmod 600 "$(eval echo $SSH)"
git remote set-url origin "git@github.com:$USERNAME/$REPO_NAME"
ssh-add "$(eval echo $SSH)"
git config --local user.name "$USERNAME"
git config --local user.email "$EMAIL"
# Checkout the main branch
git checkout main
git push -u origin main
16 work/abikesa_statacurl.sh#
# remote work
# Download the remote script using curl
curl -O https://github.com/abikesa/do/raw/main/hello.do
# Run Stata in batch mode with the downloaded script
export PATH=$PATH:/applications/stata/statamp.app/contents/macos/
stata-mp -b hello.do
17 work/bash.sh#
#!/bin/bash
# User input or some other dynamic data
dynamic_part=""
# Some conditional logic to decide the final directory
if [ "$dynamic_part" == "cst" ]; then
dir_to_go="./../$dynamic_part"
else
dir_to_go="~/dropbox/1f.ἡἔρις,κ/1.ontology/"
fi
# Now, we use eval and echo to dynamically generate the directory path
cd $(eval echo $dir_to_go)
jb build git2
18 jb build bloc/denotas#
Since jupyter-client cannot be found in the specified channels, let’s try to resolve the issue by installing it via pip, which might help us bypass the package resolution problems in conda.
First, let’s ensure that pip is available in your conda environment and then use it to install the necessary packages:
Install
jupyter-clientusing pip:pip install jupyter-client
Install
nbclientusing pip:pip install nbclient
Install
jupyterusing pip:pip install jupyter
After installing the required packages, try to register your environment as a Jupyter kernel and then build your Jupyter Book again:
Register the kernel:
python -m ipykernel install --user --name=myenv --display-name "Python (myenv)"
Build the Jupyter Book:
jb build bloc
Here are the steps consolidated:
# Activate your environment
conda activate /Users/d/Documents/github/myenv
# Install jupyter-client using pip
pip install jupyter-client
# Install nbclient using pip
pip install nbclient
# Install jupyter using pip
pip install jupyter
# Register the kernel
python -m ipykernel install --user --name=myenv --display-name "Python (myenv)"
# Build the Jupyter Book
jb build bloc
These steps should help you resolve the package availability issues and proceed with building your Jupyter Book.
19 git config --global credential#
It looks like you’re encountering an issue with pushing your changes to the GitHub repository due to an SSL error. Here are some steps to troubleshoot and resolve the issue:
Check Your GitHub Credentials#
Re-authenticate with GitHub:
Ensure you’re logged in with the correct GitHub account.
Open the terminal and run:
git config --global credential.helper cache git credential-cache exit
Clear Cached Credentials:
Clear any cached credentials by running:
git credential-cache exit
SSL/TLS Configuration#
Check SSL/TLS Configuration:
Modify the Git SSL verification settings. Sometimes, the SSL certificate verification might cause issues. Temporarily disable SSL verification to test:
git config --global http.sslVerify false
Update Git Configuration:
Update your Git configuration to use a more robust SSL backend:
git config --global http.sslBackend openssl
Re-enable SSL Verification:
If disabling SSL verification works, re-enable it to maintain security:
git config --global http.sslVerify true
Network Configuration#
Network Issues:
Check your network connection. A weak or unstable connection might cause this error. Try pushing your changes from a different network.
Large File Handling#
Reduce Push Size (
skipped this):If your push contains large files, consider reducing the size of the push by using Git LFS (Large File Storage):
git lfs install git lfs track "*.your-large-file-type" git add .gitattributes git add your-large-file git commit -m "Add large file with Git LFS" git push origin main
Retry Push#
Retry the Push:
After trying the above steps, retry pushing your changes:
git push origin main
Repeat step
# 2above:work/abikesa_jbb_https.shI can confirm that this worked in the outlined 18 -> 19 -> 2 sequence :)
By following these steps, you should be able to resolve the SSL error and successfully push your changes to the GitHub repository. If the issue persists, you might need to check for updates or reinstall Git and related tools.
20 git credential-cache exit#
To change the GitHub account you’re using in VSCode, you can follow these steps:
Sign Out from GitHub in VSCode:
Open VSCode.
Press
Ctrl+Shift+P(orCmd+Shift+Pon macOS) to open the Command Palette.Type
Sign Outand selectGitHub: Sign Out.This will sign you out of your current GitHub account.
Remove Old Credentials:
Open a terminal or command prompt.
Run the following command to clear any cached credentials:
git credential-cache exit
Clear Git Credentials from Credential Manager:
On Windows:
Open the Credential Manager (Control Panel > User Accounts > Credential Manager).
Look for entries related to GitHub and remove them.
On macOS:
Open the Keychain Access application.
Search for
github.comand delete any related entries.
On Linux:
Credentials are often stored in a file called
~/.git-credentials. You can edit this file to remove old credentials.
Sign In to New GitHub Account in VSCode:
Open VSCode.
Press
Ctrl+Shift+P(orCmd+Shift+Pon macOS) to open the Command Palette.Type
GitHub: Sign Inand select it.Follow the prompts to sign in with your new GitHub account.
Update Remote URL to Use New Account:
If you are switching to a new account, you might need to update the remote URL of your repository:
git remote set-url origin https://github.com/newusername/repository.git
Push Changes Using New Account:
Once signed in with the new account, try pushing your changes again:
git push origin main
By following these steps, you should be able to switch your GitHub account in VSCode and push your changes using the new account credentials. Let me know if you encounter any issues or need further assistance!
21 conda vs. venv#
It looks like your virtual environment is structured differently, likely because it was created using Anaconda or a similar distribution. Instead of the standard venv structure, it seems you have a conda environment. Here’s how you can work with it:
Sure, here’s a coherent step-by-step guide to setting up a Python virtual environment using venv in VSCode on your new Mac laptop:
Setting Up Python Virtual Environment in VSCode#
Install Python: Ensure you have Python installed on your Mac. You can download it from the official Python website: Python Downloads.
Open Terminal: Open the Terminal application on your Mac.
Navigate to Your Project Directory: Change the directory to where you want to set up your virtual environment. For example:
cd /path/to/your/project
Create a Virtual Environment: Create a virtual environment named
myenvusingvenv:python3 -m venv myenv
Activate the Virtual Environment: Activate the virtual environment:
source myenv/bin/activate
Install Required Packages: Install the necessary Python packages within the virtual environment:
pip install numpy matplotlib scipy pandas ipykernel
Add the Virtual Environment to Jupyter: Add your virtual environment to Jupyter kernels:
python -m ipykernel install --name=myenv --display-name "Python (myenv)"
Configuring VSCode#
Open VSCode: Open Visual Studio Code on your Mac.
Open Command Palette: Open the command palette by pressing
Cmd+Shift+P.Select Python Interpreter: Type
Python: Select Interpreterand select it from the dropdown list.Choose the Correct Environment: Choose the interpreter located at
/path/to/your/project/myenv/bin/python.Reload VSCode: Reload VSCode to ensure all settings are applied. You can do this by typing
Reload Windowin the command palette and selecting it.
Verifying the Setup#
Open a New Terminal in VSCode: Open a new terminal within VSCode. It should show
(myenv)indicating the virtual environment is activated.Run a Python Script: Create and run a Python script to verify everything is set up correctly. Here’s an example script:
import numpy as np import matplotlib.pyplot as plt from scipy import stats import pandas as pd # Sample DataFrame data = {'col1': [1, 2, 3, 4], 'col2': [5, 6, 7, 8]} df = pd.DataFrame(data) # Basic Statistics print(df.describe()) # Plot df.plot(kind='bar') plt.show()
By following these steps, you should have a fully functioning Python development environment in VSCode on your new Mac laptop. If you encounter any issues during the setup, feel free to ask for further assistance!
22 pip install#
To simplify the installation of multiple packages, you can create a script that installs all the required packages at once. Here’s how you can do it:
Create a Requirements File: Create a file named
requirements.txtand list all the packages you want to install. For example:numpy matplotlib scipy pandas ipykernel requests statsmodels geopandas networkx
Install Packages Using the Requirements File: You can then install all the packages listed in the
requirements.txtfile with a single command. Here’s how you can do it:pip install -r requirements.txt
Step-by-Step Instructions:#
Create and Activate a Virtual Environment:
cd /Users/d/Documents/GitHub python3 -m venv myenv source myenv/bin/activate
Create a Requirements File:
Create a file named
requirements.txtin your project directory and add the following content:numpy matplotlib scipy pandas ipykernel requests statsmodels geopandas networkx
Install Packages Using the Requirements File:
Run the following command to install all the packages:
pip install -r requirements.txt
Add the Virtual Environment to Jupyter:
After installing the packages, add your virtual environment to Jupyter:
python -m ipykernel install --name=myenv --display-name "Python (myenv)"
Example Script#
Here’s an example script (setup_env.sh) that you can run to automate these steps:
#!/bin/bash
# Navigate to the project directory
cd /Users/d/Documents/GitHub
# Remove the existing virtual environment if it exists
rm -rf myenv
# Create a new virtual environment
python3 -m venv myenv
# Activate the virtual environment
source myenv/bin/activate
# Create a requirements file
cat <<EOT > requirements.txt
numpy
matplotlib
scipy
pandas
ipykernel
requests
statsmodels
geopandas
networkx
EOT
# Install the required packages
pip install -r requirements.txt
# Add the virtual environment to Jupyter
python -m ipykernel install --name=myenv --display-name "Python (myenv)"
# Clean up
rm requirements.txt
echo "Setup completed successfully!"
To run the script:
Save the script as
setup_env.sh.Make it executable:
chmod +x setup_env.sh
Run the script:
./setup_env.sh
This script will set up your virtual environment, install the required packages, and add the environment to Jupyter.
23 work/abikesa_jbb_ssh.sh again!#
The error message indicates that there are several issues encountered during the build process and when pushing to the repository. Here’s a step-by-step guide to address these issues:
1. Handling Jupyter Book Build Errors#
The primary error is due to the kernel dying before replying to kernel_info. This could be due to a misconfigured kernel or missing dependencies.
Steps to Resolve:#
Install Missing Dependencies: Ensure that all required dependencies are installed in your virtual environment.
pip install jupyter jupyterlab nbclient sphinx myst-nb
Check the Kernel Configuration: Ensure that the
stata_kerneland other required kernels are installed correctly. You can install thestata_kernelby following its installation instructions.Rebuild the Jupyter Book: After ensuring all dependencies are installed, try rebuilding the Jupyter Book.
jb build /Users/d/Documents/GitHub/work
2. Addressing GitHub Push Issues#
The error message indicates a failure when pushing to GitHub due to an unexpected disconnect.
Steps to Resolve:#
Check SSH Key Configuration: Ensure that your SSH key is correctly configured with GitHub.
ssh-add ~/.ssh/id_workflow ssh -T git@github.com
The second command should result in a successful authentication message if your SSH key is set up correctly.
Push Changes Again: Retry pushing your changes to GitHub.
git push origin main
Check Network Connection: Ensure that your network connection is stable and retry the push operation. If the problem persists, try using HTTPS instead of SSH for pushing.
git remote set-url origin https://github.com/abikesa/flow.git git push origin main
Summary of Steps#
Install Required Dependencies: Ensure all necessary packages are installed in your virtual environment.
source /Users/d/Documents/GitHub/myenv/bin/activate pip install jupyter jupyterlab nbclient sphinx myst-nb stata_kernel
Rebuild Jupyter Book: Retry building the Jupyter Book after installing dependencies.
jb build /Users/d/Documents/GitHub/work
Check SSH Key Configuration and Push: Ensure SSH keys are configured correctly and push changes to GitHub.
ssh-add ~/.ssh/id_workflow ssh -T git@github.com git push origin main
Use HTTPS for Git Push (if needed): If SSH continues to fail, switch to HTTPS for Git operations.
git remote set-url origin https://github.com/abikesa/flow.git git push origin main
Following these steps should help resolve the issues with the Jupyter Book build and pushing to GitHub. If you encounter further issues, please provide the specific error messages for additional assistance.
24 ~/.ssh/id_workflow#
Based on the error messages, it seems like there are a few issues you need to resolve to successfully build your Jupyter Book and push to your GitHub repository.
1. Jupyter Book Build Errors#
Issue 1: Kernel died before replying to kernel_info#
This issue indicates that the Jupyter kernel is not properly configured or that there are missing dependencies.
Solution:#
Ensure all necessary packages are installed in your virtual environment:
source ~/documents/github/myenv/bin/activate pip install jupyter jupyterlab nbclient sphinx myst-nb stata_kernel
Ensure the
stata_kernelis installed and properly configured. Follow the stata_kernel installation instructions.Rebuild the Jupyter Book:
jb build ~/documents/github/work
2. GitHub Push Issues#
Issue 2: Connection to GitHub closed by remote host#
This issue might be related to network instability or SSH key configuration.
Solution:#
Check SSH Key Configuration: Ensure your SSH key is correctly configured with GitHub.
ssh-add ~/.ssh/id_workflow ssh -T git@github.com
Use HTTPS for Git Push (if SSH fails): If SSH continues to fail, switch to HTTPS for Git operations:
git remote set-url origin https://github.com/abikesa/flow.git git push origin main
Steps to Resolve:#
Install Required Dependencies:
source ~/documents/github/myenv/bin/activate pip install jupyter jupyterlab nbclient sphinx myst-nb stata_kernel
Rebuild Jupyter Book:
jb build ~/documents/github/work
Check SSH Key Configuration and Push:
ssh-add ~/.ssh/id_workflow ssh -T git@github.com git push origin main
Switch to HTTPS for Git Push (if needed):
git remote set-url origin https://github.com/abikesa/flow.git git push origin main
Following these steps should help resolve the issues with the Jupyter Book build and pushing to GitHub. If you encounter further issues, please provide the specific error messages for additional assistance.
25 iframe & source#
The src attribute in an <iframe> element stands for “source.” It specifies the URL of the document or content that you want to embed within the iframe. Essentially, it tells the browser where to find the content that will be displayed inside the iframe.
Here is the src attribute in the context of an <iframe> element:
<iframe src="https://www.example.com" width="600" height="400"></iframe>
In this example, the iframe will load and display the content from “https://www.example.com”.
26 pip install#
Great, you’ve successfully authenticated with GitHub using your SSH key. Now let’s address the remaining issues:
1. Jupyter Book Build Errors#
First, make sure all required packages are installed in your virtual environment:
source ~/documents/github/myenv/bin/activate
pip install jupyter jupyterlab nbclient sphinx myst-nb stata_kernel
Next, ensure the stata_kernel is properly installed and configured. Follow the stata_kernel installation instructions.
Then, rebuild your Jupyter Book:
jb build ~/documents/github/work
2. GitHub Push Issues#
Now that SSH is correctly configured, you should be able to push your changes to GitHub. Use the following commands:
git add .
git commit -m "vscode credentials first, then ssh"
git push origin main
Rebuild Jupyter Book and Push Changes to GitHub#
Install Required Dependencies:
source ~/documents/github/myenv/bin/activate pip install jupyter jupyterlab nbclient sphinx myst-nb stata_kernel
Rebuild Jupyter Book:
jb build ~/documents/github/work
Push Changes to GitHub:
git add . git commit -m "Rebuild Jupyter Book and resolve issues" git push origin main
Following these steps should help you rebuild your Jupyter Book and successfully push your changes to GitHub. If you encounter any further issues, please provide the specific error messages for additional assistance.
27 git config --global http.postBuffer 524288000#
This issue often arises due to network problems, server-side restrictions, or SSH configuration issues. Here are some steps to troubleshoot and potentially resolve the problem:
1. Verify SSH Configuration#
Ensure that your SSH key is correctly configured and added to the SSH agent:
ssh-add -l
If your key is not listed, add it again:
ssh-add ~/.ssh/id_workflow
2. Increase Git Buffer Size#
Sometimes, increasing the Git buffer size can resolve issues related to large pushes:
git config --global http.postBuffer 524288000
3. Check Your Network Connection#
Ensure you have a stable internet connection. If you’re on a VPN or behind a proxy, try disabling it and pushing again.
4. Use SSH Verbose Mode#
Enable verbose mode to get more information about the SSH connection:
GIT_SSH_COMMAND="ssh -v" git push origin main
5. Split Your Push#
If the repository is large, consider pushing smaller parts:
git add .
git commit -m "Partial commit"
git push origin main
6. Retry the Push#
Sometimes, simply retrying the push can work:
git push origin main
7. Check GitHub Status#
Ensure GitHub is not experiencing any issues by checking the GitHub status page.
Summary#
Ensure SSH key is added to the agent.
Increase Git buffer size.
Check network connection.
Use SSH verbose mode for more details.
Split large pushes into smaller commits.
Retry the push.
Check GitHub status.
Example Commands#
ssh-add ~/.ssh/id_workflow
git config --global http.postBuffer 524288000
GIT_SSH_COMMAND="ssh -v" git push origin main
If you still encounter issues after trying these steps, please share any additional output or error messages for further assistance.
28 bash#
The “unexpected disconnect while reading sideband packet” error indicates that there might be an issue on GitHub’s end or with the network connection between your local machine and GitHub’s servers. Here are a few additional steps you can try to resolve the issue:
1. Reduce Pack Size#
Sometimes large pack files can cause issues. Try reducing the pack size:
git config --global pack.windowMemory "100m"
git config --global pack.packSizeLimit "100m"
git config --global pack.threads "1"
2. Use HTTP/HTTPS Instead of SSH#
If SSH continues to cause issues, you might want to try using HTTPS to push the changes:
git remote set-url origin https://github.com/abikesa/flow.git
git push -u origin main
3. Ensure Network Stability#
Make sure your network connection is stable and not experiencing any interruptions. If possible, try switching to a different network or disabling VPN/proxy.
4. Use Verbose Mode for More Information#
Run the push command with increased verbosity to gather more information:
GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_CURL_VERBOSE=1 git push origin main
5. Split Your Commit#
If you have a very large commit, try splitting it into smaller commits and pushing them incrementally:
git reset --soft HEAD~1
git add -p # or git add -i
git commit -m "Part 1 of the changes"
git push origin main
Example Commands#
# Reduce pack size
git config --global pack.windowMemory "100m"
git config --global pack.packSizeLimit "100m"
git config --global pack.threads "1"
# Switch to HTTPS
git remote set-url origin https://github.com/abikesa/flow.git
git push -u origin main
# Push with verbose mode
GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_CURL_VERBOSE=1 git push origin main
# Split commit and push
git reset --soft HEAD~1
git add -p # or git add -i
git commit -m "Part 1 of the changes"
git push origin main
If you continue to encounter issues, consider reaching out to GitHub support for further assistance, as the problem may be related to server-side restrictions or issues.
29 rm: quickdeploy: Permission denied#
It looks like you’re encountering a permission issue while trying to remove the quickdeploy directory. You might need to use sudo to remove the directory with elevated privileges.
Try running the following command:
sudo rm -rf quickdeploy
You’ll be prompted to enter your password. This command should remove the directory regardless of the permissions set on it.
30 ghp-import -n -p -f _build/html#
Certainly! Let’s go through the process of setting up your workflow on your new Studio Pro and MacBookPro from scratch, step by step. (Later create a hybrid of #30 & #31 for optimal setup process)
Step 1: Install Homebrew#
Homebrew is a package manager for macOS that makes installing third-party software easy.
Open Terminal.
Install Homebrew by pasting the following command and pressing Enter:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Run these two commands in your terminal to add Homebrew to your PATH:
(echo; echo 'eval "$(/opt/homebrew/bin/brew shellenv)"') >> /Users/apollo/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"
Run brew help to get started
Further documentation: https://docs.brew.sh
Step 2: Install Python#
Using Homebrew, install Python.
In Terminal, run:
brew install python
Python has been installed as
/opt/homebrew/bin/python3
Unversioned symlinks python, python-config, pip etc. pointing to
python3, python3-config, pip3 etc., respectively, have been installed into
/opt/homebrew/opt/python@3.12/libexec/bin
See: https://docs.brew.sh/Homebrew-and-Python
Verify the installation:
python3 --version
Step 3: Install VSCode#
Download and install Visual Studio Code from the official website.
Step 4: Install VSCode Extensions#
Install the following extensions in VSCode:
Python
Jupyter
GitHub Repositories
You can find and install these extensions from the Extensions view in VSCode (Cmd+Shift+X).
Step 5: Set Up a Virtual Environment#
Create a directory for your project:
mkdir my_project cd my_project
Set up a virtual environment:
python3 -m venv venv
Activate the virtual environment:
source venv/bin/activate
Step 6: Install Jupyter Book and ghp-import#
Install
pipif not already installed:python3 -m ensurepip --upgrade
Install Jupyter Book:
pip install jupyter-book
WARNING: You are using pip version 21.2.4; however, version 24.0 is available. You should consider upgrading via the ‘/Users/apollo/Documents/Athena/venv/bin/python3 -m pip install –upgrade pip’ command.
Install
ghp-import:pip install ghp-import
Step 7: Create a Jupyter Book#
Create a new Jupyter Book:
jb create mybook cd mybook
Build the book:
jb build .
Step 8: Use ghp-import to Publish to GitHub Pages#
Ensure your book is built:
jb build .
Use
ghp-importto publish to GitHub Pages:ghp-import -n -p -f _build/html
Step 9: Automate Workflow with VSCode#
Open your project in VSCode.
Use the integrated terminal (`Ctrl+``) to activate your virtual environment:
source venv/bin/activate
Create tasks in VSCode to automate your workflow (optional).
Additional Tips#
Ensure your GitHub repository is correctly set up for GitHub Pages.
Regularly commit and push changes to your repository.
Customize your Jupyter Book as needed by editing the configuration files.
By following these steps, you should be able to reproduce your previous workflow on your new machines. If you encounter any issues, feel free to ask for further assistance!
31 fatal: the remote end hung up unexpectedly#
You’re right. For a public repository using HTTPS, GitHub credentials should not be necessary unless you’re pushing changes. If you still encounter issues, the problem might be related to the network or other configurations. Let’s adjust the approach to focus on the push error and the SSL issue:
Step-by-Step Guide to Resolve Push Issues and SSL Errors#
Step 1: Increase Git Buffer Size#
Open your terminal.
Increase the Git buffer size by running:
git config --global http.postBuffer 524288000
Step 2: Retry the Push#
Ensure you are in your project directory.
Retry pushing your changes:
git add . git commit -m "workflow 3.0 (ghp-import from any computer)" git push origin main
Step 3: SSL Configuration#
If you still face SSL issues, you can try reconfiguring the SSL settings for Git:
Disable SSL verification (not recommended for long-term use):
git config --global http.sslVerify false
Retry the push:
git push origin main
If the push is successful, re-enable SSL verification for security:
git config --global http.sslVerify true
Step 4: Reconfigure Remote URL (if needed)#
If the issue persists, ensure your remote URL is correctly set:
Check the current remote URL:
git remote -v
Reconfigure the remote URL (if necessary):
git remote set-url origin https://github.com/abikesa/dionysus.git
Step 5: Verify Your Changes on GitHub#
Go to your GitHub repository in your web browser.
Verify that your changes have been pushed successfully and that the GitHub Pages site is properly updated.
Step-by-Step Recap (Updated)#
Install Homebrew:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Install Python:
brew install python
Install VSCode from VSCode website.
Install VSCode Extensions:
Python
Jupyter
GitHub Repositories
Set Up a Virtual Environment:
mkdir my_project cd my_project python3 -m venv venv source venv/bin/activate
Install Jupyter Book and ghp-import:
python3 -m ensurepip --upgrade pip install jupyter-book ghp-import
Create and Build a Jupyter Book:
jb create mybook cd mybook jb build .
Publish to GitHub Pages:
ghp-import -n -p -f _build/html
Increase Git Buffer Size and Retry Push:
git config --global http.postBuffer 524288000 git add . git commit -m "workflow 3.0 (ghp-import from any computer)" git push origin main
SSL Configuration (if needed):
git config --global http.sslVerify false git push origin main git config --global http.sslVerify true
By following these updated steps, you should be able to resolve the issue and successfully push your changes to GitHub. If you encounter any further issues, let me know!
By following these steps, you should be able to resolve the issue and successfully push your changes to GitHub. If you encounter any further issues, let me know!
32 Software Update Tool#
Only received this query on Hades/MacBookPro. Didn’t showup on Apollo/Mac Studio Pro
Software Update Tool
Finding available software
Downloading Command Line Tools for Xcode
Downloaded Command Line Tools for Xcode Installing Command Line Tools for Xcode
33 xcode-select --install#
Yes, you may need to install Xcode Command Line Tools to ensure that you have all the necessary compilers and libraries for building Python packages and other software. Here’s how you can install it:
Step 1: Install Xcode Command Line Tools#
Open Terminal.
Run the following command to install Xcode Command Line Tools:
xcode-select --install
This will prompt a pop-up window to install the tools. Follow the instructions to complete the installation.
Step 2: Confirm Installation#
To confirm that the installation was successful, run:
xcode-select -p
This should return /Library/Developer/CommandLineTools.
Step-by-Step Guide Recap (Including Xcode Command Line Tools)#
Install Homebrew:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Install Xcode Command Line Tools:
xcode-select --installInstall Python:
brew install python
Install VSCode from VSCode website.
Install VSCode Extensions:
Python
Jupyter
GitHub Repositories
Set Up a Virtual Environment:
mkdir my_project cd my_project python3 -m venv venv source venv/bin/activate
Install Jupyter Book and ghp-import:
python3 -m ensurepip --upgrade pip install jupyter-book ghp-import
Create and Build a Jupyter Book:
jb create mybook cd mybook jb build .
Publish to GitHub Pages:
ghp-import -n -p -f _build/html
Increase Git Buffer Size and Retry Push:
git config --global http.postBuffer 524288000 git add . git commit -m "workflow 3.0 (ghp-import from any computer)" git push origin main
SSL Configuration (if needed):
git config --global http.sslVerify false git push origin main git config --global http.sslVerify true
By following these updated steps, you should be able to resolve any issues related to dependencies and successfully push your changes to GitHub. If you encounter any further issues, let me know!
34 pip install pandas ... #
Certainly! You can install the most frequently used Python packages for data analysis in a single command using pip. Here is the command to install packages like numpy, pandas, matplotlib, seaborn, scipy, scikit-learn, and jupyter:
pip install numpy pandas matplotlib seaborn scipy scikit-learn jupyter
If you want to ensure these packages are installed in your virtual environment, make sure the environment is activated before running the command:
Activate your virtual environment:
source venv/bin/activate
Install the packages:
pip install numpy pandas matplotlib seaborn scipy scikit-learn jupyter
This will install the most commonly used packages for data analysis in one go. If you need any additional packages, you can always add them to the list.
# this takes about an hour
# and this took half hour
brew install python
35 install.packages('IRkernel')#
To run R commands, you need to install & open the R console from your terminal. Here are the steps:
Open the R Console: In your terminal, type
Rand press Enter to start the R console.Install and Configure
IRkernel: Once in the R console, run the following commands:install.packages('IRkernel') IRkernel::installspec(user = FALSE)
Here is the complete workflow:
Open R Console:
R
Run R Commands:
install.packages('IRkernel') IRkernel::installspec(user = FALSE)
After completing these steps, you can exit the R console by typing q() and pressing Enter.
Verify Kernel Installation: After configuring the kernel, verify its installation in your terminal:
jupyter kernelspec list
This should list the available kernels, including ir.
Example:#
Opening the R Console:
(venv) apollo@Athena Athena % R
Installing and Configuring IRkernel:
> install.packages('IRkernel')
> IRkernel::installspec(user = FALSE)
> q()
After running these commands, your R kernel should be installed and configured correctly. Then, you can retry building your Jupyter Book.
For VSCode:
Extensions
Search for
@id:reditorsupport.rInstall
R Extension for visual Studio Code
36 IRkernel (take 2)#
Here’s a summary of the steps to configure the R kernel in VSCode on your MacBook Pro for easy reproducibility:
Summary of Steps#
Install Prerequisites
Install Python 3 (if not already installed).
Install R from CRAN.
Set Up a Virtual Environment
python3 -m venv ~/documents/athena/myenv source ~/documents/athena/myenv/bin/activate
Install Jupyter and IRKernel
pip install jupyter jupyter-client R -e "install.packages('IRkernel'); IRkernel::installspec(user = TRUE)"
Ensure R is in the PATH
Add R to your PATH in your
~/.zshrc:
echo 'export PATH=/usr/local/bin:$PATH' >> ~/.zshrc source ~/.zshrc
Verify Kernel Installation
jupyter kernelspec list
Install VSCode Extensions
Install the Jupyter Extension.
Optionally, install the R Extension for Visual Studio Code.
Configure VSCode to Use the Jupyter Server
Open VSCode.
Open the Command Palette (
Ctrl+Shift+PorCmd+Shift+P).Run
Jupyter: Select Interpreter to start Jupyter serverand select the Python interpreter from your virtual environment.
Open or Create a Jupyter Notebook
Open an existing
.ipynbfile or create a new one.
Select the R Kernel
Click on the kernel name at the top right corner of the notebook interface.
Select the
Rkernel from the dropdown menu.If none apparently available, select
Jupyter KernelandRwill be an option
Step-by-Step Commands#
Install Python 3 and R (if not already installed):
Follow the installation instructions for Python 3 and R on your MacBook Pro.
Set Up Virtual Environment:
python3 -m venv ~/documents/athena/myenv source ~/documents/athena/myenv/bin/activate
Install Jupyter and IRKernel:
pip install jupyter jupyter-client R -e "install.packages('IRkernel'); IRkernel::installspec(user = TRUE)"
Add R to PATH:
echo 'export PATH=/usr/local/bin:$PATH' >> ~/.zshrc source ~/.zshrc
Verify Kernel Installation:
jupyter kernelspec list
Install VSCode Extensions:
Open the Extensions view in VSCode (
Ctrl+Shift+XorCmd+Shift+X).Install the Jupyter Extension.
Optionally, install the R Extension.
Configure Jupyter Server in VSCode:
Open the Command Palette (
Ctrl+Shift+PorCmd+Shift+P).Run
Jupyter: Select Interpreter to start Jupyter serverand select the Python interpreter from your virtual environment.
Open or Create a Jupyter Notebook:
Open an existing
.ipynbfile or create a new one in VSCode.
Select the R Kernel:
Click on the kernel name at the top right corner of the notebook interface.
Select the
Rkernel from the dropdown menu.
By following these summarized steps, you should be able to replicate the setup on your MacBook Pro successfully. If you encounter any issues or need further assistance, please let me know.
37 jb create#
source ~/documents/athena/myenv/bin/activate
pip install jupyter-book
jb --version
jb create ir
38 ghp-import#
To install ghp-import, you can use pip, the Python package installer. Here’s how you can do it:
Open your terminal.
Ensure you have
pipinstalled by running:pip --versionIf
pipis not installed, you can install it by following the instructions here.Install
ghp-importusingpip:pip install ghp-import
If you want to install ghp-import in a specific virtual environment, make sure to activate your virtual environment first:
Navigate to your project directory:
cd /path/to/your/project
Activate your virtual environment. For example, if you are using
venv, you can activate it like this:On macOS and Linux:
source venv/bin/activate
On Windows:
.\venv\Scripts\activate
Once the virtual environment is activated, install
ghp-import:pip install ghp-import
To verify the installation, you can check the version of ghp-import:
ghp-import --version
This should confirm that ghp-import is installed and ready to use. If you encounter any issues, feel free to ask for further assistance.
39 setup_stata_kernel.sh#
Certainly! Below is a comprehensive script that you can run from start to finish to set up your virtual environment, install the necessary packages, configure the Stata kernel, and start Jupyter Notebook. This script ensures that the entire process is reproducible and hassle-free.
Complete Script for Setting Up Stata Kernel in Jupyter Notebook#
#!/bin/bash
# Set up variables
VENV_PATH="/Users/hades/Documents/hades/myenv"
STATA_PATH="/Applications/Stata/StataMP.app/Contents/MacOS/stata-mp"
ZSHRC_PATH="$HOME/.zshrc"
# Step 1: Remove existing virtual environment if it exists
echo "Removing existing virtual environment..."
rm -rf $VENV_PATH
# Step 2: Create a new virtual environment
echo "Creating a new virtual environment..."
python3 -m venv $VENV_PATH
# Step 3: Activate the virtual environment
echo "Activating the virtual environment..."
source $VENV_PATH/bin/activate
# Step 4: Install necessary packages
echo "Installing necessary packages..."
pip install stata_kernel ipykernel setuptools notebook
# Step 5: Configure environment variable for Stata path
echo "Configuring environment variable for Stata path..."
if [ ! -f $ZSHRC_PATH ]; then
touch $ZSHRC_PATH
fi
grep -qxF "export STATA_KERNEL_STATA_PATH=$STATA_PATH" $ZSHRC_PATH || echo "export STATA_KERNEL_STATA_PATH=$STATA_PATH" >> $ZSHRC_PATH
source $ZSHRC_PATH
# Step 6: Install the Stata kernel
echo "Installing the Stata kernel..."
python -m stata_kernel.install
# Step 7: Start Jupyter Notebook
echo "Starting Jupyter Notebook..."
jupyter notebook
echo "Setup complete!"
Instructions to Use the Script#
Save the Script:
Save the script to a file, for example,
setup_stata_kernel.sh.
Make the Script Executable:
Make the script executable by running the following command:
chmod +x setup_stata_kernel.sh
Run the Script:
Run the script by executing:
./setup_stata_kernel.sh
This script will handle the entire process of setting up the virtual environment, installing the necessary packages, configuring the environment variable, installing the Stata kernel, and starting Jupyter Notebook. This ensures a reproducible and smooth setup experience.
40 XQuartz#
41 setup_myenv.sh#
#!/bin/zsh
# Define the environment directory
ENV_DIR="myenv"
# Remove the existing environment if it exists
if [ -d "$ENV_DIR" ]; then
rm -rf "$ENV_DIR"
fi
# Create a new virtual environment
python3 -m venv $ENV_DIR
# Check if virtual environment was created successfully
if [ ! -d "$ENV_DIR" ]; then
echo "Failed to create virtual environment."
exit 1
fi
# Activate the virtual environment
source $ENV_DIR/bin/activate
# Check if activation was successful
if [ "$VIRTUAL_ENV" != "" ]; then
echo "Virtual environment activated."
else
echo "Failed to activate virtual environment."
exit 1
fi
# Ensure pip is installed
if ! command -v pip &> /dev/null; then
echo "pip could not be found, installing pip..."
curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python get-pip.py
if [ $? -ne 0 ]; then
echo "Failed to install pip."
deactivate
exit 1
fi
fi
# Upgrade pip
pip install --upgrade pip
# Install necessary Python packages
pip install jupyter jupyterlab ipykernel jupyter-book ghp-import matplotlib numpy wordcloud pandas scipy seaborn scikit-learn tensorflow keras plotly dash flask django pytest pylint black isort mypy pydantic fastapi uvicorn requests beautifulsoup4 sqlalchemy ipython tqdm joblib sympy h5py pyqt5 nbconvert nbformat ipywidgets
# Check if Jupyter Book is installed
if ! command -v jb &> /dev/null; then
echo "Jupyter Book could not be found. Something went wrong with the installation."
deactivate
exit 1
fi
# Install IRkernel for R
Rscript -e "install.packages('IRkernel', repos='https://cloud.r-project.org/')"
if [ $? -ne 0 ]; then
echo "Failed to install IRkernel."
deactivate
exit 1
fi
Rscript -e "IRkernel::installspec(name = 'ir', displayname = 'R')"
if [ $? -ne 0 ]; then
echo "Failed to install IRkernel spec."
deactivate
exit 1
fi
# Install Stata kernel (assuming you have Stata installed)
pip install stata_kernel
python -m stata_kernel.install
if [ $? -ne 0 ]; then
echo "Failed to install Stata kernel."
deactivate
exit 1
fi
echo "Environment setup complete."
# Deactivate the virtual environment
deactivate
# Print instructions for reactivating the virtual environment
echo "To reactivate the virtual environment, use the following command:"
echo "source $ENV_DIR/bin/activate"
42 git config --global http.sslVerify false#
Alright, let’s switch back to using HTTPS for your remote repository. Here’s how to resolve the issue using HTTPS:
Set Remote URL Back to HTTPS:
git remote set-url origin https://github.com/username/repo.git
Retry the Push:
git push -u origin main
If You Encounter the SSL Error Again: Since we increased the HTTP post buffer and switched to HTTP/1.1, we can try a few more steps to resolve the SSL issue.
Disable SSL Verification: This is not recommended for regular use due to security risks, but it can help diagnose the problem:
git config --global http.sslVerify false
Then try the push again.
Check GitHub Status: Make sure GitHub is not experiencing any issues by checking GitHub Status.
Reauthenticate: Sometimes, clearing saved credentials can help:
git credential-cache exit
Then try the push again. You might be prompted to enter your username and password.
Update Git: Ensure your Git version is up-to-date. You can download the latest version from Git’s official website.
If the push is successful, you can turn SSL verification back on for security reasons:
git config --global http.sslVerify true
Try these steps, and let me know if you encounter any specific errors during the process.
43 pip install "sphinx>=5.0,<6.0"#
We are caught in a dependency conflict due to the required versions of sphinx and other extensions. Let’s take a different approach:
Uninstall all currently installed versions.
Install compatible versions of the packages together, ensuring there are no version conflicts.
Let’s uninstall the current packages again:
pip uninstall sphinx sphinx-panels jupyter-book sphinxcontrib-applehelp sphinxcontrib-devhelp sphinxcontrib-jsmath sphinxcontrib-htmlhelp sphinxcontrib-serializinghtml sphinxcontrib-qthelp sphinx-design sphinx-external-toc pydata-sphinx-theme sphinx-jupyterbook-latex sphinx-book-theme myst-nb myst-parser
Next, install the correct versions together:
pip install "sphinx>=5.0,<6.0" sphinxcontrib-applehelp sphinxcontrib-devhelp sphinxcontrib-jsmath sphinxcontrib-htmlhelp sphinxcontrib-serializinghtml sphinxcontrib-qthelp sphinx-design "sphinx-external-toc<2" "pydata-sphinx-theme>=0.15.2" "sphinx-jupyterbook-latex<2" "sphinx-book-theme>=1.1.0,<2" "myst-nb<3" "myst-parser<3" "jupyter-book>=0.12.0" "sphinx-thebe>=0.3,<1" sphinx-panels
This command should install compatible versions of the required packages. If there are any issues during installation, we will need to adjust the versions accordingly. Once installed, try building your Jupyter Book again:
jb build nia/book/website
If further adjustments are needed, please let me know.
44 requirements.txt#
pip install -r requirements.txt && jupyter-book build .#
Deploying#
First, create a work directory & environment
git clone https://github.com/abikesa/workflow && mv workflow new && new/setup_myenv.sh && source myenv/bin/activate
On Netlify#
Next, navigate to your project template:
git clone https://github.com/the-turing-way/the-turing-way
mv the-turing-way project
Publish directory:
project/book/website/_build/htmlBase directory:
book/websiteBuild command:
pip install -r requirements.txt && jupyter-book build .This will give an error, but after installing key files. So just ignore & follow these instructions:
pip uninstall sphinx sphinx-panels jupyter-book sphinxcontrib-applehelp sphinxcontrib-devhelp sphinxcontrib-jsmath sphinxcontrib-htmlhelp sphinxcontrib-serializinghtml sphinxcontrib-qthelp sphinx-design sphinx-external-toc pydata-sphinx-theme sphinx-jupyterbook-latex sphinx-book-theme myst-nb myst-parser
pip install "sphinx>=5.0,<6.0" sphinxcontrib-applehelp sphinxcontrib-devhelp sphinxcontrib-jsmath sphinxcontrib-htmlhelp sphinxcontrib-serializinghtml sphinxcontrib-qthelp sphinx-design "sphinx-external-toc<2" "pydata-sphinx-theme>=0.15.2" "sphinx-jupyterbook-latex<2" "sphinx-book-theme>=1.1.0,<2" "myst-nb<3" "myst-parser<3" "jupyter-book>=0.12.0" "sphinx-thebe>=0.3,<1" sphinx-panels
jupyter-book build .
git credential-cache exit#
git credential-cache exit
cd home/book/website
git add ./*
45 wiki-style jb#
# myenv
git clone https://github.com/abikesa/workflow && mv workflow new && new/setup_myenv.sh && source myenv/bin/activate
# template
git clone https://github.com/the-turing-way/the-turing-way
mv the-turing-way kenny
cd kenny/book/website
pip install -r requirements.txt && jupyter-book build .
# error message
pip uninstall sphinx sphinx-panels jupyter-book sphinxcontrib-applehelp sphinxcontrib-devhelp sphinxcontrib-jsmath sphinxcontrib-htmlhelp sphinxcontrib-serializinghtml sphinxcontrib-qthelp sphinx-design sphinx-external-toc pydata-sphinx-theme sphinx-jupyterbook-latex sphinx-book-theme myst-nb myst-parser
pip install "sphinx>=5.0,<6.0" sphinxcontrib-applehelp sphinxcontrib-devhelp sphinxcontrib-jsmath sphinxcontrib-htmlhelp sphinxcontrib-serializinghtml sphinxcontrib-qthelp sphinx-design "sphinx-external-toc<2" "pydata-sphinx-theme>=0.15.2" "sphinx-jupyterbook-latex<2" "sphinx-book-theme>=1.1.0,<2" "myst-nb<3" "myst-parser<3" "jupyter-book>=0.12.0" "sphinx-thebe>=0.3,<1" sphinx-panels
jupyter-book build .
# big files
rm -rf figures
rm -rf _build/html/_images
# parent directory
cd ~/documents/hades
# block ghp-import (use netlify or import manually)
new/jbb_https.sh
46 everyday#
Create & destroy, everyday! That should be our motto!!
1 myenv#
git clone https://github.com/abikesa/workflow && mv workflow new && new/setup_myenv.sh && source myenv/bin/activate
2 clone & rm#
git clone https://github.com/the-turing-way/the-turing-way
mv the-turing-way cnd
3 _toc.yml#
Keep only 3 sections as template for structure
cat cnd/book/website/_toc.yml
Welcome
Forward
Guide for Reproducible Research
Guide for Project Design
pd-overview
pd-overview-methods
4 requirements.txt#
This gives an error on Athena & Hades, but not on Poseidon
cd cnd/book/website
pip install -r requirements.txt && jupyter-book build .
And here’s the fix for Athena & Poseidon
pip uninstall sphinx sphinx-panels jupyter-book sphinxcontrib-applehelp sphinxcontrib-devhelp sphinxcontrib-jsmath sphinxcontrib-htmlhelp sphinxcontrib-serializinghtml sphinxcontrib-qthelp sphinx-design sphinx-external-toc pydata-sphinx-theme sphinx-jupyterbook-latex sphinx-book-theme myst-nb myst-parser
pip install "sphinx>=5.0,<6.0" sphinxcontrib-applehelp sphinxcontrib-devhelp sphinxcontrib-jsmath sphinxcontrib-htmlhelp sphinxcontrib-serializinghtml sphinxcontrib-qthelp sphinx-design "sphinx-external-toc<2" "pydata-sphinx-theme>=0.15.2" "sphinx-jupyterbook-latex<2" "sphinx-book-theme>=1.1.0,<2" "myst-nb<3" "myst-parser<3" "jupyter-book>=0.12.0" "sphinx-thebe>=0.3,<1" sphinx-panels
jupyter-book build .
5 rm#
Can skip this since step #3 sanized the repo
rm -rf figures
rm -rf _build/html/_images
6 new/jbb_https.sh#
Prepare to push the .git
cd ~/documents/athena
new/jbb_https.sh
7 ghp-import#
git clone https://github.com/abikesa/everyday/
mv cnd/book/website/_build everyday/book/website/_build
47 scp ~/.ssh/id_rca#
Certainly! Here’s a summarized step-by-step guide for transferring your SSH private key from Poseidon (iMacPro) to Athena (Studio Pro) and ensuring everything is set up correctly:
Summary: Transfer SSH Key from Poseidon to Athena#
Find the Username and Hostname/IP Address of Athena
On Athena, open Terminal and run:
whoami hostname hostname -INote the username, hostname, and IP address.
Ensure SSH is Installed and Running on Athena
Check if SSH is installed:
ssh -VEnsure SSH service is running:
sudo systemsetup -getremotelogin sudo systemsetup -setremotelogin on # If not already on sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist # Start SSH service
Configure SSH Daemon on Athena
Edit the SSH configuration file:
sudo nano /etc/ssh/sshd_config
Ensure the following lines are uncommented:
Port 22 AddressFamily any ListenAddress 0.0.0.0 ListenAddress ::
Restart SSH service:
sudo launchctl unload /System/Library/LaunchDaemons/ssh.plist sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist
Check and Configure Firewall on Athena
Ensure firewall allows SSH:
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /usr/sbin/sshd sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblockapp /usr/sbin/sshd
Transfer SSH Key from Poseidon to Athena
On Poseidon, use
scpto copy the SSH key:scp ~/.ssh/id_rsa yourusername@athena.local:/home/yourusername/.ssh/
Or, if using IP address:
scp ~/.ssh/id_rsa yourusername@192.168.1.100:/home/yourusername/.ssh/
Set Correct Permissions on Athena
SSH into Athena:
ssh yourusername@athena.localOr, if using IP address:
ssh yourusername@192.168.1.100Set the correct permissions for the SSH key:
chmod 600 ~/.ssh/id_rsa
Verify the Transfer
Navigate to the
.sshdirectory on Athena and list the files:cd ~/.ssh ls -la
Example Commands Summary#
Find username and hostname/IP address:
whoami hostname hostname -IEnsure SSH is installed and running:
ssh -V sudo systemsetup -getremotelogin sudo systemsetup -setremotelogin on sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist
Configure SSH daemon:
sudo nano /etc/ssh/sshd_config
Uncomment:
Port 22 AddressFamily any ListenAddress 0.0.0.0 ListenAddress ::
Restart SSH service:
sudo launchctl unload /System/Library/LaunchDaemons/ssh.plist sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist
Configure firewall:
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /usr/sbin/sshd sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblockapp /usr/sbin/sshd
Transfer SSH key using
scp:scp ~/.ssh/id_rsa yourusername@athena.local:/home/yourusername/.ssh/
Or, using IP address:
scp ~/.ssh/id_rsa yourusername@192.168.1.100:/home/yourusername/.ssh/
Set correct permissions:
ssh yourusername@athena.localOr, using IP address:
ssh yourusername@192.168.1.100Then set permissions:
chmod 600 ~/.ssh/id_rsa
Verify the transfer:
cd ~/.ssh ls -la
By following these steps, you should have successfully transferred your SSH key from Poseidon to Athena and ensured the proper configuration and permissions.
48 new/setup.sh#
#! /bin/bash
# setup tidy work directory
read -p "Enter your root directory (default: /documents/rhythm): " ROOT_DIR
ROOT_DIR=${ROOT_DIR:-/documents/rhythm}
read -p "Enter the name of the subdirectory that archives .sh scripts (default: new): " SUBDIR_NAME
SUBDIR_NAME=${SUBDIR_NAME:-new}
cd ~/$ROOT_DIR && rm -rf * && git clone https://github.com/abikesa/workflow && mv workflow $SUBDIR_NAME && $SUBDIR_NAME/setup_myenv.sh && source myenv/bin/activate
# template as starting point
read -p "Enter template GitHub repository name (default: template-repo): " REPO_NAME
REPO_NAME=${REPO_NAME:-template-repo}
git clone https://github.com/abikesa/$REPO_NAME
mv $REPO_NAME local
cd local/kitabo/ensi
echo "Make updates to $ROOT_DIR/local"
49 new/jbp-https-branch.sh#
#!/bin/bash
read -p "Enter your GitHub username (default: abikesa): " GITHUB_USERNAME
GITHUB_USERNAME=${GITHUB_USERNAME:-abikesa}
read -p "Enter your GitHub repository name (default: worthy): " REPO_NAME
REPO_NAME=${REPO_NAME:-worthy}
read -p "Enter your email address (default: abikesa.sh@gmail.com): " EMAIL_ADDRESS
EMAIL_ADDRESS=${EMAIL_ADDRESS:-abikesa.sh@gmail.com}
read -p "Enter your root directory (e.g., ~/Dropbox/1f.ἡἔρις,κ/1.ontology, default: $(pwd)): " ROOT_DIR
ROOT_DIR=${ROOT_DIR:-$(pwd)}
read -p "Enter the name of the subdirectory to be built within the root directory (default: local): " SUBDIR_NAME
SUBDIR_NAME=${SUBDIR_NAME:-local}
read -p "Enter the name of the new branch (default: experiment-branch): " NEW_BRANCH
NEW_BRANCH=${NEW_BRANCH:-experiment-branch}
read -p "Enter your commit statement: " COMMIT_THIS
# Navigate to the root directory
cd "$ROOT_DIR" || { echo "Failed to navigate to root directory"; exit 1; }
# Ensure the 'local' directory exists
if [ ! -d "$SUBDIR_NAME" ]; then
echo "The '$SUBDIR_NAME' directory does not exist in the root directory."
exit 1
fi
# Set Git configuration
git config --global user.name "$GITHUB_USERNAME"
git config --global user.email "$EMAIL_ADDRESS"
# Remove previous build and repository directory if they exist
rm -rf "$SUBDIR_NAME/_build"
jb build "$SUBDIR_NAME"
rm -rf "$REPO_NAME"
# Clone the repository
git clone "https://github.com/$GITHUB_USERNAME/$REPO_NAME.git"
if [ ! -d "$REPO_NAME" ]; then
echo "Failed to clone the repository. Check your GitHub username, repository name, and permissions."
exit 1
fi
# Copy the contents of the 'local' directory to the cloned repository
cp -r "$SUBDIR_NAME"/* "$REPO_NAME"
cd "$REPO_NAME" || { echo "Failed to navigate to the repository directory"; exit 1; }
# Create and switch to the new branch
git checkout -b "$NEW_BRANCH"
# Add, commit, and push the changes
git add ./*
git commit -m "$COMMIT_THIS"
git push -u origin "$NEW_BRANCH"
if [ $? -ne 0 ]; then
echo "Failed to push to the repository. Check your credentials and GitHub permissions."
exit 1
fi
echo "Changes in the '$SUBDIR_NAME' directory have been pushed to the '$NEW_BRANCH' branch in the $GITHUB_USERNAME/$REPO_NAME repository!"
50 git push origin main --force#
Got it. If you have a perfectly fine local directory called “new” that contains the correct state of your repository, you can use it to restore your main branch. Here are the steps to do that from your terminal: (This can also be used to replace a simple page with a jupyter book)
Step-by-Step Guide#
Navigate to your repository:
cd /path/to/your/repository
Delete all files in your current repository (make sure you back up any important files before doing this):
git rm -rf .
Copy the contents of the “new” directory into your current repository:
cp -r /path/to/new/* .
Add the new files to the staging area:
git add .
Commit the changes:
git commit -m "Restored main branch from local directory 'new'"
Force push to the remote repository:
git push origin main --force
Full Command Sequence#
Here is the full sequence of commands you can copy and paste into your terminal:
cd /path/to/your/repository
git rm -rf .
cp -r /path/to/new/* .
git add .
git commit -m "Restored main branch from local directory 'new'"
git push origin main --force
Explanation#
Navigate to your repository: Replace
/path/to/your/repositorywith the actual path to your Git repository.Delete all files in your current repository: This command removes all files tracked by Git. Use this with caution and ensure you have backups of important files.
Copy the contents of the “new” directory: Replace
/path/to/newwith the actual path to your “new” directory. This command copies all files from the “new” directory to your repository directory.Add the new files to the staging area: This command stages all the new files for commit.
Commit the changes: This command commits the new state of the repository with an appropriate message.
Force push to the remote repository: This command updates the remote repository to match your local repository, overwriting the remote main branch.
By following these steps, you will successfully restore your main branch using the contents of the “new” directory.
51 .video-grid {#
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>3x3 YouTube Video Matrix</title>
<style>
.video-grid {
display: grid;
grid-template-columns: repeat(3, 1fr);
gap: 10px;
}
.video-grid iframe {
width: 100%;
height: 315px;
}
</style>
</head>
<body>
<div class="video-grid">
<iframe src="https://www.youtube.com/embed/C5cuKwNJiUs" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<iframe src="https://www.youtube.com/embed/qf69KlraCvU" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<iframe src="https://www.youtube.com/embed/D3rQLKlUBXU" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<iframe src="https://www.youtube.com/embed/V5O7dC9X5dA" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<iframe src="https://www.youtube.com/embed/ViwtNLUqkMY" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<iframe src="https://www.youtube.com/embed/bbqVg_23otg" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<iframe src="https://www.youtube.com/embed/pnLGmjcgLQw" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<iframe src="https://www.youtube.com/embed/SwwbP4kB-4Y" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
</body>
</html>
52 brew install ffmpeg#
It looks like the ffmpeg package you installed is a Python wrapper, not the actual FFmpeg binary needed for conversion. To use FFmpeg from the command line, you need to install the FFmpeg binary itself.
Here’s how to install FFmpeg on macOS using Homebrew, which is the recommended way:
Install Homebrew (if you don’t have it already): Open your terminal and paste the following command:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Install FFmpeg (here’s where I started the process; it took
forever, so be patient!): Once Homebrew is installed, run the following command to install FFmpeg:brew install ffmpeg
Convert the audio file: After FFmpeg is installed, you can convert the audio file using the following command:
ffmpeg -i ii-v-I.m4a ii-v-I.mp3
Detailed Steps:#
Install Homebrew: If you haven’t already installed Homebrew, open your terminal and run:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Install FFmpeg: With Homebrew installed, you can now install FFmpeg by running:
brew install ffmpeg
Convert the .m4a file to .mp3: Once FFmpeg is installed, you can use it to convert your file:
ffmpeg -i ii-v-I.m4a ii-v-I.mp3
Verify the conversion: Ensure that the new .mp3 file has been created in the same directory (and in the
_build/htmlextension as well).
This should resolve the issue, allowing you to convert your audio files and embed them in your Jupyter Book successfully.
Embed your files
<audio controls style="width: 100%;">
<source src="../../media/ii-v-I.mp3" type="audio/mp3">
Your browser does not support the audio element.
</audio>
53 sphinx#
Claude 3.5 sorted this out in first iteration. GPT-4o after 10 or so iterations frustrated me & failed.
It looks like there are a few issues we need to address. Let’s go through them step by step:
Unknown config value ‘bibtex_reference_order’: Remove this line from your
_config.yml:bibtex_reference_order: 'citation'
This option is not recognized by the current version of sphinxcontrib-bibtex.
Plugin not found error: The error suggests that the ‘numeric’ style for sphinxcontrib-bibtex is not found. This could be due to an outdated version of sphinxcontrib-bibtex. Let’s update it:
pip install --upgrade sphinxcontrib-bibtex
After updating, modify your
_config.ymlto use the correct configuration for numeric citations:sphinx: config: bibtex_default_style: 'plain' bibtex_reference_style: 'author_year'
Instead of using a custom CSL file, we’ll use the built-in styles. Add this to your
_config.yml:sphinx: config: bibtex_cite_style: 'numeric' bibtex_footbibliography_header: ''
In your Markdown files, you can now use citations like this:
This is a citation {cite}`muzaale2014risk`.For your bibliography section, use:
# Bibliography ```{bibliography}
After making these changes, try building your book again:
jb build .
If you still encounter issues, please provide the new error message, and we can troubleshoot further.
Remember, the exact configuration might depend on the specific versions of Jupyter Book and sphinxcontrib-bibtex you’re using. If you continue to have problems, you might want to check your installed versions and ensure they’re compatible:
pip list | grep jupyter-book
pip list | grep sphinxcontrib-bibtex
Let me know if you need any clarification or if you encounter any new errors after making these changes.
54 unsrt#
sphinx:
extra_extensions :
- 'sphinx_panels'
- 'sphinxcontrib.bibtex'
config : # key-value pairs to directly over-ride the Sphinx configuration
language : en
html_show_copyright : false
suppress_warnings :
- 'app.add_node'
- 'app.add_directive'
- 'app.add_role'
myst_heading_anchors : 5
bibtex_bibfiles :
- _bibliography/references.bib
bibtex_reference_order: 'citation'
bibtex_default_style: 'unsrt' # 'plain'
bibtex_reference_style: 'label' # 'author_year'
bibtex_cite_style: 'numeric'
bibtex_footbibliography_header: ''
55 template.sh#
# A default configuration that will be loaded for all jupyter books
# Users are expected to override these values in their own `_config.yml` file.
# This is also the "master list" of all allowed keys and values.
#######################################################################################
# Book settings
title : Template # The title of the book. Will be placed in the left navbar.
author : # The author of the book
copyright : "2025" # Copyright year to be placed in the footer
logo : "https://github.com/jhufena/jhufena.github.io/blob/main/png/hub_and_spoke.jpg?raw=true" # A path to the book logo
email : "abikesa.sh@gmail.com"
exclude_patterns : ["LICENSE.md"] # Patterns to skip when building the book. Can be glob-style (for example "*skip.ipynb")
#######################################################################################
# Execution settings
execute:
execute_notebooks : auto # Whether to execute notebooks at build time. Must be one of ("auto", "force", "cache", "off")
cache : "" # A path to the jupyter cache that will be used to store execution artifacts. Defaults to `_build/.jupyter_cache/`
exclude_patterns : ["LICENSE.md"] # A list of patterns to *skip* in execution (for example a notebook that takes a really long time)
#######################################################################################
# HTML-specific settings
html:
navbar_number_sections : False # Add a number to each section in your left navbar
home_page_in_navbar : False # Whether to include your home page in the left Navigation Bar; I like this!!!!!!!
use_repository_button : False # Whether to add an "Repository" button to pages. If `true`, repository information in repository: must be filled in
use_issues_button : False # Whether to add an "Open issue" button to pages. If `true`, repository information in repository: must be filled in
use_edit_page_button : False # Whether to add an "Suggest edit" button to pages. If `true`, repository information in repository: must be filled in
extra_footer : |
Copyright © 2025 ADM
comments:
hypothesis : False # For data collection in top right corner
extra_css:
- "_static/custom.css"
#######################################################################################
# Launch button settings
launch_buttons:
notebook_interface : "classic" # The interface interactive links will activate ["classic", "jupyterlab"]
binderhub_url : "https://mybinder.org" # The URL of the BinderHub (for example, https://mybinder.org)
jupyterhub_url : "" # The URL of the JupyterHub (for example, https://datahub.berkeley.edu)
thebelab : false # Add a thebelab button to pages (requires the repository to run on Binder)
repository:
url : https://github.com/abikesa/template # The URL to your book's repository
path_to_book : "book/website" # A path to your book's folder, relative to the repository root.
branch : main
#######################################################################################
# Advanced and power-user settings
sphinx:
extra_extensions :
- 'sphinx_panels'
- 'sphinxcontrib.bibtex'
config : # key-value pairs to directly over-ride the Sphinx configuration
language : en
html_show_copyright : false
suppress_warnings :
- 'app.add_node'
- 'app.add_directive'
- 'app.add_role'
myst_heading_anchors : 5
bibtex_bibfiles :
- _bibliography/references.bib
bibtex_reference_order: 'citation'
bibtex_default_style: 'unsrt' # 'plain'
bibtex_reference_style: 'super' # 'label' # 'author_year' (this worked)
bibtex_cite_style: 'super' #'numeric' (for diff. jb version)
bibtex_footbibliography_header: ''
56 perplexity.ai#
Jupyter Books support several variants of the {note} directive, which are known as “admonitions.” These are used to highlight important information in a structured way. Here are the different types of admonitions you can use in Jupyter Books:
Note:
```{note} This is a note.Warning:
```{warning} This is a warning.Important:
```{important} This is important.Tip:
```{tip} This is a tip.Caution:
```{caution} This is a caution.Attention:
```{attention} This is an attention.Admonition:
```{admonition} This is an admonition.
These directives help in organizing and emphasizing content in Jupyter Books, making the information more accessible and visually distinct for readers[1].
Citations:
[1] jupyter-book/jupyter-book
[2] https://discourse.jupyter.org/t/inline-variable-insertion-in-markdown/10525
[3] https://www.datacamp.com/blog/jupyter-and-r-markdown-notebooks-with-r
[4] https://www.bmc.com/blogs/installing-jupyter-for-big-data-and-analytics/
[5] https://stackoverflow.com/questions/34968112/how-to-give-jupyter-cell-standard-input-in-python
57 clear_dirs.sh update#
#!/bin/bash
# Ask for the directory to change to
echo "Enter the directory to change to (relative to ~/documents):"
read dir
# Change to the specified directory
cd ~/documents/"$dir" || { echo "Directory not found"; exit 1; }
# Loop through all items in the directory
for item in *; do
# Check if the item is a directory and not "kitabo"
if [ -d "$item" ]; then
if [ "$item" != "kitabo" ] && ! [[ $item =~ ^[1-6]-.* ]]; then
# Remove the directory and its contents
rm -rf "$item"
echo "Deleted directory $item"
fi
elif [ -f "$item" ]; then
# Check if the file should be deleted
if [[ $item == _file* ]]; then
rm "$item"
echo "Deleted file $item"
elif [[ $item == *.* ]]; then
if ! [[ $item =~ ^[1-6]-.* ]]; then
rm "$item"
echo "Deleted file $item"
fi
else
rm "$item"
echo "Deleted file $item"
fi
fi
done
echo "Finished deleting directory contents"
58. {figure} ../figures/image.*#
To adapt the figure directive in Jupyter Book to include different types of media and ensure appropriate labeling, you can use custom directives and captions. Here’s a way to distinguish different media types such as audio, video, and images:
Images: Continue using the
figuredirective for traditional images.Audio and Video: Create custom directives or use the
embeddirective provided by MyST.
Adapting for Images#
For images, you can continue using the figure directive as you normally would:
```{figure} /path/to/image.png
---
name: fig:my_image
---
This is an image.
Custom Directives for Audio and Video#
For audio and video, you can use HTML or the embed directive to properly integrate and label these media types:
Audio#
To include audio with proper labeling, use HTML and MyST capabilities to create a custom caption:
```{admonition} Audio 1: My Audio Description
:class: note
Video#
For video, you can do something similar:
```{admonition} Video 1: My Video Description
:class: note
Advanced Customization#
If you prefer a more structured approach, you can define custom roles or directives in MyST to handle different media types. This allows for consistent styling and automated numbering.
Custom Directive Example#
You can define a custom directive in your _config.yml or use Sphinx extensions:
sphinx:
config:
myst_enable_extensions:
- colon_fence
- html_admonition
- html_image
And then in your markdown file:
::::{grid} 1 2 2 3
:gutter: 3
:::{grid-item-card}
```{admonition} Audio 1: My Audio Description
:class: note
Summary
By using custom captions with HTML or MyST directives, you can clearly distinguish between different types of media in your Jupyter Book. This approach ensures your content is accessible and correctly labeled, enhancing the user experience with modern media integrations.
59. jb_build.sh && cp -r dir/*
Beyond figures in books: supporting multimodal aids to dynamic content
mkdir -p _build/html/pdfs _build/html/figures _build/html/media
cp -r pdfs/* _build/html/pdfs/
cp -r media/* _build/html/media/
cp -r act1/app/* _build/html/act1/app
60. scripts/clear_dirs.sh 08/07/24 version
#!/bin/bash
# Ask for the directory to change to
echo "Enter the directory to change to (relative to ~/documents):"
read dir
# Change to the specified directory
cd ~/documents/"$dir" || { echo "Directory not found"; exit 1; }
# Loop through all items in the directory
for item in *; do
# Check if the item is a directory
if [ -d "$item" ]; then
# If the directory matches the pattern [1-6]-*
if [[ $item =~ ^[1-6]-.* ]]; then
# Remove the contents of the directory
rm -rf "$item"/*
echo "Deleted contents of directory $item"
# If the directory is not "kitabo" and does not match the pattern
elif [ "$item" != "kitabo" ]; then
# Remove the directory and its contents
rm -rf "$item"
echo "Deleted directory $item"
fi
elif [ -f "$item" ]; then
# Check if the file should be deleted
if [[ $item == _file* ]]; then
rm "$item"
echo "Deleted file $item"
elif [[ $item == *.* ]]; then
if ! [[ $item =~ ^[1-6]-.* ]]; then
rm "$item"
echo "Deleted file $item"
fi
else
rm "$item"
echo "Deleted file $item"
fi
fi
done
echo "Finished deleting directory contents"
61 from twilio.rest import Client
To create a reminder to subscribe and follow “Musical Freedom” on YouTube, you can use a combination of Python and third-party services like Twilio for SMS or email reminders. If you prefer GitHub, you can set up a GitHub Action that triggers an email reminder. Here’s a couple of approaches you can take:
1. Python Script with Twilio for SMS Reminders
If you prefer SMS reminders, you can use Twilio, which allows you to send SMS messages through a simple Python script.
from twilio.rest import Client
from datetime import datetime, timedelta
# Your Twilio account SID and Auth Token
account_sid = 'your_account_sid'
auth_token = 'your_auth_token'
client = Client(account_sid, auth_token)
# Set the reminder time
reminder_time = datetime.now() + timedelta(days=1) # Set to remind you in 1 day
# Send SMS reminder
if datetime.now() >= reminder_time:
message = client.messages.create(
body="Reminder: Subscribe and follow Musical Freedom on YouTube!",
from_='+your_twilio_number',
to='+your_phone_number'
)
print(f"Reminder sent: {message.sid}")
2. GitHub Actions for Email Reminders
If you want to use GitHub to send an email reminder, you can create a GitHub Action that triggers an email. First, you need to set up a repository and create an action in the .github/workflows directory.
Here’s a simple workflow that sends an email using the actions-sendgrid action:
name: YouTube Reminder
on:
schedule:
- cron: '0 10 * * *' # Runs every day at 10:00 AM
jobs:
send_email:
runs-on: ubuntu-latest
steps:
- name: Send Email Reminder
uses: dawidd6/action-send-mail@v3
with:
server_address: 'smtp.sendgrid.net'
server_port: '587'
username: '${{ secrets.SENDGRID_USERNAME }}'
password: '${{ secrets.SENDGRID_API_KEY }}'
subject: 'Reminder to Subscribe to Musical Freedom on YouTube'
body: 'Don’t forget to subscribe and follow Musical Freedom on YouTube!'
from: 'your-email@example.com'
to: 'your-email@example.com'
You’ll need to set up SendGrid (or another SMTP service) and add your credentials as secrets in your GitHub repository.
3. Jupyter Notebooks with Email Reminders
You can also set up a reminder through a Jupyter Notebook. Here’s a simple example using the smtplib library for email reminders:
import smtplib
from email.mime.text import MIMEText
from datetime import datetime, timedelta
import time
# Email details
sender_email = "your-email@example.com"
receiver_email = "your-email@example.com"
password = "your-email-password"
# Create the email content
message = MIMEText("Reminder: Subscribe and follow Musical Freedom on YouTube!")
message['Subject'] = 'YouTube Reminder'
message['From'] = sender_email
message['To'] = receiver_email
# Schedule the reminder for the next day
reminder_time = datetime.now() + timedelta(days=1)
# Wait until the reminder time
while datetime.now() < reminder_time:
time.sleep(60) # Check every minute
# Send the email
with smtplib.SMTP_SSL("smtp.example.com", 465) as server:
server.login(sender_email, password)
server.sendmail(sender_email, receiver_email, message.as_string())
print("Reminder email sent!")
4. WhatsApp Reminder with Twilio
If you prefer WhatsApp:
from twilio.rest import Client
from datetime import datetime, timedelta
# Twilio setup
account_sid = 'your_account_sid'
auth_token = 'your_auth_token'
client = Client(account_sid, auth_token)
# Reminder setup
reminder_time = datetime.now() + timedelta(days=1)
if datetime.now() >= reminder_time:
message = client.messages.create(
body="Reminder: Subscribe and follow Musical Freedom on YouTube!",
from_='whatsapp:+your_twilio_number',
to='whatsapp:+your_phone_number'
)
print(f"WhatsApp Reminder sent: {message.sid}")
Setting Up
Twilio: Sign up at Twilio, get your account SID, auth token, and set up a number.
GitHub Actions: GitHub Actions documentation will help you with setting up secrets and workflows.
SendGrid: If using email, you can get an API key from SendGrid.
You can paste this code into a Jupyter Notebook or a Python script, depending on the method you choose. Let me know which approach you prefer, or if you want to explore another option!
62 scrape YouTube
from youtube_comment_downloader import YoutubeCommentDownloader
# Initialize the downloader
downloader = YoutubeCommentDownloader()
# Replace with your YouTube video ID
video_id = 'VtQorLzzbQw'
# Get comments from the video
comments = downloader.get_comments_from_url(f'https://www.youtube.com/watch?v={video_id}')
# Print comments
for comment in comments:
print(comment['text'])
1. Modes
\
2. GPT -> 4. Latency.Attention -> 5. Unveiled -> 6. Bespoke
/
3. Reinforcement.Feedback
1 Modes
PAIRS@JH as “Eyes” & data-collection
YouTube comments (i.e., text)
Save as .PDF
2 GPT
Upload into GPT-4o for thematic analysis
3 Reinforcement
Music: phonetics, temperament, scales, MQ-TEA, nexToken, ENTarcs
e.g. phrygian mode, flamenco element, arpeggio, trochaic meter for “im-per-fect-for-you”: E-
F-A-C-BF-A-Cinsertion/substitue of 3rd (i.e. G♯)“Dominant” function & lyric-syntactic-semantic consonance of “imperfect” sonic elements
4 Attention
P attention across entire “
6-step-process” above to improve prediction of nexTokenFor instance we impute that we need to pay attention to Gypsies: India-Persia-Arabia-North.Africa-Spain: Andalusia-Flamenco
That’s the origin of the “exotic” otherwordly elements everyone is going nuts about but can’t figure out why
Masterful composition places
constraintson what it admits from Andalusia into this pop song: don’t want to overwhelm the masses :)We have spanish phrygian elements even phonetically in the openning guitar & implied rhythm without accent
Ommitted is the performance, dance, & audience support with syncopated claps
5 Unveiled
Secret behind every listeners emotional response
6 Bespoke
Very personal for me since vocabulary is key element
Particularly for language-memory-intelligence-prediction-anticipation-feedback
62 BeautifulSoup
import requests
from bs4 import BeautifulSoup
# Replace with the URL you want to scrape
url = 'https://www.newyorker.com/culture/cultural-comment/blank-space-what-kind-of-genius-is-max-martin'
# Send a request to the website
response = requests.get(url)
# Check if the request was successful
if response.status_code == 200:
soup = BeautifulSoup(response.content, 'html.parser')
# Example: Find all paragraphs
paragraphs = soup.find_all('p')
for paragraph in paragraphs:
print(paragraph.text)
else:
print(f"Failed to retrieve the webpage. Status code: {response.status_code}")
63
<p>Regarding Shakespeare's protagonists and class. Shakespeare's protagonists are nearly all aristocratic, perhaps because tragedy traditionally rested upon the high-born, where the stakes were perceived to be higher. The only slight deviations are in Henry V with the common soldiers (we few, <a href="https://www.gutenberg.org/cache/epub/2253/pg2253-images.html">we happy few</a> ...), Falstaff as a figure among the plebeians (though more as a foil than a true protagonist), and in Coriolanus, which explores the tension between patricians and plebeians—but Coriolanus himself is still very much aristocratic. So plebeians are worthy only as warriors - which itself is aristocratic. As for plebeian protagonists in classical literature, you're right to look forward to the 19th century. Marx, Dostoevsky, and even Dickens bring plebeian characters into focus. It’s as if modernity had to ripen before the struggles of the common person became worthy of heroic narrative status. Before then, the focus was on kings, nobles, and gods. Of course, <b>Mozart</b> had anticipated this 19th century trend by a century in his <a href="https://www.youtube.com/watch?v=55ik-PzAXsQ">Opera</a>:
<a href="#" onclick="document.getElementById('figaro-text').style.display = (document.getElementById('figaro-text').style.display == 'none' ? 'block' : 'none'); return false;"><em><i>Le Nozze di Figaro</i></em></a>
<div id="figaro-text" style="display:none;">
<p>Here we have an unmistakably plebeian protagonist. Mozart, through the libretto by Lorenzo Da Ponte (adapted from Beaumarchais’ play), places a common servant at the center of the narrative. Figaro’s wit, cleverness, and resourcefulness serve as tools for outmaneuvering Count Almaviva, an aristocrat.</p>
<p>This subversion of class dynamics is one of the reasons <em>The Marriage of Figaro</em> was so revolutionary at the time. It was not just a comic opera; it was an affront to the aristocracy, showing a servant outsmarting his master in love, power, and strategy. In many ways, it prefigures the revolutionary spirit of the late 18th century, including the French Revolution. Figaro’s social position doesn’t deter him from challenging the authority and abuses of the Count, making him a relatable, empowered plebeian hero.</p>
<p>Mozart’s music, too, reflects this subversion. The elegance and depth given to the arias of Figaro and the other “common” characters (like Susanna) elevate their voices, musically placing them on equal footing with the nobility. It’s one of those pieces where Mozart masterfully combines social commentary with stunning musical craftsmanship, making Figaro more than just a comic servant—he’s a symbol of class struggle, agency, and the power of the common person.</p>
</div>
</p>
The href="#" in an anchor (<a>) tag is commonly used as a placeholder to create a clickable link that doesn’t navigate to another page. The # refers to the top of the current page, but when combined with JavaScript (like in your example), it serves as a dummy URL, essentially keeping the user on the current page while allowing the onclick event to perform some action.
In your case, the href="#" does nothing because the onclick JavaScript is handling the action. The return false; at the end of the onclick ensures that the default action of the link (which would be jumping to the top of the page) is prevented.
If you omit the return false;, clicking the link would still run the JavaScript, but the page would also scroll to the top (or refresh the view) due to the #. So return false; stops that from happening.
<a href="#" onclick="document.getElementById('figaro-text').style.display = (document.getElementById('figaro-text').style.display == 'none' ? 'block' : 'none'); return false;" style="color: gray;">
`
64 zipfile
Ask GPT-4o to edit a jb hosted by GitHub!
import zipfile
import os
# Function to compress files into a zip archive
def compress_to_zip(output_filename, folder_path):
with zipfile.ZipFile(output_filename, 'w', zipfile.ZIP_DEFLATED) as zipf:
# Walk the directory and add files
for root, dirs, files in os.walk(folder_path):
for file in files:
file_path = os.path.join(root, file)
relative_path = os.path.relpath(file_path, folder_path)
print(f"Adding {relative_path} to zip.") # Print for debugging
zipf.write(file_path, relative_path)
# Define the folder path and output zip file
clone_dir = os.path.expanduser('~/documents/rhythm/workflow') # Convert to absolute path
output_zip = 'workflow_compressed.zip' # Name of the output zip file
# Check if the folder has files
if not os.listdir(clone_dir):
print("Directory is empty!")
else:
compress_to_zip(output_zip, clone_dir)
print(f"Compressed repository into {output_zip}")
65 :class:
Variations on “class” for Jupyter books
Here’s a table with some commonly used class variations for Jupyter Book admonition blocks:
Class |
Description |
|---|---|
|
Indicates a helpful tip or suggestion. |
|
General information or clarification. |
|
Highlights potential issues or things to watch out for. |
|
Used for more severe warnings or cautionary notes. |
|
Points to related content or additional resources. |
|
Provides a subtle suggestion or piece of advice. |
|
Emphasizes critical information. |
|
Similar to warning, but often used for more moderate cautions. |
These can be added to admonition blocks in Jupyter Book markdown, using :class: followed by the desired class, as you demonstrated.
66 ls -l ../..
/
├── Applications
│ ├── GarageBand.app
│ ├── JustJoin.app
│ ├── Keynote.app
│ ├── Microsoft Outlook.app
│ ├── Numbers.app
│ ├── Pages.app
│ ├── R.app
│ ├── Safari.app (symlink to system)
│ ├── Stata
│ ├── Utilities
│ ├── Visual Studio Code.app
│ ├── Zoom for Safari.app
│ ├── chromedriver_mac64
│ ├── googlechrome.dmg
│ ├── iMovie.app
│ └── zoom.us.app
├── Library
├── System
├── Users
│ ├── Shared
│ └── apollo
│ ├── Desktop
│ ├── Documents
│ ├── Downloads
│ ├── Library
│ ├── Movies
│ ├── Music
│ ├── Pictures
│ └── Public
├── Volumes
├── bin
├── cores
├── dev
├── etc -> private/etc
├── home -> /System/Volumes/Data/home
├── opt
├── private
├── sbin
├── tmp -> private/tmp
├── usr
└── var -> private/var
67 The Economist & Lifestyle Magazines
Might we forge similarly honest and unantagonistic ways to communicate with each other in the workplace and the wider world? The obstacle, of course, is our own hard-wired defences, and especially the anxiety that open disagreement will draw rejection. In a fiercely hierarchical world of bosses and middle managers and underlings, is the very idea of such openness a naive pipe dream? ■
<span style="color: red;">■</span>
<span style="display: inline-block; width: 20px; height: 20px; background-color: red; border-radius: 50%;"></span>
68 Color
<div style="background-color: paleTurquoise; padding: 10px; margin: 10px; font-weight: bold;">
Melancholy (past)
</div>
<p style="color: paleTurquoise; font-weight: bold;">
Melancholy (past)
</p>
69 YouTube
<iframe
src="https://www.youtube.com/embed/uL8K7jylCKg"
width="560"
height="315"
frameborder="0"
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
allowfullscreen
title="YouTube video player">
</iframe>
70 Video
To display video files instead of audio files, you’ll need to use the <video> tag with appropriate controls. Here’s the corrected version of your code:
<video controls style="width: 100%;">
<source src="../media/contrail_1.MP4" type="video/mp4">
Your browser does not support the video element.
</video>
<video controls style="width: 100%;">
<source src="../media/contrail_2.MP4" type="video/mp4">
Your browser does not support the video element.
</video>
<video controls style="width: 100%;">
<source src="../media/contrail_3.MP4" type="video/mp4">
Your browser does not support the video element.
</video>
Explanation:
<video>Tag: Replaced<audio>with<video>to accommodate video files.File Type: Changed
type="audio/mp3"totype="video/mp4".Controls: Retained the
controlsattribute to provide a playback interface.Style: Kept the
style="width: 100%;"for responsive design.
This ensures the videos will display properly and provide playback controls.
If you’re embedding external video files (e.g., from a website or local server), you can use an <iframe> tag, but it’s typically reserved for embedding content from other web pages (like YouTube or Vimeo). For standalone videos hosted locally or on your own server, <video> is the correct and standard HTML5 element to use.
Here’s why <video> is preferred for self-hosted files:
Direct Playback: The
<video>element provides built-in controls for playing video files directly in the browser.Simpler Setup: Unlike
<iframe>, you don’t need additional HTML or JavaScript to ensure the correct functionality of embedded content.
That said, if you want to use an <iframe> (e.g., for embedding a pre-configured media player or special use cases), here’s how it would look:
Using <iframe>:
<iframe src="../media/contrail_1.MP4" style="width: 100%; height: 500px;" frameborder="0" allowfullscreen></iframe>
<iframe src="../media/contrail_2.MP4" style="width: 100%; height: 500px;" frameborder="0" allowfullscreen></iframe>
<iframe src="../media/contrail_3.MP4" style="width: 100%; height: 500px;" frameborder="0" allowfullscreen></iframe>
Key Differences:
Customization: The
<video>tag gives more control over playback features (like custom styling, captions, etc.).<iframe>Use Case: Best for embedding third-party-hosted videos, not for local/self-hosted media.
For locally hosted files, stick with <video>. Use <iframe> only if you’re embedding from another platform or need additional functionality that the <video> tag doesn’t natively support.
Great! Let me know if you need help tweaking the <video> tag setup or experimenting with <iframe> for any specific scenarios. Happy coding! 🚀
71 .HEIC
#!/bin/bash
# Define the source directory
SOURCE_DIR=~/desktop
OUTPUT_DIR="$SOURCE_DIR/converted_jpegs"
# Create the output directory if it doesn't exist
mkdir -p "$OUTPUT_DIR"
# Loop through all .heic files and convert them to .jpeg
for file in "$SOURCE_DIR"/*.HEIC; do
if [[ -f "$file" ]]; then
filename=$(basename -- "$file")
output_filename="${filename%.*}.jpeg"
output_path="$OUTPUT_DIR/$output_filename"
echo "Converting $file to $output_path..."
convert "$file" "$output_path"
fi
done
echo "All .heic files have been converted to .jpeg in $OUTPUT_DIR."