0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-06 19:01:54 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 c55f508e05 feat(readme): draw mandatory and disabled service relations

The cosmos generator linked a consumer to its provider only through an
'<role>' in group_names reference or an explicit provides: name. A hard
dependency has neither -- pinning the provider on unconditionally is
exactly what removes the Jinja reference the generator was reading -- so
web-svc-asset's bond to web-svc-file vanished from the diagram the moment
it became binding. Match a service key against the provider's own primary
key from the registry, in both directions.

Services the role turns off drew a solid 1:1 edge, claiming a mandatory
relationship for something that carries nothing at deploy time. They now
render as a red 0..0 edge; edge merging gained a real precedence so a
provider consumed through two keys stays live when only one is off.

Named colour, not hex: a '#' opens an entity code in the mermaid lexer and
turns the whole diagram into a parse error on GitHub.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-17 18:02:31 +02:00

2.8 KiB

Raw Blame History

Python Development Utilities

Description

This Ansible role sets up a Python development environment on Arch Linux. It includes Python itself, the pip package manager, and builds on the general developer persona to support scripting, application development, data science, and more.

Learn more at the Python Official Site, the Arch Wiki - Python, and Wikipedia – Python.

Overview

This role provides the essential tooling for Python developers, enabling immediate use of python and pip from the command line. It supports both general-purpose scripting and advanced software engineering workflows.

Cosmos

The diagram places Python Development Utilities in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).

flowchart LR
    subgraph deps [Dependencies]
        dep_dev_core["dev-core 💻 ⚙️"]
    end
    subgraph role [dev-python 💻]
        svc_python["python"]
    end
    dep_dev_core -- "1:1" --> svc_python

Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.

Purpose

To simplify and standardize the provisioning of Python-ready environments for developers, students, data scientists, and automation engineers.

Features

Installs Python and Pip: Ensures the interpreter and package manager are available.
Prefers Python 3.11+: Installs Python 3.11+ where available and makes it the default via /usr/local/bin/python3 and /usr/local/bin/pip3.
Persona Integration: Extends dev-core with Python-specific tools.
Foundation for Further Stacks: Ideal starting point for Flask, Django, scientific computing, and automation.

Supported distro families in the installer script:

Arch Linux
Debian
Ubuntu
Fedora
CentOS / RHEL

Customization

Easily extend this role with:

Python virtualenv tools (python-virtualenv, pyenv)
Popular libraries (numpy, requests, flask)
Framework-specific roles (e.g., dev-python-django)

Credits

Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).

2.8 KiB Raw Blame History Unescape Escape