Andrew Weiland aweiland

Raspberry Pi Kiosk Setup

Install a fresh image of Raspbian and boot the Pi
- Follow the installation guide if needed
Go through the prompts to finish initial setup
Open a Termial window
- Type sudo apt-get install unclutter
- Type sudo raspi-config
  - Select Boot Options with Enter
    - Select Wait for Network at Boot with Enter
    - Select Yes with Enter

Methods of Signing Git Commits on MacOS

Last updated March 13, 2024

This Gist explains how to sign commits using gpg in a step-by-step fashion. Previously, krypt.co was heavily mentioned, but I've only recently learned they were acquired by Akamai and no longer update their previous free products. Those mentions have been removed.

Additionally, 1Password now supports signing Git commits with SSH keys and makes it pretty easy-plus you can easily configure Git Tower to use it for both signing and ssh.

For using a GUI-based GIT tool such as Tower or Github Desktop, follow the steps here for signing your commits with GPG.

The perfect Varnish configuration for WordPress, Joomla, Drupal & other (common) CMS based websites

Updated on December 15th, 2021

IMPORTANT: Read this before implementing one of the configuration files below (for either Varnish 3.x or 4.x+).

USE: Replace the contents of the main Varnish configuration file located in /etc/varnish/default.vcl (root server access required - obviously) with the contents of the configuration you'll use (depending on your Varnish version) from the 2 examples provided below.

IMPORTANT: The following setup assumes a 180 sec (3 minute) cache time for cacheable content that does not have the correct cache-control HTTP headers. You can safely increase this to 300 sec (or more) for less busier sites or drop it to 60 sec or even 30 sec for high traffic sites. It obviously depends on your use case.

This is the example that comes with the reagent template converted to use HTML5 based history. This means there are no # in the urls.

I just got this working, so there might be better approaches

The changes are

use goog.history.Html5history instead of goog.History
listen to clicks on the page, extract the path from them, and push them onto the history
listen to history changes, and have secretary do its thing in response

	{
	"Version": "2012-10-17",
	"Statement": [
	{
	"Sid": "AllowAllUsersToListAccounts",
	"Effect": "Allow",
	"Action": [
	"iam:ListAccountAliases",
	"iam:ListUsers",
	"iam:GetAccountPasswordPolicy",

	# Adapted from https://lobster1234.github.io/2017/12/03/run-tasks-with-aws-fargate-and-lambda/

	import boto3
	import os

	def lambda_handler(event,context):
	client = boto3.client('ecs')
	response = client.run_task(
	cluster=os.getenv('CLUSTER'),
	launchType=os.getenv('LAUNCH_TYPE', 'FARGATE'),

	AWSTemplateFormatVersion: '2010-09-09'
	Description: Cognito Stack
	Parameters:
	AuthName:
	Type: String
	Description: Unique Auth Name for Cognito Resources

	Resources:
	# Creates a role that allows Cognito to send SNS messages
	SNSRole:

	# import config.
	# You can change the default config with `make cnf="config_special.env" build`
	cnf ?= config.env
	include $(cnf)
	export $(shell sed 's/=.*//' $(cnf))

	# import deploy config
	# You can change the default deploy config with `make cnf="deploy_special.env" release`
	dpl ?= deploy.env
	include $(dpl)