User desktop configuration and persistence
- Dominant language
- Nix
- Stars
- 17
- Forks
- 16
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 19
Description
There should be an option to mount $HOME from NFS on desktops:
- Persistence should strictly be *opt in*
- Check box on login screen to mount remote
- This is the easy stateless option, but one alternative is to have user configuration. but this would require having a drop down for "Persist Home: On, Off, Auto (User Settings)"
- Above point brings up the question of where to store desktop configuration. Currently, we put desktop config files in `~/.config/ocf` in the remote home. Should this continue? or should we use LDAP.
- Should it be the same or separate from the home mounted on ssh.ocf.io? There are benefits to both, and it should also be configurable. I can imagine a case where a user has a systemd user unit on ssh.ocf.io, does not want to run it on the desktop, and does not want to have to have if elses in every unit.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the desktop login flow and the existing remote-home setup, including the ~/.config/ocf location and the home mounted on ssh.ocf.io. Clarify whether persistence is opt-in, how the login checkbox or user settings should work, and whether desktop and SSH homes are shared. Done means these configuration and behavior decisions are resolved and the implementation scope is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nixos
- Domain
- desktop, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100