Ars

Ars is the repository for generating my developer environment. It is powered by Ansible for installation and configuration of the desktop environment & developer tools. The primary use-case is for terminal development in Linux, but there is support for macOS via homebrew. The docs can be found on github.

License

Copyright 2025 Phillip Bonhomme

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Installation

There are different starting points for installing pbonh/ars on your system, and they will depend on your OS. If you are on Linux, pick a bootstrap_* script that closely matches the system. There is also a portable version of ansible available(scripts/bootstrap_ansible).

Bootstrap Examples

• Install Ansible(Portable)

wget -O - https://raw.githubusercontent.com/pbonh/ars/main/scripts/bootstrap_ansible.sh | bash

• Bootstrap Bluefin

wget -O - https://raw.githubusercontent.com/pbonh/ars/main/scripts/bootstrap_bluefin.sh | bash

• Bootstrap Ubuntu

wget -O - https://raw.githubusercontent.com/pbonh/ars/main/scripts/bootstrap_ubuntu.sh | bash

• Bootstrap Fedora

wget -O - https://raw.githubusercontent.com/pbonh/ars/main/scripts/bootstrap_fedora.sh | bash

Git/SSH(Optional)

Optionally, git & ssh can be configured via a prompt:

• Configure Git/SSH

wget -O - https://raw.githubusercontent.com/pbonh/ars/main/scripts/bootstrap_gitssh.sh | bash

Workstation GUI

If GUI support is desired, the following desktop environments are available:

• KDE

Developer Tools

There are 4 installation options to choose from for the developer tools (homebrew is the default):

1. Homebrew (default)
2. Mise
3. Devbox
4. Non-Root

Homebrew is the default tool manager for the developer toolset. Mise provides a curated toolchain, and Devbox uses nix with support for custom shell environments. Non-Root is useful when you don’t have root permissions, but still need to install the developer tools. All 4 are compatible with Linux & macOS.

EITHER Checkout repository and create .envrc file (base example):

touch .envrc
ln -s .envrc .env
cat << EOF >> .envrc
DOTFILES_TASK_PRELUDE=python
OPENAI_API_KEY="MY_OPENAI_API_KEY"
ANTHROPIC_API_KEY="MY_ANTHROPIC_API_KEY"
EOF

Optional Git-Enabled .envrc values (for the dev role):

cat << EOF >> .envrc
DOTFILES_BOOTSTRAP_GIT_NAME="Your Name"
DOTFILES_BOOTSTRAP_GIT_EMAIL="your_name@address.com"
DOTFILES_BOOTSTRAP_GITHUB_USERNAME="username"
EOF

For SSH mode examples (YubiKey/FIDO2 defaults vs plain ssh-agent), see:

• Configuration > Dotfiles
• Configuration > Examples

Apply optional Git/SSH + Git tooling config:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "{dev_machine: true}"

OR Ansible Pull

# (Non-Root, Shell Tools Only)
ansible-pull -U https://github.com/pbonh/ars.git ars.yml --tags "env" -e "{tool_provider: \"nonroot\"}"

# (Install Non-Root, Shell Tools Only)
ansible-pull -U https://github.com/pbonh/ars.git ars.yml --tags "install,env" -e "{tool_provider: \"nonroot\"}"

Developer Tools

This repo supports installing terminal developer tools & packages via homebrew (default), mise, devbox, and cargo (Non-Root).

Base provider examples only require tool_provider. Git identity and GitHub username are optional and can be applied separately with the dev role (dev.yml) when desired.

The options are presented in the recommended order:

1. Homebrew (default)
2. Mise
3. Devbox
4. Non-Root

Mise

Mise is a package manager for the developer tools in this repo. The role installs the mise binary and applies the tool configuration for you.

To install the Mise-managed packages, ensure ansible is installed and create a file to apply your customizations. The variable tool_provider MUST be specified as mise.

Base Example Yaml Config(mise.yml):

---
tool_provider: "mise"

Now use ansible-pull to install the Mise packages:

ansible-pull -U https://github.com/pbonh/ars.git ars.yml --tags "install" -e "@mise.yml"

Optional Git-Enabled Example Yaml Config(mise-git.yml):

---
tool_provider: "mise"
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"

Apply optional Git/SSH + Git tooling config:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@mise-git.yml"

Devbox

Run the bootstrap script, which will install:

1. Nix(via Determinate Systems)
2. Devbox
3. Bootstrap .bashrc Config

wget -O - https://raw.githubusercontent.com/pbonh/ars/main/scripts/bootstrap_devbox.sh | bash

To install the Devbox packages, ensure ansible is installed and create a file to apply your customizations. The variable tool_provider MUST be specified as devbox.

Base Example Yaml Config(devbox.yml):

---
tool_provider: "devbox"

Now use ansible-pull to install the Devbox packages:

ansible-pull -U https://github.com/pbonh/ars.git ars.yml --tags "install" -e "@devbox.yml"

Optional Git-Enabled Example Yaml Config(devbox-git.yml):

---
tool_provider: "devbox"
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"

Apply optional Git/SSH + Git tooling config:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@devbox-git.yml"

Homebrew

The following command will install homebrew for Linux or macOS systems:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

To install the Homebrew packages, ensure ansible is installed and create a file to apply your customizations. Homebrew is the default tool provider.

Base Example Yaml Config(brew.yml):

---
tool_provider: "homebrew"

Now use ansible-pull to install the Homebrew packages:

ansible-pull -U https://github.com/pbonh/ars.git ars.yml --tags "install" -e "@brew.yml"

Optional Git-Enabled Example Yaml Config(brew-git.yml):

---
tool_provider: "homebrew"
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"

Apply optional Git/SSH + Git tooling config:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@brew-git.yml"

Non-Root

To install the Non-Root packages, ensure ansible is installed and create a file to apply your customizations. The variable tool_provider MUST be specified as nonroot.

Base Example Yaml Config(nonroot.yml):

---
tool_provider: "nonroot"

Now use ansible-pull to install the Non-Root packages:

ansible-pull -U https://github.com/pbonh/ars.git ars.yml --tags "install" -e "@nonroot.yml"

Optional Git-Enabled Example Yaml Config(nonroot-git.yml):

---
tool_provider: "nonroot"
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"

Apply optional Git/SSH + Git tooling config:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@nonroot-git.yml"

Workstation GUI

The following Desktop Environments and Window Managers are supported:

• KDE Plasma - Full desktop environment with advanced workspace management
• Niri - Scrollable-tiling Wayland compositor

See individual guides for installation and configuration instructions.

KDE

This will install KDE tools necessary for managing a KDE config, and enables config backup & restore functionality. Make sure to specify your chosen tool_provider(devbox in this example).

ansible-pull -U https://github.com/pbonh/ars.git kde.yml --tags "install" --skip-tags "kwin" -e "{tool_provider: \"devbox\"}"

Niri

This will install and configure the Niri scrollable-tiling Wayland compositor.

Installation

ansible-pull -U https://github.com/pbonh/ars.git niri.yml

Just Task

You can also use the just runner:

just workstation-niri

Apps

Application install support includes the ProtonMail Bridge and Flatpak

ProtonMail Bridge

Use this script to install the ProtonMail Bridge *.rpm(Fedora/Bluefin only):

wget -O - https://raw.githubusercontent.com/pbonh/ars/main/scripts/install_protonmail_bridge.sh | bash

Flatpak

This role will install Desktop applications via flathub.

ansible-pull -U https://github.com/pbonh/ars.git apps.yml

Node.js Packages

This role installs Node.js packages via npm/pnpm as configured in your vars file.

Prerequisites

Ensure you have a tool provider installed (homebrew, mise, devbox, or nonroot) that provides Node.js.

Installation

ansible-pull -U https://github.com/pbonh/ars.git node.yml --tags "install"

Just Task

just install-node-packages

Configuration

Add Node packages to your vars/local.yml:

---
npm_packages:
  - name: "typescript"
    global: true
  - name: "@angular/cli"
    global: true

Optional Tools

Ansible is also setup to install Ollama as a system package. This will require root access and does not use the same devbox/homebrew/nonroot scripting.

Ollama(w/ ROCM)

ansible-pull -U https://github.com/pbonh/ars.git --ask-become-pass ollama.yml -e "{rocm_support: true}"

Distrobox Developer Environments

I use distrobox to isolate my developer environments from the host system: Distrobox.

ansible-pull -U https://github.com/pbonh/ars.git distrobox.yml -e "{git_email: \"your_email@address.com\"}"

Configuration

This repo offers configuration of the developer environment in the both the desktop and terminal.

Base configuration examples in this section do not require GitHub username, Git identity, or SSH credentials. Optional Git-enabled examples are included where relevant for users that want managed Git/SSH settings.

GUI

This will configure KDE Workspaces and Activities as specified by the user. Defaults are available.

Example Yaml Config(user_kde.yml):

---
kwin_rules_web_left_23: 
  position: "48,4"
  size: "983,1432"
kwin_rules_web_right_23:
  position: "1035,4"
  size: "2376,1432"
kwin_activities:
  browse:
    name: "Browse"
    description: "Web Browse & Research"
    icon: "com.opera.Opera"
    uuid: "240d6a84-dda7-4e1f-9e0c-ab1a9585d939"
kwin_rules:
  opera:
    group: "3c93494e-08c5-4fba-a3b8-1dacfa6d1d36"
    Description: "Opera: Browser"
    wmclass: "Opera"
    activity: "{{ kwin_activities['browse']['uuid'] }}"
    position: "{{ kwin_rules_web_right_23['position'] }}"
    size: "{{ kwin_rules_web_right_23['size'] }}"
    activityrule: "3"
    positionrule: "3"
    sizerule: "3"
    wmclassmatch: "2"
    ignoregeometry: "true"
    ignoregeometryrule: "3"
  thunderbird:
    group: "6d7f8fa9-b0ef-4ed7-9832-2c223e2a78df"
    Description: "Thunderbird: Email"
    wmclass: "org.mozilla.Thunderbird"
    activity: "{{ kwin_activities['browse']['uuid'] }}"
    position: "{{ kwin_rules_web_left_23['position'] }}"
    size: "{{ kwin_rules_web_left_23['size'] }}"
    activityrule: "3"
    positionrule: "3"
    sizerule: "3"
    wmclassmatch: "2"
    ignoregeometry: "true"
    ignoregeometryrule: "3"

Run this command to apply the workspace & activity settings specified above:

ansible-pull -U https://github.com/pbonh/ars.git kde.yml --tags "kwin" --skip-tags "install" -e "@user_kde.yml"

Dotfiles

This will apply settings(dotfiles) for a large variety of programs. There are filters in place to selectivly apply them. Users are strongly encouraged to set their own project, layouts, aliases, etc.

The bare minimum would be:

Base Example:

# devbox.yml
---
tool_provider: "devbox"
projects:
  ars:
    name: "pbonh/ars"
    url: "https://github.com/pbonh/ars.git"
    path: "{{ code_checkout_path_github }}/pbonh/ars"
zellij_kdl_layouts:
  dotfiles:
    name: dotfiles
    cwd: "{{ ansible_env.HOME }}"
    template_info: "{{ zellij_kdl_template_info_default }}"
    layout_info: |
      tab name="Ars" split_direction="vertical" cwd="{{ projects['ars']['path'] }}" focus=true {
          pane {
              command "{{ nvim_exe }}"
              args "README.md"
              start_suspended true
          }
      }

Optional Git-Enabled Example:

# devbox-git.yml
---
tool_provider: "devbox"
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"
projects:
  ars:
    name: "pbonh/ars"
    url: "{{ github_ssh_url }}:pbonh/ars.git"
    path: "{{ code_checkout_path_github }}/pbonh/ars"

Optional SSH Overlay (YubiKey/FIDO2 defaults):

# devbox-git-yubikey.yml
---
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"
projects:
  ars:
    url: "{{ github_ssh_url }}:pbonh/ars.git"

# Uses role defaults:
# bash_ssh_fido2_enabled: true
# zsh_ssh_fido2_enabled: true
# dev_ssh_manage_fido2_stanza: true

Optional SSH Overlay (plain ssh-agent config):

# devbox-git-plain-ssh.yml
---
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"
projects:
  ars:
    url: "{{ github_ssh_url }}:pbonh/ars.git"

bash_ssh_fido2_enabled: false
zsh_ssh_fido2_enabled: false
dev_ssh_manage_fido2_stanza: false

The above settings can be applied by running:

ansible-pull -U https://github.com/pbonh/ars.git ars.yml --skip-tags "install" -e "@devbox.yml"

Apply optional Git/SSH + Git tooling config:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@devbox-git.yml"
ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@devbox-git-yubikey.yml"
ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@devbox-git-plain-ssh.yml"

If checking out the ars repo directly, then create vars/local.yml, and add configuration there, no -e option necessary.

ansible-playbook playbook.yml --skip-tags "install"

Bitwarden CLI + wl-clipboard (Flatpak)

This is a quick way to copy passwords to the Wayland clipboard using the Flatpak Bitwarden CLI.

Set a Flatpak wrapper alias and unlock once per shell session:

alias bw='flatpak run --command=bw com.bitwarden.desktop'
export BW_SESSION="$(bw unlock --raw)"

Copy by exact item name:

bw get password "Item Name" | wl-copy

Search and pick an item ID (requires jq):

bw list items --search "query" | jq -r '.[] | "\(.id)\t\(.name)"'
bw get password <id> | wl-copy

Bashrc helpers

# ~/.bashrc
alias bw='flatpak run --command=bw com.bitwarden.desktop'

bw_unlock() {
  export BW_SESSION="$(bw unlock --raw)"
}

bw_copy_name() {
  bw get password "$1" | wl-copy
}

bw_search() {
  bw list items --search "$1" | jq -r '.[] | "\(.id)\t\(.name)"'
}

bw_copy_id() {
  bw get password "$1" | wl-copy
}

bw_pick_copy() {
  local selection
  selection="$(bw list items --search "$1" | jq -r '.[] | "\(.id)\t\(.name)"' | fzf)"
  [ -n "$selection" ] || return 1
  bw get password "${selection%%$'\t'*}" | wl-copy
}

Clipboard auto-clear (optional): check wl-copy --help for a --clear flag; if available, you can clear after a delay.

bw_copy_name_clear() {
  bw get password "$1" | wl-copy
  (sleep 20; wl-copy --clear) &
}

Available Tags

The dotfiles role supports selective application via tags. Use --tags to apply specific configurations or --skip-tags to exclude them.

Tool-Specific Tags

Editor Tags

Terminal Multiplexer Tags

File Manager Tags

AI Tool Tags

Other Tags

Common Usage Patterns

Apply only shell configurations:

ansible-playbook ars.yml --tags "env" --skip-tags "install"

Apply only AI tool configurations:

ansible-playbook ars.yml --tags "ai" --skip-tags "install"

Apply only editor configurations:

ansible-playbook ars.yml --tags "editor" --skip-tags "install"

Exclude specific tools:

ansible-playbook ars.yml --skip-tags "install,neovim-config"

Developer Configuration

The dev role configures Git identity, SSH settings, and developer-specific tooling.

Just Tasks

Configuration

Set these variables in vars/local.yml or via -e flag:

---
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"

Ansible-Pull

Apply developer configuration via ansible-pull:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "{dev_machine: true, git_name: 'Your Name', git_email: 'email@example.com', github_username: 'username'}"

Or with a vars file:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@dev-config.yml"

Examples

Base Example (macOS):

# macos.yml
---
tool_provider: "devbox"
homebrew_path: "{{ homebrew_path_macos }}"
ars_name: "pbonh/ars"
term_dev_name: "pbonh/term-dev.nix"
projects:
  ars:
    name: "{{ ars_name }}"
    url: "https://github.com/{{ ars_name }}.git"
    path: "{{ code_checkout_path_github }}/{{ ars_name }}"
  term_dev:
    name: "{{ term_dev_name }}"
    url: "https://github.com/{{ term_dev_name }}.git"
    path: "{{ code_checkout_path_github }}/{{ term_dev_name }}"
other_projects: "{{ projects | dict2items | 
             map(attribute='key', 
                 attribute2='value', 
                 transform=lambda k, v: [k, {'name': v.name, 'path': v.path}]) | 
             items2dict }}"
nushell_extra_aliases: |
  alias zdot = {{ zellij_exe }} --layout dotfiles
bash_extra_aliases: |
  alias zdot='{{ zellij_exe }} --layout dotfiles'
extra_zsh_aliases: |
  alias zdot='{{ zellij_exe }} --layout dotfiles'
zellij_kdl_layouts:
  dotfiles:
    name: dotfiles
    cwd: "{{ ansible_env.HOME }}"
    template_info: "{{ zellij_kdl_template_info_default }}"
    layout_info: |
      tab name="Ars" split_direction="vertical" cwd="{{ projects['ars']['path'] }}" focus=true {
          pane {
              command "{{ nvim_exe }}"
              args "README.md"
              start_suspended true
          }
      }
      tab name="Dotfiles" split_direction="vertical" cwd="{{ projects['term_dev']['path'] }}" {
          pane {
              command "env"
              args {% set bash_arg_list = nvim_exe_bone_bash_cmd %}
                   {% set bash_arg_string = bash_arg_list | map('string') | map('regex_replace', '^(.*)$', '"\\1"') | join(' ') %}
                   {{ bash_arg_string }}
              start_suspended true
          }
      }
      tab name="Devbox Project" split_direction="vertical" cwd="/path/to/devbox_project" {
          pane {
              command "env"
              args "NVIM_APPNAME=nvim-chatgpt-modular" "bash" "-c" "devbox run -- {{ nvim_exe }} README.md"
              start_suspended true
          }
      }
nushell_config_dir: "{{ macos_config_dir }}/nushell"
xdg_config_dir_navi: "{{ macos_config_dir }}/navi"

Optional Git-Enabled Overlay (macos-git.yml):

---
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"
projects:
  ars:
    url: "{{ github_ssh_url }}:{{ ars_name }}.git"
  term_dev:
    url: "{{ github_ssh_url }}:{{ term_dev_name }}.git"

Base Example (Devbox, AMD-ROCM):

---
tool_provider: "devbox"
rocm_support: true
ars_name: "pbonh/ars"
projects:
  ars:
    name: "{{ ars_name }}"
    url: "https://github.com/{{ ars_name }}.git"
    path: "{{ code_checkout_path_github }}/{{ ars_name }}"
other_projects: "{{ projects | dict2items | 
             map(attribute='key', 
                 attribute2='value', 
                 transform=lambda k, v: [k, {'name': v.name, 'path': v.path}]) | 
             items2dict }}"
# {{
#   {
#     key: {
#       'name': value.name,
#       'path': value.path
#     }
#     for key, value in projects.items()
#   }
# }}
codelldb_install_path: "{{ codelldb_install_devbox_path }}"
nushell_extra_aliases: |
  alias zdot = {{ zellij_exe }} --layout dotfiles
bash_extra_aliases: |
  alias zdot='{{ zellij_exe }} --layout dotfiles'
extra_zsh_aliases: |
  alias zdot='{{ zellij_exe }} --layout dotfiles'
zellij_kdl_layouts:
  dotfiles:
    name: dotfiles
    cwd: "{{ ansible_env.HOME }}"
    template_info: "{{ zellij_kdl_template_info_default }}"
    layout_info: |
      tab name="Neovim(Ollama): Lazy-Config" split_direction="vertical" cwd="{{ nvim_config_dir }}-lazy-modular" {
          pane {
              command "env"
              args {% set bash_arg_list = nvim_exe_ollama_bash_cmd %}
                   {% set bash_arg_string = bash_arg_list | map('string') | map('regex_replace', '^(.*)$', '"\\1"') | join(' ') %}
                   {{ bash_arg_string }}
              start_suspended true
          }
      }
      tab name="CPU/MEM" split_direction="vertical" {
          pane {
              command "btm"
              start_suspended true
          }
      }

Optional Git-Enabled Overlay (devbox-rocm-git.yml):

---
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"
projects:
  ars:
    url: "{{ github_ssh_url }}:{{ ars_name }}.git"

Apply optional Git/SSH + Git tooling config:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@macos-git.yml"
ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@devbox-rocm-git.yml"

Optional SSH Overlay (YubiKey/FIDO2 defaults):

# git-yubikey-defaults.yml
---
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"
projects:
  ars:
    url: "{{ github_ssh_url }}:pbonh/ars.git"

# Uses role defaults:
# bash_ssh_fido2_enabled: true
# zsh_ssh_fido2_enabled: true
# dev_ssh_manage_fido2_stanza: true

Optional SSH Overlay (plain ssh-agent config):

# git-plain-ssh.yml
---
dev_machine: true
git_name: "Your Name"
git_email: "your_name@address.com"
github_username: "username"
projects:
  ars:
    url: "{{ github_ssh_url }}:pbonh/ars.git"

bash_ssh_fido2_enabled: false
zsh_ssh_fido2_enabled: false
dev_ssh_manage_fido2_stanza: false

Apply SSH mode overlays with the dev role:

ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@git-yubikey-defaults.yml"
ansible-pull -U https://github.com/pbonh/ars.git dev.yml -e "@git-plain-ssh.yml"

License

                             Apache License
                       Version 2.0, January 2004
                    http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

   “License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

   “Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

   “Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

   “You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License.

   “Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

   “Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

   “Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

   “Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

   “Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”

   “Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

   (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

   (b) You must cause any modified files to carry prominent notices stating that You changed the files; and

   (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

   (d) If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

   You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

  To apply the Apache License to your work, attach the following
  boilerplate notice, with the fields enclosed by brackets "[]"
  replaced with your own identifying information. (Don't include
  the brackets!)  The text should be enclosed in the appropriate
  comment syntax for the file format. We also recommend that a
  file or class name and description of purpose be included on the
  same "printed page" as the copyright notice for easier
  identification within third-party archives.

Copyright 2025 Phillip Bonhomme

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.