# Run "test" script on all packages
npm run test --workspaces


# Tip - this also works:
npm run test  -ws

----------------------------------------------------


# Runs "test" only on package-a
npm run test --workspace package-a


# Tip - this also works:
npm run test -w package-a

----------------------------------------------------


# Install `lodash` on `package-a`
npm install lodash --workspace package-a


# Install `tap` on `package-b` as a dev dependency
npm install tap --workspace package-b --save-dev


# Install `package-a` on `package-b`
npm install package-a --workspace package-b


# Install `eslint` in all packages
npm install eslint --workspaces

for region in `aws ec2 describe-regions --output text | cut -f4`
do
     echo -e "\nListing Instances in region:'$region'..."
     aws ec2 describe-instances --query 'Reservations[*].Instances[*].{Instance:InstanceId,Subnet:SubnetId}' --region $region
done
#This script is to be used with any AWS CLI configured environment, it will list any EC2 instances and their associated subnet network ID's in JSON format

#Leif Messinger

#For when you want to search a lot of words in a file fast


#Arg 1 is the argument the list of words you want to search

#Arg 2 is the file you want to search


#-z means that it looks at the file as a whole, just treating newlines a characters.

#-r is regex. Needed for $, even tho the documentation says you don't need it. They are liars.

#First command replaces all . with \. and all - with \-

#Second command takes all newlines and replaces them with )|(

#Third command takes the trailing |( and deletes it

#Forth command puts a /( at the start

#Fith command puts /!d at the end. This tells it to not delete any lines that match the pattern.


#The second sed takes the output of the first sed as a command that searches any of the combined words

#-f - takes a command from the input
sed -z -r -e 's/\./\\\./g ; s/\-/\\\-/g' -e 's/\n/\)\|\(/g' -e 's/\|\($//' -e 'i/\(' -e 'a/!d' $1 | sed -r -f - $2

#!/bin/bash

#Originally made by Isaac Cook https://gist.github.com/icook/5400173

#Modified by Leif Messinger

#upload_key.sh [server_ip [server2_ip [...]]]

#To be run locally on a linux computer

if [ -e ~/.ssh/id_rsa.pub ];
then
    echo "SSH Key already exists on local machine"
else
    echo "Generating SSH key on local machine"
    ssh-keygen -t rsa   #generates id_rsa and id_rsa.pub
    chmod -R 700 ~/.ssh #Sets permissions of ssh folder
    ssh-add     #Adds keys (and passwords?) to ssh_agent. (hopefully doesn't require password)
fi

echo "Loading client public key into memory"
pubKey=$(<~/.ssh/id_rsa.pub)

for server
do
    echo "Adding client public key to $server remote server authorized keys"
    #Idiot Isaac Cook didn't know about ssh-copy-id
    #ssh-copy-id even checks if your key already exists
    #In fairness, I didn't either until researching ssh-add
    ssh-copy-id -i ~/.ssh/id_rsa.pub $server        #In theory, this should prompt for a username

    #ssh $server "mkdir -p ~/.ssh;  #Make the folder if not already made
    #       echo \"$pubKey\" >> ~/.ssh/authorized_keys;     #Append your public key to the server's authorized_keys
    #       chmod 700 ~/.ssh && chmod 600 ~/.ssh/authorized_keys"   #Set the correct permissions of those files

    #echo "Adding server public key to local authorized keys"
    #ssh $server "ssh-copy-id -i ~/.ssh/id_rsa.pub \$SSH_CLIENT" #this might need some awk, as $SSH_CLIENT spits out clientip portnumber

    echo "Displaying server public key"
    ssh $server "cat ~/.ssh/id_rsa.pub"

    #Though, he did give me a good idea
    echo "Displaying keys authorized on $server (you can paste them in your authorized_keys file)"
    ssh $server "cat ~/.ssh/authorized_keys"

    #echo "Appending keys authorized on $server to your local authorized_keys"
    #ssh $server "cat ~/.ssh/authorized_keys" >> ~/.ssh/authorized_keys
done
echo "SSH keys schronized successfully!"

#!/bin/bash

#Leif Messinger lsm0147

#credit.sh FILES
cred="Leif Messinger lsm0147"
for bruh; do
	if [[ $bruh =~ \.cpp|\.c|\.java|\.js ]]; then
		comment="//$cred"
	else

		#Basically everything else gets a pound sign comment

		#Pound signs are standard across linux. bash, sed, gawk, python etc

		#Speaking of which, I need to escape it because of that.
		comment="\#$cred"
	fi
	if [ -s $bruh ]; then

		#If the file has a shebang
		if egrep -q '^#!/' $bruh; then
			sed -i "/^\#!\//a$comment" $bruh
		else
			sed -i "1i$comment" $bruh
		fi
	else
		echo "$comment" > $bruh
	fi
done

#!/bin/sh

BAT_LOW=15
BAT_CRITICAL=5

if [ "$1" = "--help" ]
then
    printf "
    Usage:
    \tbattery_check.sh warning%% hibernate%%

    Description:
    \tA script for notifying the user via dunst and logging when
    \tthe battery is low and the system is going to hibernate.
    \tCan be supplied arguments for the battery low warning and
    \thibernation percentage thresholds as the first and second arguments.

    \t Default behavior is to warn at 15% and hibernate at 5%."
    exit
fi

if [[ -n "$1" && -n "$2" && $1 -gt $2 ]]
then
    BAT_LOW=$1
    BAT_CRITICAL=$2
fi

acpi -b | awk -F'[,:%]' '{print $2, $3}' | {

    read -r status capacity
    echo Low threshold: $BAT_LOW, Hibernate threshold: $BAT_CRITICAL
    echo Status: $status, Capacity: $capacity

    if [ "$status" = Discharging -a "$capacity" -le $BAT_CRITICAL ]; then
        echo Battery critical threshold.
        dunstify -u critical "Critical battery threshold, hibernating..."
        logger "Critical battery threshold, hibernating..."
        sleep .5
        systemctl hibernate
        exit
    fi

    if [ "$status" = Discharging -a "$capacity" -le $BAT_LOW ]; then
        echo Battery low threshold.
        dunstify -u critical 'Battery low! System will hibernate at 5%.'
        logger 'Battery low! System will hibernate at 5%.'
        sleep .5
        light -S 15
        exit
    fi
}