Commit Graph

116 Commits

Author SHA1 Message Date
David
71541c79e7 fix pagination 2025-12-15 17:14:56 +01:00
David
368de79a1c merge 2025-12-15 16:51:36 +01:00
David
49b02face6 fix booking validate 2025-12-15 15:03:59 +01:00
David
faf1207300 feature fix branch 2025-12-12 10:31:49 +01:00
David
4279cd291d feature 2025-12-11 15:04:52 +01:00
David
54e7a42601 fix email send 2025-12-05 13:55:40 +01:00
David
3a43558d47 mail changer 2025-12-03 22:37:11 +01:00
David
55e44ab21c fix carte 2025-12-03 22:24:48 +01:00
David
7fc43444a9 fix search 2025-12-03 21:39:50 +01:00
David
a27b1d6cfa fix search booking 2025-11-30 23:27:22 +01:00
David
2da0f0210d fix organisation 2025-11-30 18:58:12 +01:00
David
c76f908d5c fix error get organisation 2025-11-30 18:39:08 +01:00
David
1a92228af5 contexte user reparer 2025-11-30 17:50:05 +01:00
David
cf029b1be4 fix users deleted and actived desactived 2025-11-30 17:36:34 +01:00
David
591213aaf7 layout access admin and manager 2025-11-30 13:48:04 +01:00
David
cca6eda9d3 send invitations 2025-11-30 13:39:32 +01:00
David
a34c850e67 fix register 2025-11-29 12:50:02 +01:00
David
b2f5d9968d fix: repair user management CRUD operations (create, update, delete)
Problems Fixed:

1. **User Creation (Invite)**
   -  Missing password field (required by API)
   -  Hardcoded organizationId 'default-org-id'
   -  Wrong role format (lowercase instead of ADMIN/USER/MANAGER)
   -  Now uses currentUser.organizationId from auth context
   -  Added password field with validation (min 8 chars)
   -  Fixed role enum to match backend (ADMIN, USER, MANAGER, VIEWER)

2. **Role Change (PATCH)**
   -  Used 'as any' masking type errors
   -  Lowercase role values
   -  Proper typing with uppercase roles
   -  Added success/error feedback
   -  Disabled state during mutation

3. **Toggle Active (PATCH)**
   -  Was working but added better feedback
   -  Added disabled state during mutation

4. **Delete User (DELETE)**
   -  Was working but added better feedback
   -  Added disabled state during mutation

5. **UI Improvements**
   - Added success messages with auto-dismiss (3s)
   - Added error messages with auto-dismiss (5s)
   - Added loading states on all action buttons
   - Fixed role badge colors to use uppercase keys
   - Better form validation before API call

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 23:35:10 +01:00
David
84c31f38a0 fix: load CSV files from MinIO instead of local filesystem for rate search
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 7m30s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 11m56s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 1s
CI/CD Pipeline / Deploy to Portainer (push) Successful in 11s
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Successful in 1s
Problem:
- CSV files uploaded to MinIO via admin panel
- But getAvailableCsvFiles() only listed local filesystem
- Result: rate search returned 0 results even though files exist in MinIO

Solution:
- Modified getAvailableCsvFiles() to check MinIO first
- Lists files from csv_rate_configs table with minioObjectKey
- Falls back to local filesystem if MinIO not configured
- Logs clearly which source is being used

This ensures rate search uses the uploaded CSV files from MinIO storage.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 23:18:03 +01:00
David
010c804b2e Revert "fix: convert Portainer stack to Docker Swarm mode with deploy labels"
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 3m3s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 11m46s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 1s
CI/CD Pipeline / Deploy to Portainer (push) Successful in 12s
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Successful in 1s
This reverts commit a2f80dd23f.
2025-11-20 22:55:05 +01:00
David
a2f80dd23f fix: convert Portainer stack to Docker Swarm mode with deploy labels
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Deploy to Portainer (push) Blocked by required conditions
CI/CD Pipeline / Discord Notification (Success) (push) Blocked by required conditions
CI/CD Pipeline / Discord Notification (Failure) (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 3m9s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
Changes:
- Moved all Traefik labels from root level to deploy.labels for Swarm compatibility
- Added deploy.restart_policy to backend, frontend, and MinIO services
- Removed restart: unless-stopped (incompatible with Swarm mode)
- Keeps depends_on for startup ordering

This fixes Gateway Timeout errors by ensuring Traefik can properly discover
and route to services when running in Docker Swarm mode.

Services updated:
- xpeditis-backend: Deploy labels + restart policy
- xpeditis-frontend: Deploy labels + restart policy
- xpeditis-minio: Deploy labels + restart policy

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 22:51:41 +01:00
David
dc62166272 fix: correct Argon2 password hash and organization UUIDs in migrations
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 7m52s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 11m40s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 1s
CI/CD Pipeline / Deploy to Portainer (push) Successful in 14s
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Successful in 1s
- Fixed test user migration to use real Argon2id hash for Password123!
- Replaced random uuidv4() with fixed UUIDs in organization seeds
- Updated auth.service.ts to use DEFAULT_ORG_ID constant
- Added ON CONFLICT DO UPDATE to migration for existing users
- Ensures consistent UUIDs across environments (dev/preprod/prod)

Fixes:
- Registration 500 error (foreign key constraint violation)
- Login 401 error (invalid password hash)
- Organization ID mismatch between migrations and application code

Test users (Password: Password123!):
- admin@xpeditis.com (ADMIN)
- manager@xpeditis.com (MANAGER)
- user@xpeditis.com (USER)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 20:05:22 +01:00
David
6e3191b50e fix ci/cd and docker
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 5m45s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 28m26s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 1s
CI/CD Pipeline / Deploy to Portainer (push) Successful in 14s
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Successful in 1s
2025-11-20 00:12:01 +01:00
David
2e5dcec05c fix
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 6m17s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 14m45s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 2s
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Successful in 2s
2025-11-19 18:27:42 +01:00
David
7dadd951bb fix portainer deploy
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 16m18s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 30m58s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 2s
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Successful in 1s
2025-11-19 15:17:53 +01:00
David
88f0cc99bb fix: enable Tailwind CSS compilation in Docker builds
CRITICAL FIX: Frontend was serving raw CSS with uncompiled @tailwind directives,
resulting in completely unstyled pages (plain text without any CSS).

Root cause:
- postcss.config.js and tailwind.config.js/ts were excluded in .dockerignore
- This prevented PostCSS/Tailwind from compiling CSS during Docker builds
- Local builds worked because config files were present

Changes:
1. apps/frontend/.dockerignore:
   - Commented out postcss.config.js exclusion
   - Commented out tailwind.config.js/ts exclusions
   - Added explanatory comments about why these files are needed

2. apps/backend/Dockerfile:
   - Copy src/ directory to production stage for CSV upload paths
   - Create csv-storage/rates directory with proper permissions
   - Fix EACCES errors when uploading CSV files

3. apps/backend/src/application/controllers/admin/csv-rates.controller.ts:
   - Add getCsvUploadPath() helper function
   - Support both local dev and Docker environments
   - Use absolute paths instead of relative paths

4. docker-compose.dev.yml:
   - Change backend port mapping to 4001:4000 (avoid local dev conflicts)
   - Change frontend port mapping to 3001:3000
   - Update CORS_ORIGIN and NEXT_PUBLIC_API_URL accordingly

Impact:
-  Fixes completely broken frontend CSS in Docker/production
-  Applies to CI/CD builds (uses apps/frontend/.dockerignore)
-  Applies to Portainer deployments (pulls from CI/CD images)
-  Fixes CSV upload permission errors in backend
-  Enables local Docker testing on Mac ARM64

Testing:
- Local Docker build now shows compiled Tailwind CSS (60KB+)
- Frontend displays properly styled pages at http://localhost:3001
- Backend CSV uploads work without permission errors

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-19 13:39:05 +01:00
David
c002c9a1d3 feat: add local Docker Compose stack for Mac testing
- Add docker-compose.local.yml with all services
- Use production images from Scaleway registry
- Configure local PostgreSQL, Redis, MinIO
- Add comprehensive testing guide in LOCAL_TESTING.md
- Includes debugging commands and troubleshooting

This allows testing production Docker images locally before
deploying to Portainer.
2025-11-18 20:59:39 +01:00
David
2505a36b13 fix: simplify Docker image tags to only use branch name
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 2m34s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 11m30s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 1s
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Successful in 1s
- Remove SHA-based tags (preprod-<sha>)
- Remove semver and PR tags
- Keep only branch-based tag (preprod)
- Keep latest tag for default branch
- Add Portainer debugging documentation

This ensures Portainer always pulls the stable branch tag
instead of commit-specific tags.
2025-11-18 00:00:06 +01:00
David
f9b1625e20 fix: replace require() with ES6 imports for fs and path
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 7m10s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 11m27s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 1s
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Successful in 2s
- Add fs and path imports at top of file
- Remove inline require() statements that violated ESLint rules
- Fixes 6 @typescript-eslint/no-var-requires errors
2025-11-17 23:26:22 +01:00
David
435d587501 fix: correct Docker registry paths in Portainer stack
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Discord Notification (Success) (push) Blocked by required conditions
CI/CD Pipeline / Discord Notification (Failure) (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 1m26s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
- Change backend image from DockerHub to Scaleway registry
- Change frontend image from :latest to :preprod tag
- Fix S3 bucket name to match CSV rates system
- Add comprehensive deployment fix documentation

This fixes container startup issues where Portainer was trying
to pull images from DockerHub instead of Scaleway Container Registry.
2025-11-17 23:21:00 +01:00
David
18098eb6c1 fix: correct import path in delete-orphaned-csv-config script 2025-11-17 23:12:11 +01:00
David
4f0d6f8f08 fix: add StorageModule import to CsvRateModule for S3 support
- Export S3StorageAdapter directly from StorageModule
- Import StorageModule and ConfigModule in CsvRateModule
- Fix dependency injection for S3StorageAdapter in CSV controllers
2025-11-17 20:52:27 +01:00
David
753cfae41d feat: add MinIO storage support for CSV rate files
- Upload CSV files to MinIO/S3 after validation
- Store MinIO object key in database metadata
- Support loading CSV from MinIO with fallback to local files
- Delete from both MinIO and local storage when removing files
- Add migration script to upload existing CSV files to MinIO
- Graceful degradation if MinIO is not configured
2025-11-17 20:12:21 +01:00
David
e030871b4e fix: handle missing CSV files gracefully in rate search with Promise.allSettled 2025-11-17 20:02:49 +01:00
David
f5eabf4861 fix: generate CSV filename from company name instead of using multer callback
Some checks failed
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 1m32s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 11m35s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Has been skipped
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Has been skipped
Fixed CSV file upload to properly generate filename based on company name. The previous implementation tried to read `req.body.companyName` in multer's filename callback, but the body is not yet parsed at that point, causing files to be named "unknown.csv".

## Solution
1. Use temporary filename during upload (timestamp + random)
2. After validation and parsing, rename file to proper company name format
3. Delete old file if it exists before renaming
4. Store final filename in database configuration

## Changes
- Multer filename callback now generates temporary filename
- Added file renaming logic after successful validation
- Updated database records to use final filename instead of temp name
- Added logging for file operations

## Impact
- New CSV uploads will have correct filenames (e.g., "ssc-consolidation.csv")
- No more "unknown.csv" files
- Existing "unknown.csv" needs to be manually deleted via dashboard

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 19:57:10 +01:00
David
aeb3d2a75d fix: use company name from form instead of CSV column
Some checks failed
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 1m33s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Discord Notification (Success) (push) Blocked by required conditions
CI/CD Pipeline / Discord Notification (Failure) (push) Blocked by required conditions
Fixed CSV rate upload to use the company name provided in the upload form instead of reading it from the CSV file's companyName column. This prevents "unknown" or incorrect company names from being used.

## Changes

**Domain Layer**
- Updated `CsvRateLoaderPort` interface to accept optional `companyNameOverride` parameter
- Modified `CsvRateSearchService.loadAllRates()` to pass company name from config when loading rates

**Infrastructure Layer**
- Updated `CsvRateLoaderAdapter.loadRatesFromCsv()` to accept `companyNameOverride` parameter
- Modified `mapToCsvRate()` to use override company name if provided, otherwise fallback to CSV column value
- Added logging to show which company name is being used (from override or CSV)

**Application Layer**
- Updated CSV upload controller to pass `dto.companyName` to the loader

## Impact
- When uploading a CSV file through the admin interface, the company name from the form is now correctly used
- Existing CSV files with "unknown" in the companyName column will now show the correct company name from the database configuration
- Backward compatible: if no override is provided, the CSV column value is still used

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 19:53:45 +01:00
David
27caca0734 feat: add CSV rates CRUD management to frontend dashboard
Some checks failed
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 1m38s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 25m29s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
Added comprehensive CSV rates management interface to the frontend dashboard with full CRUD operations.

## Backend Changes
- Added `GET /api/v1/admin/csv-rates/files` endpoint to list all uploaded CSV files with metadata
- Added `DELETE /api/v1/admin/csv-rates/files/:filename` endpoint to delete CSV files and their configurations
- Both endpoints provide frontend-compatible responses with file info (filename, size, rowCount, uploadedAt)
- File deletion includes both filesystem cleanup and database configuration removal

## Frontend Changes
- Added "CSV Rates" navigation item to dashboard sidebar (ADMIN only)
- Moved CSV rates page from `/app/admin/csv-rates` to `/app/dashboard/admin/csv-rates` for proper dashboard integration
- Updated CsvUpload component to include required `companyEmail` field
- Component now properly validates and sends all required fields (companyName, companyEmail, file)
- Enhanced form validation with email input type

## Features
-  Upload CSV rate files with company name and email
-  List all uploaded CSV files with metadata (filename, size, row count, upload date)
-  Delete CSV files with confirmation dialog
-  Real-time file validation (format, size limit 10MB)
-  Auto-refresh after successful operations
-  ADMIN role-based access control
-  Integrated into dashboard navigation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 19:11:37 +01:00
David
0ddd57c5b0 docs: add Discord notifications setup guide
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 2m41s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 11m38s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 1s
CI/CD Pipeline / Discord Notification (Failure) (push) Has been skipped
CI/CD Pipeline / Discord Notification (Success) (push) Successful in 2s
Complete guide for configuring Discord webhooks to receive CI/CD notifications.

Includes:
- Step-by-step Discord webhook creation
- Gitea secret configuration
- Notification format examples
- Customization options
- Troubleshooting section
- Security best practices

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 14:42:39 +01:00
David
4125c9db18 feat: add Discord notifications for CI/CD pipeline status
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Discord Notification (Success) (push) Blocked by required conditions
CI/CD Pipeline / Discord Notification (Failure) (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Has been cancelled
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
Added two notification jobs that send Discord webhooks:
- notify-success: Sends a green embed when pipeline succeeds
- notify-failure: Sends a red embed when pipeline fails

Notifications include:
- Repository and branch information
- Commit SHA with clickable link
- Docker image names (backend & frontend)
- Link to workflow run for debugging

Requires DISCORD_WEBHOOK_URL secret to be configured in repository settings.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 14:42:00 +01:00
David
d8007c0887 fix: allow package-lock.json in frontend Docker build
All checks were successful
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 17m2s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Successful in 31m59s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Successful in 1s
The .dockerignore was excluding package-lock.json, causing npm ci to fail
with "The npm ci command can only install with an existing package-lock.json".

Commented out the package-lock.json line in .dockerignore to allow it to be
copied into the Docker build context.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 12:33:10 +01:00
David
f25dbd7ab9 fix: remove duplicate :preprod tag and align cache image names
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Frontend - Build, Test & Push (push) Failing after 6m46s
CI/CD Pipeline / Backend - Build, Test & Push (push) Has been cancelled
Fixed invalid Docker tag errors caused by:
1. Duplicate :preprod suffix in image names (xpeditis-backend:preprod:preprod)
2. Mismatched cache image names (backend vs xpeditis-backend)

Changes:
- Backend: images: xpeditis-backend (removed :preprod suffix)
- Frontend: images: xpeditis-frontend (removed :preprod suffix)
- Backend cache: backend:buildcache → xpeditis-backend:buildcache
- Frontend cache: frontend:buildcache → xpeditis-frontend:buildcache

docker/metadata-action automatically adds branch-based tags, so we should
never add :preprod to the base image name.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 12:23:00 +01:00
David
3d871f9813 ci
Some checks failed
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 2m16s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Failing after 6m27s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Has been skipped
2025-11-17 12:05:29 +01:00
David
70c1c9c285 fix: replace GitHub Actions cache with registry cache for Gitea compatibility
Some checks failed
CI/CD Pipeline / Frontend - Build, Test & Push (push) Failing after 6m43s
CI/CD Pipeline / Backend - Build, Test & Push (push) Successful in 19m10s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Has been skipped
GitHub Actions cache (type=gha) is not available in Gitea, causing timeout errors.
Replaced with registry-based cache which works with any container registry.

Changes:
- Backend: cache-from/to type=registry,ref=backend:buildcache
- Frontend: cache-from/to type=registry,ref=frontend:buildcache
- Removed debug step that's no longer needed

This allows Docker layer caching while maintaining Gitea compatibility.
Images are successfully being pushed to rg.fr-par.scw.cloud/weworkstudio

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 11:45:13 +01:00
David
825809febb ci
Some checks failed
CI/CD Pipeline / Frontend - Build, Test & Push (push) Failing after 7m13s
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 16m48s
CI/CD Pipeline / Integration Tests (push) Has been skipped
CI/CD Pipeline / Deployment Summary (push) Has been skipped
2025-11-17 01:58:50 +01:00
David
fb54cfbaf2 fix: correct Docker image tags to avoid duplicate tag names
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 3m20s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
Fixed invalid Docker tag format errors:
- Removed :preprod suffix from base image names in metadata action
- docker/metadata-action already adds branch-based tags automatically
- Unified registry to rg.fr-par.scw.cloud/weworkstudio for both backend and frontend
- This fixes "invalid reference format" error

Before: backend:preprod:preprod (invalid - duplicate tags)
After: backend:preprod (valid)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 01:53:53 +01:00
David
ee38ee6961 fix: add missing domain ports files that were gitignored
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 2m11s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
Root cause: The .gitignore had 'out/' which was ignoring ALL directories
named 'out', including 'src/domain/ports/out/' which contains critical
port interfaces for hexagonal architecture.

Changes:
- Modified .gitignore to only ignore Next.js output directories
- Added all 17 missing files from src/domain/ports/out/
  - audit-log.repository.ts
  - booking.repository.ts
  - cache.port.ts
  - carrier-connector.port.ts
  - carrier.repository.ts
  - csv-booking.repository.ts
  - csv-rate-loader.port.ts
  - email.port.ts
  - index.ts
  - notification.repository.ts
  - organization.repository.ts
  - pdf.port.ts
  - port.repository.ts
  - rate-quote.repository.ts
  - storage.port.ts
  - user.repository.ts
  - webhook.repository.ts

This resolves all "Cannot find module '@domain/ports/out/*'" TypeScript errors.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 01:50:05 +01:00
David
62cad30fc2 debug: add TypeScript config inspection to CI
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 1m3s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
2025-11-17 01:47:43 +01:00
David
8b20a7e548 fix: configure nest build to use tsc compiler directly
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Has been cancelled
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
- Set explicit "builder": "tsc" in nest-cli.json
- Simplified tsconfig.build.json to only extend base config
- Updated build script back to `nest build && tsc-alias`

This ensures NestJS uses the TypeScript compiler that properly respects path mappings in tsconfig.json.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 01:46:57 +01:00
David
a0863d19ac fix: use tsc directly instead of nest build to resolve path aliases
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 2m11s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
- Changed build script from `nest build` to `tsc -p tsconfig.build.json`
- This ensures TypeScript path aliases (@domain/*, @application/*, @infrastructure/*) are properly resolved during compilation
- tsc-alias then converts the resolved paths to relative imports in the output
- Reverted tsconfig.json to original baseUrl: "./" configuration
- Added explicit path aliases to tsconfig.build.json for clarity

Root cause: NestJS's `nest build` command doesn't fully support TypeScript path aliases out of the box. Using `tsc` directly ensures proper path resolution.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 01:41:28 +01:00
David
e1e9b605cc fix: correct TypeScript baseUrl to resolve path aliases during build
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 2m5s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
Changed baseUrl from "./" to "./src" and updated paths to be relative
to src directory. This allows TypeScript to correctly resolve imports
using @domain/*, @application/*, and @infrastructure/* aliases during
compilation.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 01:35:55 +01:00