Skip to content

Instantly share code, notes, and snippets.

View kkdai's full-sized avatar

Evan Lin kkdai

1.7k followers · 283 following
View GitHub Profile
@kkdai
kkdai / SHELL
Created June 1, 2016 01:17 — forked from jeffhung/SHELL
Vagrantfile for Declaring Tax (2016)
$ VBoxManage list usbhost
Host USB Devices:
...
UUID: 248ee848-3d9e-47cc-96d7-779e54946e39
VendorId: 0x0bda (0BDA)
ProductId: 0x0169 (0169)
Revision: 97.35 (9735)
Port: 1
@kkdai
kkdai / Dockerfile.slack
Created August 7, 2016 01:15 — forked from alexellis/Dockerfile.slack
Slack Dockerfile for 2.1.0
FROM debian:stretch
ENV LC_ALL en_US.UTF-8
ENV LANG en_US.UTF-8
RUN apt-get update && apt-get install -y \
apt-transport-https \
ca-certificates \
curl \
gconf2 \
@kkdai
kkdai / Go-MarshalJSON-Problem.go
Created August 10, 2016 06:10 — forked from twsiyuan/Go-MarshalJSON-Problem.go
詢問用範例
package math
type A struct {
FieldA1 int32
FieldA2 int32
}
func (this A) MarshalJSON() ([]byte, error) {
m := make(map[string]interface{}, 3)
m["FieldA1"] = this.FieldA1
@kkdai
kkdai / gen_le_cert.sh
Created October 16, 2016 12:32 — forked from pahud/gen_le_cert.sh
letsencrypt cert generator with docker
#!/bin/bash
#
# 1. create a EC2 instance with public IP
# 2. create a A RR in route53 pointing your.domain.com to the public IP
# 3. make sure HTTP/HTTPS ports(80 443) are public to all in security group of this EC2 instance
# 4. make sure docker daemon is running in this EC2 instance
# 5. run this script !
# 6. keys/cert will be generated under /root/letsencrypt/etc/live/
mkdir -p /root/letsencrypt/log /root/letsencrypt/lib /root/letsencrypt/etc
@kkdai
kkdai / main.go
Last active March 21, 2022 13:40 — forked from adityarama1210/main.go
Test Uploader GCP
package main
import (
"cloud.google.com/go/storage"
"context"
"log"
)
const (
projectID = "your-project-id" // FILL IN WITH YOURS
@kkdai
kkdai / git-commit-styleguide.md
Created January 2, 2025 07:29 — forked from rishavpandey43/git-commit-styleguide.md
This gist consist of the rules and best practice of good conventional git commit message

Git Commit Messages Style-Guides

  • Use the present tense ("Add feature" not "Added feature")
  • Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
  • Limit the first line to 72 characters or less
  • Reference issues and pull requests liberally after the first line
  • When only changing documentation, include [ci skip] in the commit title
  • Consider starting the commit message with an applicable emoji

Types