All of the following information is based on go version go1.8.3 darwin/amd64
.
(Bold = supported by go
out of the box, ie. without the help of a C compiler, etc.)
android
darwin
#!/usr/bin/env bash | |
sudo apt update | |
sudo apt install \ | |
zsh \ | |
vim vim-gtk vim-nox \ | |
tmux \ | |
meld \ | |
smbclient \ # get secrets | |
stow \ # to unload dotfiles |
:: Credits from Go-Swagger itself: https://goswagger.io/install.html#for-windows-users | |
:: Same approach can be used for other Windows Host + Linux Containers, | |
:: which can completely replace some development setup command line tools. | |
:: | |
:: `--rm` - eliminates the need for a lot of dangling containers each time the command script is run. | |
:: | |
:: The `-v %CD%:<container path>` then `-w <that same container path>` makes the current directory | |
:: in the host universally accessible to the container. | |
:: | |
:: `%*` - this accepts any param after the docker image |
user nginx; | |
worker_processes 1; | |
error_log /var/log/nginx/error.log warn; | |
pid /var/run/nginx.pid; | |
events { | |
worker_connections 1024; | |
} |
Quarkus native-build needs:
gu install native-image
I hereby claim:
To claim this, I am signing this object:
$ GOOS=windows GOARCH=amd64 go build -ldflags="-s -w" cmd/app-name | |
$ upx --brute app-name.exe | |
from 5.7MB to 1.7MB! |
yum -y install git-core zlib zlib-devel gcc-c++ patch readline readline-devel libyaml-devel libffi-devel openssl-devel make bzip2 autoconf automake libtool bison curl sqlite-devel | |
cd ~ | |
git clone https://github.com/rbenv/rbenv.git ~/.rbenv | |
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bash_profile | |
echo 'eval "$(rbenv init -)"' >> ~/.bash_profile | |
source ~/.bash_profile | |
git clone https://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-build | |
echo 'export PATH="$HOME/.rbenv/plugins/ruby-build/bin:$PATH"' >> ~/.bash_profile | |
source ~/.bash_profile |
These rules are adopted from the AngularJS commit conventions.
We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the AngularJS change log.
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject: