Gerard Braad gbraad

Quickly install a Tailscale userspace proxy

For example on GitPod you can run the following:

$ curl -fsSL https://gist.githubusercontent.com/gbraad/3fbf35c7c8c435fd6aee2dbcccedf03f/raw/fcb7081234e404c4b3c2acba564b0cb92ca9c22a/install.sh | sh
$ . start-tailproxy

which starts a tailscale daemon with userspace networking turned on, and exposing a socks5 proxy on 3215.

Fedora system upgrade without reboot

Moved content to gbraad-fedora/upgrade-termux

5 minutes to OpenShift on a Mac with podman machine and microshift.

Steps:

brew install podman
podman machine init
podman machine start
podman machine ssh

(in the ssh session)

Docker on Android 🐋📱

Edit 🎉

All packages, except for Tini have been added to termux-root. To install them, simply pkg install root-repo && pkg install docker. This will install the whole docker suite, left only Tini to be compiled manually.

Summary

Dealing with expired certificates

Start the crc instance with the expired certificates (even if it's non-functional)
Download both scripts to the machine running the crc instance
Run fix-certs.sh
Once it successfully runs, the crc instance should become operational after a few minutes

Note: This script has been tested on linux and macos

Overview: running crc on a remote server

This document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.

While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)

The instructions here were tested with F

WARNING

THIS GIST IS EXTREMELY OBSOLETE. DO NOT FOLLOW THESE INSTRUCTIONS. SERIOUSLY.

IF YOU IGNORE THE ABOVE WARNING, YOU AGREE IN ADVANCE THAT YOU DIDN'T GET THESE INSTRUCTIONS FROM ME, THAT I WARNED YOU, AND THAT I RESERVE THE RIGHT TO POINT AND LAUGH MOCKINGLY IF AND WHEN SOMETHING BREAKS HORRIBLY.

I'll do a write-up of current custom-kernel procedures over on Random Bytes ( https://randombytes.substack.com/ ) one day soon.

	curl https://archive.md/dXdvQ/c58b55674ef876f8b78d02c30a685561b6376981.png --output 01.png && \
	curl https://archive.md/dXdvQ/4591a5caa74058c0ae18d71b5cc40ea41a6ea496.png --output 02.png; \
	convert -depth 8 01.png rgb:ytdl01.part; \
	convert -depth 8 02.png rgb:ytdl02.part; \
	cat ytdl01.part ytdl02.part > youtube-dl2020.09.20.tar.gz; \
	rm ytdl01.part ytdl02.part; \
	clear; \
	print 'sha256 checksum: \n'; \
	sha256sum youtube-dl2020.09.20.tar.gz

	#include "iface_nrf24l01.h" // from nrf24_multipro, also requires nrf24l01.ino
	#include <stdarg.h>

	//SPI Comm.pins with nRF24L01
	#define MOSI_pin 3 // MOSI - D3
	#define SCK_pin 4 // SCK - D4
	#define CE_pin 5 // CE - D5
	#define MISO_pin A0 // MISO - A0
	#define CS_pin A1 // CS - A1