Eric Ashman eashman

macOS Preferences for Sequoia

This document outlines how I configure macOS manually on a clean install of macOS Sequoia (15.4) on an Apple Silicon Mac. The focus is on privacy, usability, and performance, with added guidance for security-conscious users and developers. Scripts are intentionally avoided to ensure users understand and control each change.

Feel free to fork, tweak, or contribute.

Finder
iCloud
- iCloud Drive
iMessage

Easily Switch Accounts in AWS

When working with multiple AWS accounts, it can be a pain to keep signing out and signing back in. I work with a number of accounts, my own, customer accts, burner accts, etc. It was a pain to keep logging in and out of the AWS Console. Thankfully the AWS Console has a "Role Switcher" that lets you quickly switch between accounts built-in. It does this by assuming a role from another account. Here's how to set that up...

Smart Heroku Review Apps managed by GitHub Actions

This gist aims to provide a simple solution for managing Heroku Review Apps with GitHub Actions due to the security incident that continues to disrupt Heroku's GitHub integration. Watch the demo to learn more.

.github
├── workflows
│   ├── heroku_review_app_create.yml

Git Flow (with rebasing)

See http://nvie.com/posts/a-successful-git-branching-model/

Features

Wiring up a Google Form to GitHub is not that difficult with a little bit of Apps Script automation. All you need is a Google account, a GitHub account, and a web browser...

Set up your GitHub Personal Access Token

Personal access tokens provide an easy way to interact with the GitHub API without having to mess with OAuth. If you don't already have a personal access token with repo or public_repo access, visit your GitHub settings page and generate a new token.

Be sure to copy your token some place safe and keep it secure. Once generated, you will not be able to view or copy the token again.

Set up the Form & Spreadsheet

Create a Google Form.

Make sure the domain you picked points at the IP of your Redash server.
Switch to the root user (sudo su).
Create a folder named nginx in /opt/redash.
Create in the nginx folder two additional folders: certs and certs-data.
Create the file /opt/redash/nginx/nginx.conf and place the following in it: (replace example.redashapp.com with your domain name)
```
upstream redash {
    server redash:5000;
}
```

Git Guide

This document is meant to serve as a repository of best practices for large, multi-environment source control management.

Table of Contents

Introduction
Rules of the Trunk
The Basic Process
Creating a topic branch


	stages:
	- build
	- deploy

	variables:
	BASE_REPOSITORY_URL: 936832894876.dkr.ecr.us-east-2.amazonaws.com/slackbot/feedback-bot

	.aws_setup:
	image: docker:latest

	version: 0.2

	phases:
	install:
	commands:
	- echo Entered the install phase...
	- pip install -r requirements.txt
	build:
	commands:
	- echo Entered the build phase...

-// License: MIT, feel free to use it!
-const Intercom = require('intercom-client');
-const appId = 'APP_ID'
-const apiKey = 'APP_KEY'
-const client = new Intercom.Client(appId, apiKey);
-const async = require('async-q')
-//REF: https://developers.intercom.com/reference#iterating-over-all-users
-//WARNING: you can only have one scroll working at once. you need to wait for that scroll to clear to try again