Trebejo

Shell-dependent system utilities extracted from Apero.

Why Trebejo?

Apero was split into two packages:

Package	Contents
apero (≥ 3.0.0)	Pure stdlib wrappers — Env, Conf, Retry, Crypto, Cache, File trees/paths, OS type/hostname, Proc which/command_exists?
trebejo	Shell-dependent operations — Docker, Git, SSH, K8s, Compress, Network, OS info (arch, distro, kernel, cpu, memory), Proc listing/signalling, File watch

Module	Description
`Trebejo.Docker`	Docker container management
`Trebejo.Git`	Git repository operations
`Trebejo.SSH`	SSH connections and remote commands
`Trebejo.K8s`	Kubernetes resource management
`Trebejo.Compress`	Archive creation and extraction
`Trebejo.Network`	Network interface and connectivity
`Trebejo.OS`	OS metadata: arch, distro, kernel, CPU, memory, info, root, WSL/container detection
`Trebejo.Proc`	Process listing, signalling, lsof, fuser, log access
`Trebejo.File`	File system watching
`Trebejo.File.IO`	Disk usage reporting

Pure functions are delegated to Apero.* — this package depends on apero.

Add trebejo to your mix.exs:

def deps do
  [
    {:trebejo, "~> 1.0.0"}
  ]
end

Generated with ExDoc.