pipx VS podman

Use pipx to install Cog and my aws-sso-config-builder tool in the same environment:

Given how useful pre-commit is across projects I generally recommend installing via pip install --user, making it part of a tooling virtual environment, or using pipx:

I would recommend going with PipX. You toss in a setup.py file, put your project on github, and then anyone on any OS can pipx install your project. It's a glorious thing. The only thing they need is 1) some supported version of Python installed, 2) pipx installed. They can even get updates by calling pipx upgrade.

See https://github.com/pypa/pipx/issues/278

Good overview. There are quite a few on there I was not aware of. That said, I am not sure the organizational schema makes a tone of sense. I would assume most users that come across this would be looking for a package manager for a specific platform and then weighing the options of binary/source/etc., instead of the other way around.

Also, pipx (https://github.com/pypa/pipx) would be a good addition to the list. I'd add it but I'm not sure where it would go. Maybe every section? It's cross platform and handles both binary and source based app distributions.

Pip is pretty simple and useful for me - you have your own environment for every script/program, requirements.txt is simple to understand too... It's kinda good solution for regular users... For more complex projects we have Poetry, PipX, that was inspired by NPM(x), I think...

What benefit would joining your cult bestow upon me that brew does not already?

My brew list is intentionally very short and my faffing about desire is limited.

Generally I use brew to pull in asdf (https://github.com/asdf-vm/asdf) to install programming languages/tooling, it works flawlessly.

I use Pipx (https://github.com/pypa/pipx) to install python thingies (such as yt-dlp) as a cli. Go and Rust handle binaries in their languages beautifully and without issues.

Example of why: https://github.com/containers/podman/issues/5102#issuecommen...

Podman

Even though we will focus on Docker for this article, I wanted to mention that there are more container creation and management tools such as Podman, Rkt, and so on.

By using containerization, the application will always have the same configuration that is used in the development environment and production environment. There is no more "It works on my machine". Some examples of containerization technologies are Docker and Podman.

Podman Documentation. Podman is a daemonless container engine for developing, managing, and running OCI Containers on your Linux System.

AFAIK podman either already supports pods in quadlet container files, or will in the near future. https://github.com/containers/podman/pull/20762

Podman as a devcontainers engine doesn't currently work if you use devcontainer features [1] or (and this sounds like you're issue) if you use WSL2.

I haven't submitted the WSL2 issue to the Podman team yet. If you get to it before I do, can you like it here?

https://github.com/containers/podman/issues/18691#issuecomme...

You can also use their Oracle Linux Docker images with the database preinstalled using either Podman or Docker. Just make absolutely sure you are downloading something you are licensed to use, because it seems really easy to accidentally infringe copyright via this method.

It's an open source project. https://github.com/containers/podman and https://podman.io - go there, get engaged, see what's going on and most important become part of the community and contribute!