# Install tgenv with Homebrew

Terragrunt version manager inspired by tfenv. Version 1.3.0 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:tgenv
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install tgenv
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:tgenv
- **Package manager:** Homebrew
- **Version:** 1.3.0
- **Source summary:** Terragrunt version manager inspired by tfenv
- **Homepage:** <https://github.com/tgenv/tgenv>
- **Repository:** <https://github.com/tgenv/tgenv>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- tgenv (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.3.0
## Project history and usage

TGEnv is a Terragrunt version manager inspired by tfenv. Its README describes installing, switching, and managing multiple Terragrunt versions from one shell environment.

### Project history

The current project documents itself as a fork of cunymatthieu/tgenv. Its installation docs describe a shell-based tool distributed as a Git repository, exposed through `~/.tgenv/bin`, with Homebrew support on macOS and Linux.

The documentation centers on reproducible per-project Terragrunt selection through `.terragrunt-version`, mirroring the version-file workflow familiar from tfenv and other language/runtime managers.

### Adoption history

The README points to dedicated documentation for installation, usage, the `.terragrunt-version` file, environment variables, architecture, and contribution. The input metadata records Homebrew packaging.

### How it is used

The normal workflow is to install TGEnv, then run commands such as `tgenv install latest` and `tgenv use latest`. The docs say `.terragrunt-version` can pin a project to a literal version, `latest`, or a regex-based latest constraint.

When a `.terragrunt-version` file is present, TGEnv resolves it by walking up from the current directory, then falling back to the user's home directory and the global `~/.tgenv/version` file. The docs recommend committing `.terragrunt-version` so new contributors install the correct Terragrunt version automatically.

### Why package nerds care

tgenv is part of the version-manager family around infrastructure CLIs. For package-manager users, it keeps the Homebrew-installed manager stable while project repositories declare the Terragrunt version they need.

### Timeline

- 2024-01-05: The GitHub releases page lists tgenv v1.1.0.
- 2025-11-18: The GitHub releases page lists tgenv v1.3.0.
- 2026: The input metadata records tgenv as a Homebrew package.

### Related projects

- TGEnv is explicitly inspired by tfenv and manages releases of Terragrunt.

### Sources

- <https://github.com/tgenv/tgenv README>
- <https://github.com/tgenv/tgenv/blob/main/docs/installation.md>
- <https://github.com/tgenv/tgenv/blob/main/docs/terragrunt-version-file.md>
- <https://github.com/tgenv/tgenv/releases>
- source_facts.package-manager


## Security Notes

infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- infrastructure mutation or orchestration signal


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: .terragrunt-version

## Combined YAML source

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


## Sources

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