kojq
commented
1 year ago All entries except credentials are filled by default and can thereby only be changed. As a result, excluding credentials, we do not need to check if user-modifiable "variables" are being filled prior to install.
Consider implementing fuzzy search for a faster setup.
Disk
WARNING:
Back up data for all devices.
Ensure the disk name is correct.
The entire disk will be wiped.- default: guess with
disk=$(lsblk -do NAME | tail -1)since USB connected devices could also be installed upon
Credentials
users
- detection: at least one user exists
- detection: all user credentials must have username and password
- default: none
- typing is required
root
- default: waterfall from first user password in the list (must be the case during install time)
- typing is optional
Package
- default: prewritten list
- typing is optional
Timezone
- default: UTC
Keyboard
- default: U.S. (or waterfall if possible)
Language
- default: U.S. (or waterfall if possible)
Hostname
- default: arch
- typing is optional
Services
systemctl enable
- default: provided for package list
- typing is optional
systemctl start
- default: provided for package list
- typing is optional
We can do a selection menu. It should be lean in selection and have an efficient layout for mass deployment.
While we could have an optional configuration file, it is a bad practice for this project because information such as credentials and location data are more accessible (regardless of if the harm is statistically negligible). Even a partial configuration file consisting of only technical choices would be obsolete due to having more for all parties to manage. A configuration file would be desirable for tuning hefty amounts of technical choices. At that point, this project would become an interactive install guide, and that is not the goal. Thus, it's best to not have a configuration file for security, privacy, safety, and development. Instead, an interactive selection menu can be provided.