Add build-args from client to pipeline

Author: sfdamm

.github/workflows/ci.yml

@@ -286,6 +286,19 @@ jobs:
             type=ref,event=pr
             type=sha
 
+      - name: Set build arguments for client
+        id: build-args
+        run: |
+          if [[ "${{ matrix.service }}" == "client" ]]; then
+            if [[ "${{ github.ref }}" == "refs/heads/main" ]]; then
+              echo "build_env=production" >> $GITHUB_OUTPUT
+            elif [[ "${{ github.ref }}" == "refs/heads/dev" ]]; then
+              echo "build_env=staging" >> $GITHUB_OUTPUT
+            else
+              echo "build_env=development" >> $GITHUB_OUTPUT
+            fi
+          fi
+
       - name: Build and push Docker Image
         uses: docker/build-push-action@v5
         with:
@@ -295,6 +308,8 @@ jobs:
           push: true
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
+          build-args: |
+            ${{ matrix.service == 'client' && format('BUILD_ENV={0}', steps.build-args.outputs.build_env) || '' }}
           cache-from: type=gha
           cache-to: type=gha,mode=max
 

client/README.md

@@ -57,3 +57,73 @@ Angular CLI does not come with an end-to-end testing framework by default. You c
 ## Additional Resources
 
 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.
+
+## Environment Configuration
+
+The application supports multiple environments:
+
+- **Development**: Uses `environment.ts` (default for local development)
+- **Staging**: Uses `environment.staging.ts` (for the staging environment)
+- **Production**: Uses `environment.prod.ts` (for the production environment)
+
+## Building with Docker
+
+The Dockerfile supports building the application for different environments using the `BUILD_ENV` build argument.
+
+### Building for Production (default)
+
+```bash
+docker build -t client .
+```
+
+This will use the production environment configuration by default.
+
+### Building for Staging
+
+```bash
+docker build -t client --build-arg BUILD_ENV=staging .
+```
+
+This will use the staging environment configuration.
+
+### Building for Development
+
+```bash
+docker build -t client --build-arg BUILD_ENV=development .
+```
+
+This will use the development environment configuration.
+
+## Environment Configuration Files
+
+The environment configuration files are located in `src/environments/`:
+
+- `environment.ts`: Development environment
+- `environment.staging.ts`: Staging environment
+- `environment.prod.ts`: Production environment
+
+Each file contains environment-specific settings like API URLs and feature flags.
+
+## CI/CD Integration
+
+The project's CI/CD pipeline automatically sets the appropriate `BUILD_ENV` value based on the Git branch:
+
+- **main branch**: Uses `BUILD_ENV=production` for production deployments
+- **dev branch**: Uses `BUILD_ENV=staging` for staging deployments
+- **other branches**: Uses `BUILD_ENV=development` as a fallback
+
+This is implemented in the GitHub Actions workflow (`.github/workflows/ci.yml`), which automatically builds and deploys the application with the correct environment configuration.
+
+### Manual CI/CD Example
+
+For manual CI/CD integration, you can use the `BUILD_ENV` build argument to specify the target environment:
+
+```yaml
+# Example for staging deployment
+docker build -t client --build-arg BUILD_ENV=staging .
+
+# Example for production deployment
+docker build -t client --build-arg BUILD_ENV=production .
+```
+
+This ensures that the correct environment configuration is used for each deployment target.

client/src/environments/environment.prod.ts

@@ -4,4 +4,4 @@ export const environment = {
   apiUrl: 'https://aieventconcepter.student.k8s.aet.cit.tum.de/api',
   mockDelay: 0,
   enableLogging: false
-}; 
+};