cullylarson

const stages = ['production', 'staging', 'development', 'test'] as const;

type Stage = typeof stages[number];

function getStage(stages: Stage[]) {
  if (!stages.length) return 'production';

  for (const stage of stages) {
    // if any of the provided stages is production, assume we are in production
    if (stage === 'production') {

cullylarson

/* eslint-disable @typescript-eslint/no-unused-vars */
/* eslint-disable no-console */

/* ************************************** */

export interface Branding<BrandT> {
  _type: BrandT;
}

export type Brand<T, BrandT> = T & Branding<BrandT>;

cullylarson

Wordpress as a Dependency

How to install Wordpress as a dependency in your project, without including the WP install in version control.

Rationale

In the spirit of The Twelve Factor App, we want to "explicitly declare and isolate dependencies". Wordpress doesn't really promote this idea out of the box, so we have jump through a few hoops to do it. This document describes a simple method to include Wordpress as a dependency in this way.

General Idea

cullylarson

// Most of this is copied from: https://github.com/wbyoung/babel-plugin-transform-postcss

const {spawnSync, spawn} = require('child_process')
const path = require('path')

const socketPath = path.join('/tmp', 'styled-jsx-plugin-postcss--' + process.pid + '.sock')

const nodeExecutable = process.argv[0]
const clientExcutable = path.join(__dirname, 'client.js')
const serverExcutable = path.join(__dirname, 'server.js')

cullylarson

+ app
  - App.js
  - Layout.js
+ components
  - FormText.js
  - FormEmail.js
  - Card.js
  - CancelButton.js
 - Pagination.js

cullylarson

Site Performance Checklist

Do these things

• Enable gzip
• HTTP/2

Tools

• Chrome Lighthouse Audit

cullylarson

1. Strict-Transport-Security. Ensures that all traffic, even the first request to a non-https version of the URL, will be encrypted.
2. Referrer-Policy. Allows you to tell the browser what to set as the referrer URL when going to an external site.

cullylarson

### ABOUND BACKUPS

DB_BK_CMD = /home/user/backups/site_name/do-db-backup.sh
FILE_BK_CMD = /home/user/backups/site_name/do-files-backup.sh

# backup / Every day @ 3 am
0 3 * * * $DB_BK_CMD do-daily database_name
0 3 * * * $FILE_BK_CMD do-daily /home/user/public_html

# rotate weekly / Every 7 days @ 3:30am

cullylarson

Pushing to a client's git repo

I'm a freelance programmer. Sometimes I work on projects where the client wants to occasionally see code updates in their own repo, but I don't want them to see my work schedule. If I push my dev repo, they'll see when I'm working, how many hours, etc. To solve that, I started maintaining a for-client branch that only shows weekly, squashed merges of master. Each commit is monolithic, with one commit message (it doesn't include all of the individual commit times, messages, etc. from the master branch).

cullylarson

#
# Many apps send email. In a dev environment, we generally don't want those emails
# to get out. However, we still want our app to think it's sending mail and we want
# to verify that emails are being sent, with the correct content and to the correct
# recipients.
#
# This setup solves that problem by delivering all out-bound emails to the local
# "vagrant" user's mailbox.  You can then read the emails using the "mutt" command.
#
# Most if this is copied from: