Skip to content

Instantly share code, notes, and snippets.

View juddey's full-sized avatar

Justin Lane juddey

56 followers · 31 following
View GitHub Profile
@charlespeach
charlespeach / hack-mini.md
Last active May 26, 2017 18:06
Hack-mini part list

Parts list for the Hack-Mini

The following parts are what I used for mine. If you want to build your own, please message me and I can help with the hackintosh setup!

  • 1x ASRock Deskmini 110 (Case/Mobo/DC Powerbrick combo!)
  • 1x Intel Skylake Core i3 (You could swap this out for any Skylake processor, just be mindful the board that comes in the Deskmini has a intel H110 chipset and does not support overclocking)
  • 2x Kingston ValueRAM SO-DIMM DDR4 PC17000/2133MHz CL15 8GB (You could increase this to 2x 16GB as the system supports 32GB)
  • Lastly: What ever storage you want. There is a m.2 slot for a PCI-e x4 SSD (think intel 600p, samsung 950/960 PRO, cannot be sata) and also 2x SATA 3 headers for 2.5mm SATA SSD's. Pick your poison!

If you want wifi/bluetooth, I suggest buying this: [Broadcom WIFI Wireless AC BCM94352Z](https://www.aliexpress.com/item/NEW-Broadcom-Or

@Aupajo
Aupajo / a-better-git-branch.md
Last active July 16, 2017 06:55

A better git branch

I'll often use branches to try out experiments, ideas, and to separate different trains of thought. Not every branch gets merged – in fact, it's quite common for me to make several commits on a branch, look at the end result, and throw the branch away without ever merging it (branching is cheap and ideas are cheap, but bad code is expensive). As a result, I can end up with a lot of branches. This makes the output of git branch difficult to sort through:

$ git branch
* account-org-association
  acdx-blog-posts
  add-static-resource-support
  alter-component-naming
@jswny
jswny / Flexible Dockerized Phoenix Deployments.md
Last active September 5, 2025 05:27
A guide to building and running zero-dependency Phoenix (Elixir) deployments with Docker. Works with Phoenix 1.2 and 1.3.

Prelude

I. Preface and Motivation

This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.

For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai

@Glutnix
Glutnix / index.js
Created February 4, 2019 21:26
cloudfront lambda to redirect requests for folders to the index.html inside that folder
/*
redirect requests for folders to folders/index.html
*/
const resolveUrlEndingInSlashToIndexHtml = require('./resolve-url-ending-in-slash-to-index-html');
exports.handler = (event, context, callback) => {
// Extract the request from the CloudFront event that is sent to Lambda@Edge
const { request } = event.Records[0].cf;