Skip to content

Instantly share code, notes, and snippets.

View jkirira's full-sized avatar

James Kirira jkirira

  • Nairobi, Kenya
View GitHub Profile
@acarril
acarril / bootable-win-on-mac.md
Created November 18, 2022 17:49
Create a bootable Windows USB using macOS

For some reason, it is surprisingly hard to create a bootable Windows USB using macOS. These are my steps for doing so, which have worked for me in macOS Monterey (12.6.1) for Windows 10 and 11. After following these steps, you should have a bootable Windows USB drive.

1. Download a Windows disc image (i.e. ISO file)

You can download Windows 10 or Windows 11 directly from Microsoft.

2. Identify your USB drive

After plugging the drive to your machine, identify the name of the USB device using diskutil list, which should return an output like the one below. In my case, the correct disk name is disk2.

Introduction

This document presents possible causes and solutions for "RCP failed http 400 error" that occurs while pushing a project using heroku cli.

Disclaimer

I didn't encounter this error and didn't change the default buffer size, I just gathered useful resources and shared the output of the sample running react-todo on heroku. Please be careful in troubleshooting and backup your project.

Resource

Below I list the most relevant resources on the subject.

  1. Everything you need to know to resolve the Git Push RPC error:
@blakethepatton
blakethepatton / Description.md
Last active November 7, 2023 09:37
Getting Mailhog running on a dev server (nginx, letsencrypt, ssl, ubuntu)

Get it running as a service

wget https://github.com/mailhog/MailHog/releases/download/v1.0.0/MailHog_linux_amd64

mv MailHog_linux_amd64 mailhog

chmod +x mailhog

sudo vi /etc/systemd/system/mailhog.service

@zcaceres
zcaceres / Nested-Routers-Express.md
Last active September 6, 2024 16:45
Child Routers in Express

Nested Routers in Express.js

Express makes it easy to nest routes in your routers. But I always had trouble accessing the request object's .params when you had a long URI with multiple parameters and nested routes.

Let's say you're building routes for a website www.music.com. Music is organized into albums with multiple tracks. Users can click to see a track list. Then they can select a single track and see a sub-page about that specific track.

At our application level, we could first have a Router to handle any requests to our albums.

const express = require('express');