[GH-ISSUE #24] Answer file passing to script to modify defaults #23

New issue

Open

opened 2026-03-03 11:13:26 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 11:13:26 +03:00

Owner

Originally created by @andiohn on GitHub (Jul 30, 2024).
Original GitHub issue: https://github.com/debloper/xiosk/issues/24

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.

Originally created by @andiohn on GitHub (Jul 30, 2024). Original GitHub issue: https://github.com/debloper/xiosk/issues/24 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.

kerem added the

good first issue

label

2026-03-03 11:13:26 +03:00

kerem referenced this issue

2026-03-03 11:13:26 +03:00

[GH-ISSUE #23] Auto Mouse Hiding Enhancement #24

kerem commented

2026-03-03 11:13:27 +03:00

Author

Owner

@andiohn commented on GitHub (Jul 30, 2024):

This would require an established file format and variable names etc.

@andiohn commented on GitHub (Jul 30, 2024): This would require an established file format and variable names etc.

kerem commented

2026-03-03 11:13:27 +03:00

Author

Owner

@debloper commented on GitHub (Jul 31, 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.

@debloper commented on GitHub (Jul 31, 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.