Generate strong ed25519 key
ssh-keygen -t ed25519 -b 4096
References for the above command
set hlsearch | |
set scrolloff=3 | |
set ignorecase smartcase | |
set showmode | |
set history=1000 | |
"" easy system clipboard copy/paste | |
"noremap <space>y "*y | |
"noremap <space>Y "*Y | |
"noremap <space>p "*p |
Sometimes you need to keep two upstreams in sync with eachother. For example, you might need to both push to your testing environment and your GitHub repo at the same time. In order to do this simultaneously in one git command, here's a little trick to add multiple push URLs to a single remote.
Once you have a remote set up for one of your upstreams, run these commands with:
git remote set-url --add --push [remote] [original repo URL]
git remote set-url --add --push [remote] [second repo URL]
Once set up, git remote -v
should show two (push) URLs and one (fetch) URL. Something like this:
Fri Jun 29 14:35:32 UTC 2018 |
I hereby claim:
To claim this, I am signing this object:
8.2.3. HTTP log format | |
---------------------- | |
The HTTP format is the most complete and the best suited for HTTP proxies. It | |
is enabled by when "option httplog" is specified in the frontend. It provides | |
the same level of information as the TCP format with additional features which | |
are specific to the HTTP protocol. Just like the TCP format, the log is usually | |
emitted at the end of the session, unless "option logasap" is specified, which | |
generally only makes sense for download sites. A session which matches the | |
"monitor" rules will never logged. It is also possible not to log sessions for |
job "redis" { | |
region = "global" | |
datacenters = ["test"] | |
type = "service" | |
constraint { | |
attribute = "${node.class}" | |
value = "default" | |
} |