You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
andiohn
changed the title
Answer file loading!
Answer file passing to script to modify defaults
Jul 30, 2024
The config.json file does just that & it's structured to be manually editable. That's also specifically why the cleanup script takes a backup of the config.json file to make reinstallation painless.
All you need to do is edit/replace (overwrite) the config file with your custom config file, and reboot.
Keeping the issue open, just in case someone wants to parameterize the config file and pass it on with a flag or environment variable or something to load up the file from a different path/location/protocol etc. But otherwise, this is already taken care of.
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.
The text was updated successfully, but these errors were encountered: