Skip to content

Add .env to .gitignore and provide .env.example to prevent misconfiguration #5

@FMBManuel

Description

@FMBManuel

To reduce the risk of misconfiguration and accidental exposure of sensitive information, the .env file should be added to .gitignore. Additionally, the current .env file can be renamed to .env.example and contain placeholder values only.

This approach ensures that environment-specific configurations remain local and private, while still providing a clear template for new instances or deployments.

Benefit:

  • Prevents accidental publishing of credentials or critical configuration data.
  • Provides a consistent and secure guideline for configuring local or replicated environments.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions