laduke

function h(tag, as, xs) {
  var attrs = Object.entries(as).map(([k, v]) => ` ${k}="${v}"`);

  return `<${tag}${attrs}>${xs.join("")}</${tag}>`;
}

console.log(
  h("div", { id: "foo" }, [
    h("p", { class: "big" }, ["hi", h("p", {}, ["3"])]),
    h("p", {}, ["bye"])

laduke

Collect information helpful for troubleshooting zerotier-one

Run this on Mac or Linux

It will create a text file in the current directory. It won't modify anything.

Make sure you are root

   (set -x; \
 zerotier-cli info -j; \

laduke

Testing out a test thing

• https://github.com/hyperdivision/vhs-tape
• https://github.com/hyperdivision/hui
• https://github.com/davidkpiano/xstate/tree/master/packages/xstate-test
• https://github.com/davidkpiano/xstate

laduke

const myMachine = Machine({
  type: 'parallel',
  context: {},

  states: {
    hi: {
      initial: 'no',
      states: {
        yes: {},
        no: { on: { CLICK_ME: 'yes' } }

laduke

#compdef zerotier-cli
#autoload


_get_network_ids ()
{
    if [[ "$OSTYPE" == "darwin"* ]]; then
        COMPREPLY=($(compgen -W "$(ls -1 /Library/Application\ Support/ZeroTier/One/networks.d | cut -c 1-16)" -- ${cur}))
    else
        COMPREPLY=($(compgen -W "$(ls -1 /var/lib/zerotier-one/networks.d | cut -c 1-16)" -- ${cur}))

laduke

Typically, you use zerotier-cli to join and leave networks, but you can also write files to the filesystem to do this.

The networks.d subdirectory of the ZeroTier working directory keeps track of which networks are joined and their settings.

The ZeroTier working directory can be found...

• On Windows: \ProgramData\ZeroTier\One
• On Mac: /Library/Application Support/ZeroTier/One
• On Linux: /var/lib/zerotier-one

laduke

curl --silent --header "authorization: bearer ${TOKEN}" "https://my.zerotier.com/api/network/${NWID}/member" | jq  ".[] | [ .nodeId, .name, .config.ipAssignments[0] ]" | jq -rs ".[] | @csv"