[PR #1248] [CLOSED] Add KeyEnv to Security section #6084

New Issue

GiteaMirror · 2026-04-21T07:12:56-05:00

GiteaMirror commented

2026-04-21 07:12:56 -05:00

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/1248
Author: @ivannovazzi
Created: 2/26/2026
Status: ❌ Closed

Base: master ← Head: add-keyenv

📝 Commits (2)

1f98ee1 Add KeyEnv to Security section
cadb9b2 fix: correct URL from https://github.com/keyenv/keyenv to https://keyenv.dev

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Adding KeyEnv to the Security section.

KeyEnv is a CLI-first secrets manager that replaces .env files with encrypted, team-synced secrets. Instead of mounting plaintext .env files into containers, developers use keyenv run to inject secrets at runtime — secrets never touch the filesystem.

AES-256-GCM encryption at rest
Per-project environments (dev, staging, production)
Full audit trail for compliance
Works as a drop-in replacement for docker run --env-file

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/veggiemonk/awesome-docker/pull/1248 **Author:** [@ivannovazzi](https://github.com/ivannovazzi) **Created:** 2/26/2026 **Status:** ❌ Closed **Base:** `master` ← **Head:** `add-keyenv` --- ### 📝 Commits (2) - [`1f98ee1`](https://github.com/veggiemonk/awesome-docker/commit/1f98ee17b2c8506f8eed8e2ee60a40cef9b65c3c) Add KeyEnv to Security section - [`cadb9b2`](https://github.com/veggiemonk/awesome-docker/commit/cadb9b2ae4975b583cd58b5c2be132daa469d373) fix: correct URL from https://github.com/keyenv/keyenv to https://keyenv.dev ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description Adding [KeyEnv](https://keyenv.dev) to the Security section. KeyEnv is a CLI-first secrets manager that replaces `.env` files with encrypted, team-synced secrets. Instead of mounting plaintext `.env` files into containers, developers use `keyenv run` to inject secrets at runtime — secrets never touch the filesystem. - AES-256-GCM encryption at rest - Per-project environments (dev, staging, production) - Full audit trail for compliance - Works as a drop-in replacement for `docker run --env-file` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-21 07:12:56 -05:00

GiteaMirror closed this issue

2026-04-21 07:12:57 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-docker#6084