Someone was asking me about comparing the HoC and Render Props patterns (and their shortcomings) to hooks. I might leave this up as a public gist for others if it's helpful.
tldr;
Issues with HoC:
import React, { useState, useRef } from 'react' | |
import ReactDOM from 'react-dom' | |
/** | |
* 1. Start by creating some state to store an array of items | |
* where you have the array holding objects as shown below | |
* 2. Eventually, your array will start empty, but for now it might | |
* make sense to have that array already populated with an item | |
* or two so that way we can show them in the `<ul>`. So do that | |
* and then iterate over the `items` array in the JSX and make |
# Build a container from a local Dockerfile | |
# 1. -t is the tagname | |
# 2. The appname is any name we want to distinguish containers | |
# 3. . the path to Dockerfile | |
docker build -t <appname> . | |
# List Images | |
docker images | |
# Remove an Image |
⚠ This post is fairly old. I don't keep it up to date. Be sure to see comments where some people have posted updates
What this will cover
www.website.com
to website.com
index.html
)It seems as though some people like me are experiencing a weird thing when upgrading mac these days, the RSA keys still work for connecting to things like GitHub but my keychain doesn't want to remember the password and is annoyingly asking me for it with every git push
.
The solution I found that works is at http://stackoverflow.com/a/41576222
Basically, edit my ~/.ssh/config
file to be:
Host *
UseKeychain yes
sudo npm uninstall npm -g
brew uninstall node
Then
sudo rm -rf /usr/local/lib/dtrace/node.d /usr/local/lib/node_modules /usr/local/bin/npm /usr/local/bin/nodemon /usr/local/bin/node /usr/local/include/node ~/.npm* ~/.node* /usr/local/share/man/*/node* /usr/local/share/man/*/npm*
Bump Semver - https://docs.npmjs.com/cli/version
# One of these
npm version patch -m 'Git commit message'
npm version minor -m 'Git commit message'
npm version major -m 'Git commit message'
Push to GitHub
Instructions for setting up a basic Apache environment on OS X Yosemite Only. For Mavericks, view this guide
For this guide, square brackets are used to denote places where you need to plugin your own stuff. In none of these cases are you supposed to use actual square brackets.
Note that /private/etc
and /etc
go to the same place on Yosemite. This is good to know for later.
If you've already configured Apache correctly and you just want to know the part about setting up a new Virtual Host, then you can skip to that section. If not, then you'll need to configure Apache.
You will need the user_id
from the user. This is difficult to discover at Instagram but easy from this site http://jelled.com/instagram/lookup-user-id
I used http://jelled.com/instagram/access-token for the next few steps
You will also need an access token
which ends up being difficult to obtain. Log into the account and go to their Developer Page.
When setting up an Ubuntu server, you'll want to establish basic security including a firewall to only allow certain types of requests, and to allow only certain types of responses. This code will:
/etc/iptables.up.rules