diya/fchaty
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct production relay hostname

Browse Source
This commit is contained in:
diyaa 2026-07-26 20:15:55 +02:00
parent f0b930ebce
commit 1225103dc9
6 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
FchatiApp/Sources/FchatiApp/Networking/RelayAPI.swift
View File

@ -55,7 +55,7 @@ actor RelayAPI {
return try await execute(request) return try await execute(request)
} }
private let baseURL = URL(string: "https://fchati.diyaa.de")! private let baseURL = URL(string: "https://fchaty.diyaa.de")!
private let session = URLSession.shared private let session = URLSession.shared
private init() {} private init() {}

2
FchatiApp/Sources/FchatiApp/Session/AppSession.swift
View File

@ -16,7 +16,7 @@ final class AppSession: ObservableObject {
@Published var messages: [ChatMessage] = [] @Published var messages: [ChatMessage] = []
private let relayAPI = RelayAPI.shared private let relayAPI = RelayAPI.shared
private let webSocket = WSClient(url: URL(string: "wss://fchati.diyaa.de/ws")!) private let webSocket = WSClient(url: URL(string: "wss://fchaty.diyaa.de/ws")!)
private let messageStore = MessageStore.shared private let messageStore = MessageStore.shared
private var incomingMessagesTask: Task<Void, Never>? private var incomingMessagesTask: Task<Void, Never>?

1
IMPLEMENTATION_STATUS.md
View File

@ -195,6 +195,7 @@
- Verified the Docker Compose configuration with the example environment and confirmed a local relay instance responds successfully from `GET /health`. - Verified the Docker Compose configuration with the example environment and confirmed a local relay instance responds successfully from `GET /health`.
- Extended WebSocket serialization coverage to preserve the sender timestamp used for offline message delivery. - Extended WebSocket serialization coverage to preserve the sender timestamp used for offline message delivery.
- The relay now defaults to the production Traefik certificate resolver (`myresolver`) and allows a host-specific override through `TRAEFIK_CERT_RESOLVER`. - The relay now defaults to the production Traefik certificate resolver (`myresolver`) and allows a host-specific override through `TRAEFIK_CERT_RESOLVER`.
- Corrected the production hostname to `fchaty.diyaa.de` in the relay route and macOS application HTTP and WebSocket clients.
## Bug Fixes — Post-Review ✅ ## Bug Fixes — Post-Review ✅

4
TASKS.md
View File

@ -67,7 +67,7 @@ These are decisions made during planning — do not change without revisiting th
|------|---------| |------|---------|
| `relay-server/src/index.js` | Node.js relay — Pairing, WebSocket, offline queue (disk-backed), read receipts, file upload/download | | `relay-server/src/index.js` | Node.js relay — Pairing, WebSocket, offline queue (disk-backed), read receipts, file upload/download |
| `relay-server/Dockerfile` | Multi-stage Alpine build | | `relay-server/Dockerfile` | Multi-stage Alpine build |
| `relay-server/docker-compose.yml` | Traefik labels for `fchati.diyaa.de`, three persistent volumes (files, queue, pairing) | | `relay-server/docker-compose.yml` | Traefik labels for `fchaty.diyaa.de`, three persistent volumes (files, queue, pairing) |
| `relay-server/.env.example` | Environment variable template | | `relay-server/.env.example` | Environment variable template |
| Git repo | `git.mohfarawati.de/diyaa/fchaty` | | Git repo | `git.mohfarawati.de/diyaa/fchaty` |
@ -383,7 +383,7 @@ Context:
- Repo: https://git.mohfarawati.de/diyaa/fchaty.git - Repo: https://git.mohfarawati.de/diyaa/fchaty.git
- App folder: FchatiApp/ (Swift Package, no Xcode, SPM only) - App folder: FchatiApp/ (Swift Package, no Xcode, SPM only)
- macOS 14+, Swift 5.9+, no third-party libraries - macOS 14+, Swift 5.9+, no third-party libraries
- Relay server is already running at https://fchati.diyaa.de - Relay server is already running at https://fchaty.diyaa.de
Task: [paste the full task section here, e.g. TASK-04] Task: [paste the full task section here, e.g. TASK-04]

1
relay-server/.env.example
View File

@ -6,3 +6,4 @@ FILE_TTL_DAYS=30
TRAEFIK_CERT_RESOLVER=myresolver TRAEFIK_CERT_RESOLVER=myresolver
# Required for POST /admin/cleanup. Generate a unique value, for example: openssl rand -hex 32 # Required for POST /admin/cleanup. Generate a unique value, for example: openssl rand -hex 32
ADMIN_TOKEN=replace-with-a-unique-random-secret ADMIN_TOKEN=replace-with-a-unique-random-secret
TRAEFIK_CERT_RESOLVER=letsencrypt

2
relay-server/docker-compose.yml
View File

@ -12,7 +12,7 @@ services:
- traefik-net - traefik-net
labels: labels:
- "traefik.enable=true" - "traefik.enable=true"
- "traefik.http.routers.fchati.rule=Host(`fchati.diyaa.de`)" - "traefik.http.routers.fchati.rule=Host(`fchaty.diyaa.de`)"
- "traefik.http.routers.fchati.entrypoints=websecure" - "traefik.http.routers.fchati.entrypoints=websecure"
- "traefik.http.routers.fchati.tls.certresolver=${TRAEFIK_CERT_RESOLVER:-myresolver}" - "traefik.http.routers.fchati.tls.certresolver=${TRAEFIK_CERT_RESOLVER:-myresolver}"
- "traefik.http.services.fchati.loadbalancer.server.port=3000" - "traefik.http.services.fchati.loadbalancer.server.port=3000"