todgru

1. in channel type /github settings,
2. select "mute" url preview
3. in channel type /github settings,
4. select "disable" pr preview

todgru

#launchd Usage

I have a bash script called foo.sh that takes one command line argument, bar. I want it to run every 60 seconds and load at startup.

• an XML plist is Apple Property List
• com.mydomain.foo.plist Name of launchd plist file should be a reverse fqdn, like (this may not be required, but convention)
• com.mydomain.foo.plist lives in $HOME/Library/LaunchAgents and is ran as that user.
• com.mydomain.foo.plist can also live /Library/LaunchDaemons or /Library/LaunchAgents, have requirements, ran as root
• Load plist with launchctl load com.mydomain.foo.plist
• Unload plist with lauchctl unload com.mydomain.foo.plist

todgru

Setup redis-cli on AWS EC2

SSH into your EC2 instance. Run the following:

$ sudo yum install gcc This may return an "already installed" message. That's OK.

$ wget http://download.redis.io/redis-stable.tar.gz && tar xvzf redis-stable.tar.gz && cd redis-stable && make

See: http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/GettingStarted.ConnectToCacheNode.Redis.html

todgru

Elasticsearch Setup Apple MacBook Pro M1

Apple MacBook Pro M1, 32 GB, Ventura 13.2

Documentation based on comments in this Github Elasticsearch issue.

Install Homebrew

todgru

ERR_REQUIRE_ASYNC_MODULE

Node 20.18.0 vs 20.19.0

Error [ERR_REQUIRE_ASYNC_MODULE]: require() cannot be used on an ESM graph with top-level await. 
Use import() instead. To see where the top-level await comes from, use --experimental-print-required-tla.

This error is due to a Node.js updating the name of the error with a special "backport" of the require(esm) feature.

todgru

#git rebase -i <sha>

List of commits from git log

F--E--D--C--B--A

Lets say you want to remove commit D from the commits.

git rebase -i E

todgru

Mac OS X python virtual environments setup for new or existing projects

install pyenv

# install pyenv
curl https://pyenv.run | bash

# set env vars to support pyenv
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.zshrc

todgru

#Git Interactive Rebase

Scenario: We have a topic branch we've been working on. We want to combine the last few commits into one single commit. Our intention is to merge this topic branch, with one clean commit, into our main dev branch.

Solution: Git Rebase Interactive

Checkout your topic branch and look at your commit history:

$ git checkout topic-branch

todgru

1. Convert our ".jks" file to ".p12" (PKCS12 key store format):
 
keytool -importkeystore -srckeystore oldkeystore.jks -destkeystore newkeystore.p12 -deststoretype PKCS12
 
1.1. List new keystore file contents:
 
keytool -deststoretype PKCS12 -keystore newkeystore.p12 -list
 
2. Extract pem (certificate) from ".p12" keysotre file:
 

todgru

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

Tip

Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs

Commit Message Formats

Default