tokens VS netlify-cache-nextjs

Visit GitHub Personal Access Tokens

Go to GitHub Settings > Tokens

I combined this with the release workflow, setup requires a GitHub token. I created a fine-grained PAT for this.

(1) Create a personal access token: either a classic token or a fine-grained token. Name it something like "OpenAI Codex" and give it read + write access to the private repositories. (2) Add the token to Codex: go to your Codex environment settings, scroll to Secrets, and click Add +. Name the secret COMPOSER_AUTH. The value must be a JSON-encoded element with the token that you created earlier. The format is the same as used in the file ~/.composer/auth.json but you must put everything in a single line. For example:

GitHub API key for use with the requests

Go to GitHub → Settings → Developer Settings → Personal Access Tokens

Go to the Personal access tokens area in the Developer settings of your GitHub profile and click Generate new token.

my-lisp-load is a function I introduced in 2016-05-06-2. If you create a PAT at https://github.com/settings/tokens and save it to ~/.emacs.d/spec/github-expand-link-token, you can load it with (my-lisp-load "github-expand-link-token"). If you want to reference Issues/PRs/Discussions in private repositories, set the PAT scope to repo.

ask@cs-278579150805-default:~/meteor-pulumi-esc$ gh auth login ? Where do you use GitHub? GitHub.com ? What is your preferred protocol for Git operations on this host? HTTPS ? Authenticate Git with your GitHub credentials? Yes ? How would you like to authenticate GitHub CLI? Paste an authentication token Tip: you can generate a Personal Access Token here https://github.com/settings/tokens The minimum required scopes are 'repo', 'read:org', 'workflow'. ? Paste your authentication token: ********************************************************************************************* - gh config set -h github.com git_protocol https ✓ Configured git protocol ✓ Logged in as kafechew

Generate a GitHub Personal Access Token with repo scope.

In terms of deployment, you can deploy the site wherever you can host a Next.js Jamstack site. I deployed mine to Netlify and utilized the Netlify Next.js cache plugin to improve the build speed. Utilizing the cache was important in my case as I have a lot of DEV posts and the DEV API is rate limited to 3 rps for reads (1 rps for writes, but that doesn't impact our API). (Note: the code has a short delay built into the blog post rendering to prevent API limit errors during the build on sites with a lot of posts.)