the following regex will validate all examples provided here: https://www.conventionalcommits.org/en/v1.0.0/
^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)
a grep/posix compatible variant
^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test){1}(\([[:alnum:]._-]+\))?(!)?: ([[:alnum:]])+([[:space:][:print:]]*)
| // +build windows | |
| package screen | |
| import ( | |
| "fmt" | |
| "image" | |
| "reflect" | |
| "syscall" | |
| "unsafe" |
# Key considerations for algorithm "RSA" ≥ 2048-bit
openssl genrsa -out server.key 2048
# Key considerations for algorithm "ECDSA" ≥ secp384r1
# List ECDSA the supported curves (openssl ecparam -list_curves)
This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.
While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.
| apiVersion: extensions/v1beta1 | |
| kind: Deployment | |
| metadata: | |
| creationTimestamp: null | |
| name: test | |
| spec: | |
| replicas: 1 | |
| template: | |
| metadata: | |
| creationTimestamp: null |
Reed Slaby, March 2018
Having grown tired of wasting a perfectly good monitor on my ethereum mining rig, I finally decided to replace the Ubuntu Desktop 16.04 installation with Ubuntu Server 16.04. Many of the gtutorials available at the time of this writing range from unecessarily complicated to flat-out wrong. This guide is intended to address many of those shortfalls.
To complete this guide, you should already have:
| package main | |
| import ( | |
| "database/sql" | |
| "fmt" | |
| "net" | |
| "os" | |
| "github.com/go-sql-driver/mysql" | |
| "golang.org/x/crypto/ssh" |
