You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: client/README.md
+70Lines changed: 70 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,3 +57,73 @@ Angular CLI does not come with an end-to-end testing framework by default. You c
57
57
## Additional Resources
58
58
59
59
For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.
60
+
61
+
## Environment Configuration
62
+
63
+
The application supports multiple environments:
64
+
65
+
-**Development**: Uses `environment.ts` (default for local development)
66
+
-**Staging**: Uses `environment.staging.ts` (for the staging environment)
67
+
-**Production**: Uses `environment.prod.ts` (for the production environment)
68
+
69
+
## Building with Docker
70
+
71
+
The Dockerfile supports building the application for different environments using the `BUILD_ENV` build argument.
72
+
73
+
### Building for Production (default)
74
+
75
+
```bash
76
+
docker build -t client .
77
+
```
78
+
79
+
This will use the production environment configuration by default.
This will use the development environment configuration.
96
+
97
+
## Environment Configuration Files
98
+
99
+
The environment configuration files are located in `src/environments/`:
100
+
101
+
-`environment.ts`: Development environment
102
+
-`environment.staging.ts`: Staging environment
103
+
-`environment.prod.ts`: Production environment
104
+
105
+
Each file contains environment-specific settings like API URLs and feature flags.
106
+
107
+
## CI/CD Integration
108
+
109
+
The project's CI/CD pipeline automatically sets the appropriate `BUILD_ENV` value based on the Git branch:
110
+
111
+
-**main branch**: Uses `BUILD_ENV=production` for production deployments
112
+
-**dev branch**: Uses `BUILD_ENV=staging` for staging deployments
113
+
-**other branches**: Uses `BUILD_ENV=development` as a fallback
114
+
115
+
This is implemented in the GitHub Actions workflow (`.github/workflows/ci.yml`), which automatically builds and deploys the application with the correct environment configuration.
116
+
117
+
### Manual CI/CD Example
118
+
119
+
For manual CI/CD integration, you can use the `BUILD_ENV` build argument to specify the target environment:
0 commit comments