Discover gists

title	slug	createdAt	language	preview
React Hook prompting the user to "Add to homescreen"	react-hook-prompting-the-user-to-add	2018-11-29T20:35:02Z	en	Simple React Hook for showing the user a custom "Add to homescreen" prompt.

React Hook for showing custom "Add to homescreen" prompt

macOS Internals

Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.

Starting Points

How to use this gist

You've got two main options:

This is a mini-tutorial of sorts for getting started with gdb on the Switch, with the target audience being people who want to mod and/or reverse games, with no prerequisite knowledge of gdb. The goal will be to walk you through some of the basic workflows needed to use a debugger on the Switch, while being brief enough for skimming for when you forget things.

If some part is unclear, your OS doesn't have install instructions, or you feel part of your workflow should be added here, feel free to comment any additions.

(If you only need a quick reference Jump to the Appendix)

Installing GDB

First off you'll need a version of GDB compatible with aarch64. This can be obtained via either a distribution of

Prerequisite

sudo apt update
sudo apt install software-properties-common -y

Add custom APT repository

#Transform web.config on build

Unload the project
Edit .csproj
Append figure 1 to the end of the file just before </Project>; v12.0 my change depending on your version of Visual Studio
Save .csproj and reload
Open configuration manager
Add a new Configuration Name: Base. Copy settings from: Release
Copy the contents of your web.config
Right click Web.Config > Add Config Transformation

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

1. Preparing the server

Install git

sudo apt install git-all

Generate Server's SSH public key

ssh-keygen -t rsa -b 4096 -C "deploy"
cat ~/.ssh/id_rsa.pub

Using GitHub Pages with a custom domain: Namecheap Edition

As often happens, I found the official documentation and forum answers to be "close, but no cigar", and so had to experiment a little to get things working.

The main problem for me was a lack of concrete configuration examples. That's not entirely GitHub's fault: having migrated from Google Domains to Namecheap in the middle of this project, I was once again reminded of how many different ways there are to do things in the name service universe [1].

Although you'd think the simplest setup would be to merely configure for the subdomain case (https://www.example.com), in my experience using the apex domain (https://example.com) instead resulted in fewer complications.

Procedure

So here's my recipe for using a custom domain with GitHub pages where Namecheap is the DNS provider:

	class Logger {
	sucesso(message) {
	console.log(`SUCESSO: ${message}`)
	}

	error(message) {
	console.error(`ERROR: ${message}`)
	}
	}

	/* open up chrome dev tools (Menu > More tools > Developer tools)
	* go to network tab, refresh the page, wait for images to load (on some sites you may have to scroll down to the images for them to start loading)
	* right click/ctrl click on any entry in the network log, select Copy > Copy All as HAR
	* open up JS console and enter: var har = [paste]
	* (pasting could take a while if there's a lot of requests)
	* paste the following JS code into the console
	* copy the output, paste into a text file
	* open up a terminal in same directory as text file, then: wget -i [that file]
	*/