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

Fix relay storage permissions

Browse Source
This commit is contained in:
diyaa 2026-07-26 20:57:05 +02:00
parent 1225103dc9
commit e1e8ff89cd
2 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
IMPLEMENTATION_STATUS.md
View File

@ -196,6 +196,7 @@
- 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. - Corrected the production hostname to `fchaty.diyaa.de` in the relay route and macOS application HTTP and WebSocket clients.
- `relay-server/Dockerfile` initializes all persistent-data paths as the unprivileged `node` user, preventing pairing, queue, and upload write failures on newly created volumes.
## Bug Fixes — Post-Review ✅ ## Bug Fixes — Post-Review ✅

3
relay-server/Dockerfile
View File

@ -10,7 +10,8 @@ COPY --from=deps /app/node_modules ./node_modules
COPY src/ ./src/ COPY src/ ./src/
COPY package.json ./ COPY package.json ./
RUN mkdir -p /data/files RUN mkdir -p /data/files /data/queue /data/pairing \
&& chown -R node:node /data
USER node USER node