Description: The Giphy API key is currently exposed in the codebase. To enhance security and prevent unauthorized access, we need to implement environment variables to store sensitive information like the API key. This should rely on a .env file for local development and secrets management in GitHub for production.
Expected Behavior: The application should access the Giphy API key from an environment variable instead of being hardcoded in the source code. This will help prevent the key from being exposed in the repository and ensure better security practices.
For deployment, set the Giphy API key as a secret in GitHub by navigating to your repository settings and adding it under "Secrets."
Ensure the deployment process reads from these secrets.
Ensure that the .env file is not committed to the repository.
Document the setup process in the project's README to guide other contributors on how to configure the environment variables locally.
Description: The Giphy API key is currently exposed in the codebase. To enhance security and prevent unauthorized access, we need to implement environment variables to store sensitive information like the API key. This should rely on a .env file for local development and secrets management in GitHub for production.
Expected Behavior: The application should access the Giphy API key from an environment variable instead of being hardcoded in the source code. This will help prevent the key from being exposed in the repository and ensure better security practices.
For deployment, set the Giphy API key as a secret in GitHub by navigating to your repository settings and adding it under "Secrets." Ensure the deployment process reads from these secrets.
Ensure that the .env file is not committed to the repository. Document the setup process in the project's README to guide other contributors on how to configure the environment variables locally.