Skip to content

Instantly share code, notes, and snippets.

View esevan's full-sized avatar
💭
I may be slow to respond.

Eunsoo Park (Evan) esevan

💭
I may be slow to respond.
View GitHub Profile
@esevan
esevan / prepull.yaml
Created February 28, 2019 10:46 — forked from itaysk/prepull.yaml
Kubernetes: Pre-pull images into node
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: prepull
annotations:
source: "https://gist.github.com/itaysk/7bc3e56d69c4d72a549286d98fd557dd"
spec:
selector:
matchLabels:
name: prepull

Install on ubuntu 18.04

Remove docker.io

sudo apt-get remove docker docker-engine docker.io

Install docker-ce

sudo apt-get install \
    apt-transport-https \
@esevan
esevan / ShortTips.md
Last active August 7, 2019 01:08
Useful tips

Short tips!

Pull from the PR

git pull origin pull/110/head:pr-110
@esevan
esevan / zen2.ipynb
Last active September 11, 2019 05:05
enterprise-gateway.gist
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@esevan
esevan / pr_etiquette.md
Created September 29, 2020 02:22 — forked from mikepea/pr_etiquette.md
Pull Request Etiquette

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.

@esevan
esevan / pr_etiquette.md
Created September 29, 2020 02:22 — forked from mikepea/pr_etiquette.md
Pull Request Etiquette

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.

@esevan
esevan / mbti_vibe.ipynb
Last active January 10, 2023 13:12
MBTI chemistry
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.