Per-Dir API keys
How to easily setup per directory API keys to, for example, scope different AI subscriptions in different folders. This will use the CLI direnv to accomplish that.
How to easily setup per directory API keys to, for example, scope different AI subscriptions in different folders. This will use the CLI direnv to accomplish that.
Clone a repo with worktrees setup from the start:
mkdir <repo-name>
cd <repo-name>
git clone --bare --filter=blob:none <git-url>
cd <repo-name>.git
Some options to help your sanity:
# always prune on fetch
git config fetch.prune true
# allow `git fetch origin <branch-name>` to work as expected (create a remote ref)
git config remote.origin.fetch '+refs/heads/*:refs/remotes/origin/*'
To create a new branch:
git worktree add ../<branch-name>
cd ../<branch-name>
To copy a remote branch (note that this will only work with the above fetch config set):
git fetch origin <branch-name>
git worktree add ../<branch-name>
cd ../<branch-name>
To create a new branch based on a remote branch:
git worktree add ../<branch-name> -b <branch-name> --no-track origin/dev
cd ../<branch-name>
A step-by-step guide on how to setup a fresh Windows 11 installation for web development. These steps should also work on Windows 10 without much variation.
This is intended to be a very basic high level overview of GraphQL, explained to a developer that already understands the basics of REST API design. This is not a deep dive into all GraphQL's features or a GraphQL pros/cons list. Also, while GraphQL is backend language agnostic, this guide will be mentioning JavaScript implementations (since that's what I work with).
This blog is built using Docusaurus in blog-only mode. Here's how I did it: