Blaise Pabon blaisep
| [[language]] | |
| name = "python" | |
| scope = "source.python" | |
| injection-regex = "python" | |
| file-types = ["py","pyi","py3","pyw",".pythonstartup",".pythonrc"] | |
| shebangs = ["python"] | |
| roots = [".", "pyproject.toml", "basedpyrightconfig.json", "pyrightconfig.json"] | |
| comment-token = "#" | |
| language-servers = ["basedpyright", "ruff"] | |
| indent = { tab-width = 4, unit = " " } |
| {-# LANGUAGE OverloadedStrings #-} | |
| {- | |
| Copyright (C) 2012-2024 John MacFarlane <[email protected]> | |
| This program is free software; you can redistribute it and/or modify | |
| it under the terms of the GNU General Public License as published by | |
| the Free Software Foundation; either version 2 of the License, or | |
| (at your option) any later version. | |
| This program is distributed in the hope that it will be useful, |
| # Copied from https://github.com/kpfleming/ci-python-image/blob/main/workflow-support/make_ci_image.sh | |
| # the goal of the kata is to make an OCI image for CI. | |
| # The referene uses sh, but the suggestion is to refactor using an atuomation tool. | |
| # --- | |
| #!/usr/bin/env bash | |
| set -ex | |
| scriptdir=$(realpath "$(dirname "${BASH_SOURCE[0]}")") | |
| base_image=${1}; shift |
I hereby claim:
- I am blaisep on github.
- I am blaisepabon (https://keybase.io/blaisepabon) on keybase.
- I have a public key ASBqAeFHyU7b2rmjVAwPS_033rRGNvxiGZUOByDNyVOfwAo
To claim this, I am signing this object:
Background: The objective is to run python everywhere and my first step is to replace shell activity with pypyr. These notes relate to the process of automating a common task: running a containerized application in a local virtual host. It happens to the podman, but the structure is similar to Docker, Vagrant, kubectl, etc. The naive workkflow of "copy/paste commands into yaml blocks" resulted in the question of how to handle common failure scenarios. So I wonder if there is an approach or even some scaffolding for the "typical launch script"
The happy path is usually what is left over after everything else has failed. My intuition is that one should probe for the common failure conditions first.
Welcome to this week's Insiders Update! Insiders gain exclusive access to early previews, tutorials, updates, news, and events on my OSS work.
✅ Subscribe today and pay whatever you want 👉 through GitHub Sponsors
Insiders Update: 1st May 2020 - Netbooting the Raspberry Pi for Kubernetes and OpenFaaS enhancements
Pictured: netbooted Raspberry Pi cluster with Kubernetes (k3s)
The situation gets even worse where there are "too many cooks in the kitchen". In long-lived projects (many years, many versions) where there are lots of contributors, keeping docs current is a nightmare. As trust in the docs fails, so does confidence in the project ( cough >jenkins< cough ).
By way of example, allow me to present a few project we're all familiar with, because they are similar to Sanic and because we don't hear people complaining about the docs:
Facebook Workplace charges extra to log admin events. Facebook will publish Admin events for free via webhooks. You can "subscribe" they don't queue and they don't retransmit. To subscribe, you'll need to register a public URL with a recognized TLS certificate. Finally, you'll need a handler at that URL to participate in a rudimentary verification handshake before Facebook will register a webhook destination.
Considering these requirements, the solution has to:
- set up an externally accessible server
- get a domain name and a public SSL cert