How to configure your Mac to use DNS over TLS in five easy steps:
-
Install Stubby with Homebrew (https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Daemon+-+Stubby):
brew install stubby -
Edit the configuration file:
| <!DOCTYPE html> | |
| <html lang='`en'> | |
| <head> | |
| <meta charset='utf-8'/> | |
| <title>Audio only stream example</title> | |
| <script src='https://cdn.dashjs.org/latest/dash.all.min.js'></script> | |
| <style> | |
| video { |
| #!/bin/bash | |
| message=$1 | |
| if [[ -n "$message" ]]; then | |
| curl -s -X POST https://api.telegram.org/bot[Your_API_Key]/sendMessage -d chat_id=[Your_Chat_ID] -d text="$message" | |
| else | |
| curl -s -X POST https://api.telegram.org/bot[Your_API_Key]/sendMessage -d chat_id=[Your_Chat_ID] -d text="The task is finished." | |
| fi |
| #!/usr/bin/env python | |
| import io | |
| import os | |
| import tarfile | |
| import requests | |
| import stash | |
| SITE_PACKAGES = os.path.expanduser("~/Documents/site-packages-3") |
| # Configuring DNS-over-TLS on macOS | |
| # Worked on macOS 10.13.4 | |
| brew -v update | |
| brew -v doctor | |
| # Next two commands are optional | |
| sudo chown -R $(whoami) $(brew --prefix)/* | |
| echo 'export PATH="/usr/local/sbin:$PATH"' >> ~/.bash_profile | |
| # Install DNS client | |
| brew install knot-resolver | |
| # Should be installed to something like: /usr/local/Cellar/knot-resolver/2.3.0/sbin/kresd |
How to configure your Mac to use DNS over TLS in five easy steps:
Install Stubby with Homebrew (https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Daemon+-+Stubby):
brew install stubby
Edit the configuration file:
| #!/bin/bash | |
| # This is a simple script that increments the integer in a the 'build-version' | |
| # file, and makes a new commit. The new commit will be tagged with the branch | |
| # and version | |
| # | |
| # You may specify a path. If no path is specified, the working directory will be | |
| # used. | |
| # | |
| # Eventually we might want to replace this with a proper CI pipline, but this |
| set -ex | |
| REGISTRY_INGRESS_IP=10.73.177.23 | |
| REGISTRY_INGRESS_REGISTRY_INGRESS_HOSTNAME=registry.$REGISTRY_INGRESS_IP.xip.io | |
| # if [ ! -e $REGISTRY_INGRESS_HOSTNAME.key ]; then | |
| # echo '{"CN":"'$REGISTRY_INGRESS_HOSTNAME'","hosts":[""],"key":{"algo":"rsa","size":2048}}' | cfssl gencert -config=ca-config.json -ca=ca.pem -ca-key=ca-key.pem -hostname="$REGISTRY_INGRESS_HOSTNAME" - | cfssljson -bare $REGISTRY_INGRESS_HOSTNAME | |
| # fi | |
| # juju ssh easyrsa/0 |
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.