Skip to content

Remove sensitive .env file from history to prevent secrets exposure#1

Open
nirabo wants to merge 1 commit intomainfrom
fix/remove-env-file
Open

Remove sensitive .env file from history to prevent secrets exposure#1
nirabo wants to merge 1 commit intomainfrom
fix/remove-env-file

Conversation

@nirabo
Copy link
Owner

@nirabo nirabo commented Sep 28, 2024

The .env file contained sensitive information such as API keys, passwords, and other secret data. To prevent unauthorized access or accidental leakage of these secrets, we have removed this file from our Git history and replaced it with an empty example.env file. Developers should create their own .env file based on the example.env template for their respective environments.

Refactor: Remove sensitive config file (.env)

The .env file contained sensitive information such as API keys, passwords,
and other secret data. To prevent unauthorized access or accidental leakage
of these secrets, we have removed this file from our Git history and replaced
it with an empty example.env file. Developers should create their own .env
file based on the example.env template for their respective environments.

Refactor: Remove sensitive config file (.env)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant