# Installer epinio avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de epinio pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:epinio
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install epinio
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:epinio
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.14.1
- **Résumé source:** CLI for Epinio, the Application Development Engine for Kubernetes
- **Page d'accueil:** <https://epinio.io/>
- **Dépôt:** <https://github.com/epinio/epinio>
- **Dernière mise à jour:** 2026-07-30T15:23:02Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- epinio (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 1.14.1
## Historique du projet et usages

Epinio is a Kubernetes application-development platform and CLI that turns application source into a running URL in one step. Its documentation positions it as a PaaS-style abstraction over Kubernetes for developers who do not want to work directly with Kubernetes internals.

### Historique du projet

The GitHub repository was created in November 2020. The project was originally associated with SUSE and later lists Krumware and SUSE in the docs and copyright notices. Current documentation describes Epinio as a Krumware project in collaboration with SUSE.

Epinio evolved as a developer-facing layer over Kubernetes: the CLI pushes applications, Cloud Native Buildpacks and Paketo buildpacks can build them, and operators retain control of the cluster, ingress, service templates, and platform setup.

### Historique d'adoption

Epinio's adoption is concentrated in the cloud-native and Rancher/SUSE ecosystem rather than general-purpose Unix tooling. The official docs link Rancher-related projects, community Slack, and GitHub discussions, while the README documents release binaries and Homebrew installation for the CLI.

### Modes d'utilisation

Typical usage starts with a Kubernetes cluster plus ingress and certificate management, then installing Epinio through Helm and using the epinio CLI to create namespaces and push applications. The project targets teams that want a Heroku-like developer experience on top of Kubernetes.

### Pourquoi les passionnés de paquets s'y intéressent

Epinio matters to package nerds as a compact CLI entry point into a larger Kubernetes platform. Packaging the CLI through Homebrew makes the developer-facing part easy to install even though the running system depends on cluster-side components.

### Chronologie

- 2020: The GitHub repository is created.
- 2020-2024: Project copyright is listed under SUSE.
- 2025-2026: Project copyright is listed under Krumware.
- 2026: Official docs publish version 1.14.0.

### Related projects

- Rancher, Fleet, Elemental, and Rancher Desktop appear as related projects in the official docs navigation.
- Paketo and Cloud Native Buildpacks are used for application build workflows.

### Sources

- <https://docs.epinio.io/>
- <https://github.com/epinio/epinio>
- <https://raw.githubusercontent.com/epinio/epinio/main/README.md>
- <https://api.github.com/repos/epinio/epinio>


## Notes de sécurité

infrastructure mutation or orchestration signal.

- **Risque Geiger:** orange / moyen
- infrastructure mutation or orchestration signal


## Combined YAML source

View the package source record on GitHub. [combined/epinio.yml](https://github.com/mxcl/pkgdb/blob/main/combined/epinio.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph