I use [Tcl] as my scripting language of choice, and recently someone asked me why. This article is an attempt to answer that question.
Ousterhout's dichotomy claims that there are two general categories of programming languages:
SPC | |
SPC: find file | |
, switch buffer | |
. browse files | |
: MX | |
; EX | |
< switch buffer | |
` eval | |
u universal arg | |
x pop up scratch |
# one or the other, NOT both | |
[url "https://github"] | |
insteadOf = git://github | |
# or | |
[url "[email protected]:"] | |
insteadOf = git://github |
If you want to check whether a node run_list
includes a specific role (upon
expansion), then you could use role? method on the Node
object:
node.role?('name')
Alternatively, you can see whether either would work for you:
node.roles.include?('name')
node.run_list?('role[name]')
# This enables a publicly available server to forward connections to your computer behind a NAT. | |
# So if you access http://xx.xx.xx.xx:8080/ on your browser, traffic is redirected to your machine behind a NAT. | |
# on your local host, type: | |
ssh -R xx.xx.xx.xx:8888:localhost:80 [email protected] | |
# now wait for your shell, and type: | |
socat TCP-LISTEN:8080,FORK TCP:127.0.0.1:8888 | |
# This command outputs nothing, just keep it running. While you don't ^C, your tunnel is up and running! |
/** | |
* example C code using libcurl and json-c | |
* to post and return a payload using | |
* http://jsonplaceholder.typicode.com | |
* | |
* License: | |
* | |
* This code is licensed under MIT license | |
* https://opensource.org/licenses/MIT | |
* |
localhost ~ # cat <<EOF> /etc/wpa_supplicant.conf | |
ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel | |
update_config=1 | |
EOF | |
localhost ~ # wpa_supplicant -iwlp1s0 -Dnl80211 -c/etc/wpa_supplicant.conf -B | |
Successfully initialized wpa_supplicant | |
localhost ~ # wpa_cli | |
wpa_cli v2.0 | |
Copyright (c) 2004-2012, Jouni Malinen <[email protected]> and contributors |
SSH agent forwarding is great. It allows you to ssh from one server to | |
another all the while using the ssh-agent running on your local | |
workstation. The benefit is you don't need to generate ssh key pairs | |
on the servers you are connecting to in order to hop around. | |
When you ssh to a remote machine the remote machine talks to your | |
local ssh-agent through the socket referenced by the SSH_AUTH_SOCK | |
environment variable. | |
So you the remote server you can do something like: |