2019-09-24, 10:57 AM
Would it make sense to have the GUI setup app in the sk server codebase and have it call signalk-server-setup with command line parameters? Then we could have one place where the logic to create sk server basic settings is mastered.
An example: we should add a new environment parameter. If command line and GUI setup scripts are separate it is very easy to miss updating the separate one.
But do we actually need a separate GUI for this? What about launching the server admin in ”first time setup wizard” mode, so that it would guide you through the basic setup? This would have the added benefit of being usable everywhere with a browser and teach people to use the SK admin. It could also auto discover your serial devices and guide you through their setup.
What do you think?
Sent from my iPhone using Tapatalk
An example: we should add a new environment parameter. If command line and GUI setup scripts are separate it is very easy to miss updating the separate one.
But do we actually need a separate GUI for this? What about launching the server admin in ”first time setup wizard” mode, so that it would guide you through the basic setup? This would have the added benefit of being usable everywhere with a browser and teach people to use the SK admin. It could also auto discover your serial devices and guide you through their setup.
What do you think?
Sent from my iPhone using Tapatalk