Commit graph

13 commits

Author SHA1 Message Date
9da95a27b3 Add "steam"-specific type
This implementation allows each platform to choose how to launch Steam (on Linux, we use the snap as the examples suggested before), and keeps Steam alive after an activity exits so that save sync, game updates, etc. can continue to run.

Change written by Codex 5.2 on medium:

Consider this GitHub issue https://github.com/aarmea/shepherd-launcher/issues/4. On Linux, an activity that uses the "steam" type should launch Steam via the snap as shown in the example configuration in this repository.

Go ahead and implement the feature. I'm expecting one of the tricky bits to be killing the activity while keeping Steam alive, as we can no longer just kill the Steam snap cgroup.
2026-02-07 16:22:55 -05:00
d823ed0a19 Implement Flatpak application type 2026-01-09 22:26:26 -05:00
1e584f2907 Add optional child process logging 2026-01-02 19:00:27 -05:00
3b1a2fb166 shepherdd shouldn't require root to run 2025-12-31 22:33:44 -05:00
5e5e6f6806 Lint: electric boogaloo 2025-12-29 17:51:55 -05:00
f5d7d69578 :%s/daemon/service/g 2025-12-29 12:52:03 -05:00
1fe6971fb2 Add CI 2025-12-28 22:07:23 -05:00
fb7503eeb4 Add volume policy 2025-12-28 09:30:54 -05:00
336a8f7eb2 Use common command/args syntax 2025-12-28 00:35:33 -05:00
d449a7adff Implement time-unrestricted activities 2025-12-27 23:26:49 -05:00
74e54a016c Allow arguments for Snap apps 2025-12-27 20:53:13 -05:00
252ee4dd8d Pull Snap process managment into its own entry kind 2025-12-27 14:27:34 -05:00
ac2d2abfed (Hopefully) productionized shepherdd 2025-12-26 15:35:27 -05:00