jojo ultralightspeed

(generated by chatgpt 4o and reviewed/edited by claude 3.5 sonnet, YMMV)

| Feature | Bash | Elvish | NuShell | Murex | Es Shell | Fish | Xonsh | PowerShell | Oil | Ion | |----------------------------------|-----------------------------------------------|-----------------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------|----------------------------------------------|-------------------------

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

How to setup AWS lambda function to talk to the internet and VPC

I'm going to walk you through the steps for setting up a AWS Lambda to talk to the internet and a VPC. Let's dive in.

So it might be really unintuitive at first but lambda functions have three states.

No VPC, where it can talk openly to the web, but can't talk to any of your AWS services.
VPC, the default setting where the lambda function can talk to your AWS services but can't talk to the web.
VPC with NAT, The best of both worlds, AWS services and web.

Intro

This note describes how to connect two networks/devices/VMs over public network using Wireguard with Layer 2 support (ARP, IPv6 link-local, etc).

This can also be achieved using SSH and its "tap" tunnel, however, it does not provide the same level of latency and bandwidth as full-blown VPN such as Wireguard.

In addition, this note describes how to tunnel Wireguard over TCP connection. This may be of use if you encounter firewall in-between so, for instance, you can use TCP port 443 only.

Objective

Adaptive Streaming has become the neccessity for streaming video and audio. Unfortantely, as of this post, there isn't a whole lot of tutorials that accumulate all of the steps to get this working. Hopefully this post achieves that. This post focuses on using Amazon Web Services (AWS) to transcode for HLS and DASH and be the Content Delivery Network (CDN) that delivers the stream to your web page. We'll be using Video.js for the HTML5 player as well as javascript support libaries to make Video.js work with HLS and DASH.

	# Borrowed from:
	# https://github.com/silven/go-example/blob/master/Makefile
	# https://vic.demuzere.be/articles/golang-makefile-crosscompile/

	BINARY = superdo
	VET_REPORT = vet.report
	TEST_REPORT = tests.xml
	GOARCH = amd64

	VERSION?=?

	a.myhost.com {
	tls off
	root /var/www/
	proxy / localhost:8091
	log log/access.a.log
	}

	b.myhost.com {
	tls off
	root /var/www/

	#! /usr/bin/env bash
	#
	# Run parallel commands and fail if any of them fails.
	#

	set -eu

	pids=()

	for x in 1 2 3; do

	addEventListener('fetch', event => {

	event.respondWith(purgeCache(event.request))

	})

	async function purgeCache(request) {

	const url = new URL(request.url)

	brew options ffmpeg

	brew install ffmpeg \
	--with-chromaprint \
	--with-fdk-aac \
	--with-fontconfig \
	--with-freetype \
	--with-frei0r \
	--with-game-music-emu \
	--with-libass \

jojo ultralightspeed

Auto-deploying built products to gh-pages with GitHub Actions

How to setup AWS lambda function to talk to the internet and VPC

Intro

Objective

So Here's what you need:

Set up three S3 buckets