dusk-network / dusk-network/node-installer
Make target user detection explicit
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 38
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Summary
The installer currently uses logname to determine which user's home directory should receive the wallet configuration.
This is fragile in non-login contexts such as cloud-init, automation, or some sudo environments. In those cases, logname can fail or return a user that is not the intended operator account.
Possible solution design or implementation
Make the target operator user explicit or more reliably derived.
For example, the installer could accept an optional --user flag, and otherwise fall back to the current behavior or a documented default. The installer should print the selected user and home directory before making changes, so misconfiguration is visible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the installer entry point and locate its current logname usage. Trace how the target home directory is selected, then clarify the supported explicit-user and fallback behavior. Done means the selected user and home directory are shown before changes and non-login contexts are covered by tests or documented verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100