Description:
To ensure that the frontend configuration is flexible and can be adjusted per environment without code changes, environment variables will be implemented. This approach allows the frontend application to dynamically adapt to different deployment settings, such as development, staging, or production. The .env file is crucial for storing non-sensitive configuration data which can change between environments, like API URLs.
Tasks:
[x] Define necessary environment variables: Create a .env file at the root of the frontend project. List all the configurable environment variables like REACT_APP_API_BASE_URL, which will be used across the application to make API requests.
[x] Securely integrate .env variables: Use the defined environment variables in the application's codebase, especially where API URLs or other configurable settings are required.
[x] Document environment variables usage: Update the project's README file to include instructions on how to set up the .env file, which variables are required, and potentially what the expected values should be for different environments.
[x] Test across environments: Verify that the application correctly picks up the values from the .env file in various environments, such as local development, CI/CD pipelines, and production servers.
gabrielvaca
commented
8 months ago
Description: To ensure that the frontend configuration is flexible and can be adjusted per environment without code changes, environment variables will be implemented. This approach allows the frontend application to dynamically adapt to different deployment settings, such as development, staging, or production. The .env file is crucial for storing non-sensitive configuration data which can change between environments, like API URLs.
Tasks: