Sven laptop
f935bbeb8c
Build and Push Docker Images / detect-changes (push) Successful in 10s
Build and Push Docker Images / build-auth-api (push) Successful in 1m0s
Build and Push Docker Images / build-employee-api (push) Successful in 1m3s
Build and Push Docker Images / build-transit-api (push) Successful in 59s
Build and Push Docker Images / build-error-log-api (push) Successful in 1m9s
Build and Push Docker Images / build-admin-ui (push) Successful in 1m20s
Build and Push Docker Images / deploy-test-node (push) Successful in 4s
46 lines
1.3 KiB
Markdown
46 lines
1.3 KiB
Markdown
# 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
|