I have been helping
@robsworld78 with his initial loading script (well I hope I have been of some help,lol) and I think it goes a long way to automate the initial loading things up but it got me thinking about how we can move this to the next stage for the end user. It doesn't need to go to that next stage but there are a lot of users that are not tech savvy etc, that just want to plug something in and use it. To that end here are some of the things that I think if we could set via the reef-pi interface would move us to more of an appliance type setup vs the setup that we have today:
Critical
tzdata (need the ability to set,update, modify)
pi user password (ability to set, update, modify)
update the OS software
Nice to have
Hostname (ability to set, update, modify)
Wireless networking is pretty straightforward since the image contains a blank wpa_supplicant.conf file in the /boot directory and they just add the SSID and PSK to join the network, now knowing what the address turns out to be is another issue and need to think more about that. I always use a DHCP reservation for the given mac address but how do all of the IOT devices handle it, there is probably an easier way but something to consider.
I think with a few additions to the admin screen where it allows a user to do everything through the web would possibly open things up to more users, food for thought.