jhrr

name	explain-diff-html
description	Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.

Explain Diff

Please make me a rich, interactive explanation of the specified code change.

It should have these sections:

PostgreSQL is Enough

See the new site: https://postgresisenough.dev

What's this

Sample codes in this blog. https://dev.to/paprikamah/how-to-setup-aws-waf-v2-21f1

What is this gist?

Explanation of a fullstack deployment of wagtail in a dockerized environment with Nginx, Elasticsearch, Postgres and Memcached

Required Skills:

docker
docker-compose
get a local wagtail site running

If you enjoyed reading this, I'm intending to do more blogging like this over here: https://cdgd.tech

This is not a complaint about Webpack or v4 in any way. This is just a record of my process trying it out so I could provide feedback to the webpack team

Hmm... I don't see any docs for 4.0 on https://webpack.js.org. I guess I'll just wing it. All I need to do is npm i -D webpack@next, right?

+ webpack@4.0.0-beta.2

Transduce

What is transduce? What is it for? This document is intended to help people (such as myself) who would be looking through the ramda docs, find transduce and have no idea if it would be a good fit for my current problem.

Idiomatic React Testing Patterns

Testing React components seems simple at first. Then you need to test something that isn't a pure interaction and things seem to break down. These 4 patterns should help you write readable, flexible tests for the type of component you are testing.

Setup

I recommend doing all setup in the most functional way possible. If you can avoid it, don't set variables in a beforeEach. This will help ensure tests are isolated and make things a bit easier to reason about. I use a pattern that gives great defaults for each test example but allows every example to override props when needed:

	# any images you use later, add them here first to create aliases
	# I like keeping all my versions at the top
	FROM node:14.3-slim as node
	FROM php:7.2.1-fpm-slim as php
	FROM nginx:1.17 as nginx

	# The real base image to start from
	FROM ubuntu:focal-20210827 as base

	# install apt stuff

	-- original code: https://github.com/ericelliott/cuid

	-- Add the "plv8" extension
	create extension if not exists "plv8";

	-- Add the "pgcrypto" extension
	create extension if not exists "pgcrypto";
	\dx

	-- Connect a database

	After automatically updating Postgres to 10.0 via Homebrew, the pg_ctl start command didn't work.
	The error was "The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.0."

	Database files have to be updated before starting the server, here are the steps that had to be followed:

	# need to have both 9.6.x and latest 10.0 installed, and keep 10.0 as default
	brew unlink postgresql
	brew install postgresql@9.6
	brew unlink postgresql@9.6
	brew link postgresql