Answer file passing to script to modify defaults
- Dominant language
- Astro
- Stars
- 348
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
What if you directed the bash script to an answer file and then all of your customizations could simply be loaded? I'm thinking Piosk specific ones, nothing extra.
This would be huge because we could have one answer file for all instances, and then it would be selected based on the hostname of the device. This could also mean that we could re-deploy super fast by just maintaining a fresh example. Kind of like Ansible but not really ansible.
I was thinking of having an answer file in like github and then passing the path in the installation path.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the bash installation script and tracing how installation arguments and defaults are currently handled. Define the answer-file format and how a path supplied during installation loads Piosk-specific customizations, including hostname-based selection. Done means a fresh deployment can use the maintained answer file to reproduce the intended instance configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100