Skip to content

Conversation

@xrissoula
Copy link
Contributor

Description:

This PR adds a new article titled “The Problem with .env Files & Why Polykey Is the Future” to the documentation.

The article covers:

  • Why .env files are a security risk (plaintext storage, accidental commits, lack of version control).
  • Common bad practices teams use to replace .env files (hardcoding, databases, third-party cloud services).
  • How Polykey provides a secure, decentralized alternative for secrets management.
  • A breakdown of how Polykey works and how it eliminates the need for .env files.

The article is located in: --> docs/how-to-guides/companies-and-teams/the-problem-with-env.md

Issues Fixed

  • Fixes #...

Tasks

  • 1. Write and format the .env article
  • 2. Ensure markdown syntax is correct
  • 3. Review and Revise

Final checklist

  • Domain specific tests
  • Full tests
  • Updated inline-comment documentation
  • Lint fixed
  • Squash and rebased
  • Sanity check the final build

@xrissoula xrissoula self-assigned this Mar 6, 2025
@xrissoula xrissoula requested a review from CMCDragonkai March 6, 2025 06:24
@CMCDragonkai
Copy link
Member

This is some crazy wild stuff!!

Let's just forget that this ever happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants