snowspeeder/pi-web
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add sessiond restart command to docs

Browse Source
This commit is contained in:
Federico Jaramillo Martinez
2026-05-07 14:04:56 +02:00
parent 886c0fcde9
commit 34df785b68
2 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+7 -1
View File
@@ -7,4 +7,10 @@ This project is expected to run locally using split systemd user services:
When working on this project, assume the session runtime owner is long-lived and separate from the autoreloading UI/API process. Browser disconnects and UI/API restarts should not stop active Pi sessions.
If you make changes that affect `src/server/sessiond.ts`, session runtime ownership, the session daemon protocol, or any code path only loaded by the session daemon, inform the user that `pi-web-sessiond.service` must be manually restarted. Changes to the web/API/UI side generally only require the `pi-web-ui-dev.service` autoreload/restart path.
If you make changes that affect `src/server/sessiond.ts`, session runtime ownership, the session daemon protocol, or any code path only loaded by the session daemon, inform the user that `pi-web-sessiond.service` must be manually restarted and give them this command:
```bash
systemctl --user restart pi-web-sessiond.service
```
Changes to the web/API/UI side generally only require the `pi-web-ui-dev.service` autoreload/restart path.
README.md
+7 -1
View File
@@ -94,7 +94,13 @@ journalctl --user -u pi-web-sessiond.service -f
journalctl --user -u pi-web-ui-dev.service -f
```
Because `sessiond` is intentionally not watched or restarted automatically, code changes that affect `src/server/sessiond.ts` or session runtime ownership require manually restarting `pi-web-sessiond.service`. Restarting only the UI dev service is enough for changes in the web/API/UI processes.
Because `sessiond` is intentionally not watched or restarted automatically, code changes that affect `src/server/sessiond.ts` or session runtime ownership require manually restarting `pi-web-sessiond.service`:
```bash
systemctl --user restart pi-web-sessiond.service
```
Restarting only the UI dev service is enough for changes in the web/API/UI processes.
For deployment: