ping ping ff02::1%br-lanarp | grep ma:ca:dd:re:ssssh -L 8080:localhost:80 -o GlobalKnownHostsFile=/dev/null -o UserKnownHostsFile=/dev/null -6 root@fe80::0000:0000:0000:0000%eth0
$ MACOS_VM_VERSION=12.4
$ MACOS_VM_CODENAME=$(softwareupdate --list-full-installers 2>&1 | grep "Version:\s$(echo "${MACOS_VM_VERSION}" | sed 's#\.#\\.#g')[0-9.]*," | awk -F' macOS ' '{print$2}' | awk -F, '{print$1}' | uniq)
$ MACOS_VM_NAME="ansible-core-ci-template-macos-${MACOS_VM_VERSION}-playground"
$ MACOS_INSTALLER_NAME="Install macOS ${MACOS_VM_CODENAME}"
$ MACOS_INSTALLER_VOLUME_NAME="${MACOS_VM_CODENAME}"-"${MACOS_VM_VERSION}"
$ MACOS_INSTALLER_VOLUME_PATH="/Volumes/${MACOS_INSTALLER_VOLUME_NAME}"
$ MACOS_DOWNLOADED_INSTALLER_APP_PATH="/Applications/${MACOS_INSTALLER_NAME}.app"
$ MACOS_CREATEINSTALLMEDIA_BIN_PATH="${MACOS_DOWNLOADED_INSTALLER_APP_PATH}/Contents/Resources/createinstallmedia"
$ MACOS_ORIGINAL_INSTALLER_VOLUME_PATH="/Volumes/${MACOS_INSTALLER_NAME}"
💭 Thoughts
I want to have:
🔎 Findings
This document lists links to web pages related to mentoring and similar activities.
The provided below cp_tls_builtin.py and cp_tls_pyopenssl.py modules are
almost bare minimum CherryPy apps set up to serve a static string over HTTPS.
I say "almost" because having an HTTP handler mounted isn't really necesary to
verify that TLS works but having it provides a nice visual cue when using
curl, for example.
This instruction assumes that you have a freshly made virtualenv where you
executed something like pip install 'CherryPy[ssl]' trustme. The ssl extra
is only needed to pull in pyOpenSSL and isn't needed for the built-in stdlib
TLS adapter. The trustme project is needed for demonstration purposes — it'll
