──────
Build and Push Docker Images / detect-changes (push) Successful in 11s
Build and Push Docker Images / build-auth-api (push) Successful in 1m0s
Build and Push Docker Images / build-employee-api (push) Successful in 1m2s
Build and Push Docker Images / build-transit-api (push) Successful in 1m1s
Build and Push Docker Images / build-error-log-api (push) Successful in 1m5s
Build and Push Docker Images / build-admin-ui (push) Successful in 1m13s
Build and Push Docker Images / build-monitoring-ui (push) Successful in 1m15s
Build and Push Docker Images / deploy-test-node (push) Successful in 3s
Build and Push Docker Images / detect-changes (push) Successful in 11s
Build and Push Docker Images / build-auth-api (push) Successful in 1m0s
Build and Push Docker Images / build-employee-api (push) Successful in 1m2s
Build and Push Docker Images / build-transit-api (push) Successful in 1m1s
Build and Push Docker Images / build-error-log-api (push) Successful in 1m5s
Build and Push Docker Images / build-admin-ui (push) Successful in 1m13s
Build and Push Docker Images / build-monitoring-ui (push) Successful in 1m15s
Build and Push Docker Images / deploy-test-node (push) Successful in 3s
### Summary of Changes
1. Documentation Consolidation:
• Relocated the docs/ folder and all repository .md files (README.md, DEPLOYMENT.md, DOCKER_README.md,
DOMAINS_README.md, GETTING_STARTED.md, CI_CD_PORTAINER_GUIDE.md, ADMIN_DEPLOYMENT_SUMMARY.md,
SECURITY_PRIVATE_FILES.md, handoff.md, azure-project-plan.md, plus service-specific READMEs) into .
• Updated document links in README.md.
2. AI Agent Project Map:
• Created PROJECT_MAP.md in the project root containing complete architecture diagrams, service specs, ports, DB
schemas, environment variables, and developer workflows.
• Added PROJECT_MAP.md to .gitignore.
3. Monitoring UI & Infrastructure Integration:
• Added monitoring_ui service to docker-compose.yml (port 5175).
• Configured Gitea workflow docker-build.yml for monitoring_ui builds.
• Added CORS middleware headers in index.js.
• Added nginx.conf copy step in Dockerfile.
──────
### Recommended Commit Message
docs: consolidate project documentation into monitoring_ui and add agent project map
- Move all markdown documentation files and docs/ folder into monitoring_ui/docs/
- Update documentation hub index (monitoring_ui/docs/README.md) with relative paths
- Generate comprehensive AI agent reference map (PROJECT_MAP.md) in repository root
- Add PROJECT_MAP.md and monitoring_ui build output/env overrides to .gitignore
- Integrate monitoring_ui service into docker-compose.yml and Gitea CI workflow
- Configure CORS handling in employee_api for monitoring dashboard access
──────
### Alternative Short Commit Message
refactor(docs): move docs to monitoring_ui and create AI agent PROJECT_MAP.md
This commit is contained in:
@@ -1,45 +0,0 @@
|
||||
# Transit Driver XP
|
||||
|
||||
Native Win32 driver client targeting Windows XP-era systems.
|
||||
|
||||
For Windows XP compatibility, the client temporarily uses the LAN services:
|
||||
|
||||
- Login: `http://192.168.68.66:5000/login`
|
||||
- Assigned schedules: `http://192.168.68.66:5001/driver/schedules/daily`
|
||||
- Route stops: `http://192.168.68.66:5001/bus-lines/:busLineId/stops`
|
||||
|
||||
This HTTP fallback avoids the TLS 1.2/certificate limitations of Windows XP.
|
||||
|
||||
Schedules are assigned through `transit.shifts`; the client does not expect a
|
||||
`driver_id`, `bus_id`, or `weekdays` column on `transit.schedules`.
|
||||
|
||||
## Build
|
||||
|
||||
```bash
|
||||
make clean && make
|
||||
```
|
||||
|
||||
## Distribution
|
||||
|
||||
Build the installer with:
|
||||
|
||||
```bash
|
||||
makensis installer.nsi
|
||||
```
|
||||
|
||||
Distribute `TransitDriverXPSetup.exe`. It detects an existing installation,
|
||||
stops the previous client, and replaces it in the same directory.
|
||||
|
||||
## Login diagnostics
|
||||
|
||||
If the app shows `Driver service unreachable`, open `driver_xp.log` in the same
|
||||
folder as the installed `driver_xp.exe` and inspect the latest entries. The log
|
||||
records the failing stage and WinHTTP or HTTP status code, but never writes the
|
||||
password or JWT token.
|
||||
|
||||
Common codes:
|
||||
|
||||
- `12007`: hostname could not be resolved (DNS)
|
||||
- `12029`: connection to the server failed
|
||||
- `12175`: HTTPS certificate or TLS validation failed
|
||||
- `401` or `403`: the server responded, but authentication was rejected
|
||||
Reference in New Issue
Block a user