Skip to content

Instantly share code, notes, and snippets.

View bolutife-lawrence's full-sized avatar

Bolutife Lawrence bolutife-lawrence

View GitHub Profile
@bolutife-lawrence
bolutife-lawrence / httpRequestSaga.js
Last active August 24, 2018 02:07
Create a reusable redux-saga for HTTP requests.
import { call } from 'redux-saga/effects';
const requireParam = (msg) => {
throw new Error(msg);
};
function* dumbScenarioHandler() {
yield;
}
@bolutife-lawrence
bolutife-lawrence / routerException.js
Last active March 15, 2017 20:39
An HTTP-based `Router` in it's simplest form :)
'use strict';
/**
* A very basic `RouterException` class.
**/
export default class RouterException {
constructor (name, msg) {
this.name = name;
this.message = msg;

macOS 10.12 Sierra Setup

Custom recipe to get macOS 10.12 Sierra running from scratch, setup applications and developer environment. This is very similar (and currently mostly the same) as my 10.11 El Capitan setup recipe and 10.10 Yosemite setup recipe. I am currently tweaking this for 10.12 Sierra and expect to refine this gist over the next few weeks.

I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. I generally reinstall each computer from scratch every 6 months, and I do not perform upgrades between releases.

This keeps the system performing at top speeds, clean of trojans, spyware, and ensures that I maintain good organizational practices for my content and backups. I highly recommend this.

You are encouraged to fork this and modify it to your heart's content to match your o

@bolutife-lawrence
bolutife-lawrence / nginxproxy.md
Created September 23, 2016 15:30 — forked from soheilhy/nginxproxy.md
How to proxy web apps using nginx?

Virtual Hosts on nginx (CSC309)

When hosting our web applications, we often have one public IP address (i.e., an IP address visible to the outside world) using which we want to host multiple web apps. For example, one may wants to host three different web apps respectively for example1.com, example2.com, and example1.com/images on the same machine using a single IP address.

How can we do that? Well, the good news is Internet browsers

@bolutife-lawrence
bolutife-lawrence / README.md
Created September 22, 2016 01:06 — forked from jimothyGator/README.md
Nginx configuration for Mac OS X with Homebrew, using sites-enabled directory.
mkdir -p /usr/local/etc/nginx/sites-{enabled,available}
cd /usr/local/etc/nginx/sites-enabled
ln -s ../sites-available/default.conf
ln -s ../sites-available/default-ssl.conf

File locations:

  • nginx.conf to /usr/local/etc/nginx/
  • default.conf and default-ssl.conf to /usr/local/etc/nginx/sites-available
  • homebrew.mxcl.nginx.plist to /Library/LaunchDaemons/
@bolutife-lawrence
bolutife-lawrence / introrx.md
Created July 26, 2016 00:20 — forked from staltz/introrx.md
The introduction to Reactive Programming you've been missing
@bolutife-lawrence
bolutife-lawrence / README.md
Created January 31, 2016 09:25 — forked from zenorocha/README.md
A template for Github READMEs (Markdown) + Sublime Snippet

Project Name

TODO: Write a project description

Installation

TODO: Describe the installation process

Usage

@bolutife-lawrence
bolutife-lawrence / README.md
Created January 31, 2016 09:21 — forked from jxson/README.md
README.md template

Synopsis

At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)

Code Example

Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.

Motivation

@bolutife-lawrence
bolutife-lawrence / osx-10.10-setup.md
Created January 20, 2016 19:31 — forked from kevinelliott/osx-10.10-setup.md
Mac OS X 10.10 Yosemite Setup

Mac OS X 10.10 Yosemite

Custom recipe to get OS X 10.10 Yosemite running from scratch, setup applications and developer environment. I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. On average, I reinstall each computer from scratch every 6 months, and I do not perform upgrades between distros.

This keeps the system performing at top speeds, clean of trojans, spyware, and ensures that I maintain good organizational practices for my content and backups. I highly recommend this.

You are encouraged to fork this and modify it to your heart's content to match your own needs.

Install Software