This gist shows how to use the just command runner for a docker based project. The trick is to give the ability to call the recipes inside or outside the container, making it compatible for example with pipelines, or Devcontainers.
image_name := env_var_or_default("IMAGE_NAME", "buildenv:componentTesting")
# https://stackoverflow.com/questions/23513045/how-to-check-if-a-process-is-running-inside-docker-container
Create file /etc/systemd/system/[email protected]. SystemD calling binaries using an absolute path. In my case is prefixed by /usr/local/bin, you should use paths specific for your environment.
[Unit]
Description=%i service with docker compose
PartOf=docker.service
After=docker.service
| client = paramiko.SSHClient() | |
| client._policy = paramiko.WarningPolicy() | |
| client.set_missing_host_key_policy(paramiko.AutoAddPolicy()) | |
| ssh_config = paramiko.SSHConfig() | |
| user_config_file = os.path.expanduser("~/.ssh/config") | |
| if os.path.exists(user_config_file): | |
| with open(user_config_file) as f: | |
| ssh_config.parse(f) |
| (def levdist | |
| (let [lev (atom nil) | |
| impl | |
| (fn [s t] | |
| (let [lev @lev] | |
| (cond | |
| (empty? s) (count t) | |
| (empty? t) (count s) | |
| :else (let [ns (rest s) | |
| nt (rest t)] |
| ; inspired from http://stackoverflow.com/questions/3906831/how-do-i-generate-memoized-recursive-functions-in-clojure | |
| (defmacro memoize-fn | |
| "Produces a memoized anonymous function that can recursively call itself." | |
| [fn-name & fn-args] | |
| `(with-local-vars | |
| [~fn-name (memoize | |
| (fn ~@fn-args))] | |
| (.bindRoot ~fn-name @~fn-name) | |
| @~fn-name)) |