Currently in standalone mode, the user is faced with a connection screen even when all of the required values are configured (username, password, dashboard name, connection etc.) in the config json.
This may suit some environments and use cases, however it is an unwanted distraction for those wanting to use neodash as a public facing information portal for less technical users. It also unnecessarily exposes connection information.
Describe the solution you'd like
1.) Add a configuration key to the config.json that allows neo-dash to auto connect if the other required keys are present.
(username, password, dashboard name, database, connection etc.)
2.) Alternatively, provide a configuration key that provides a 'stripped' connection splash screen with only a description field and connect button.
Not as elegant as 1, but less confronting for non technical users.
Current situation
Currently in standalone mode, the user is faced with a connection screen even when all of the required values are configured (username, password, dashboard name, connection etc.) in the config json. This may suit some environments and use cases, however it is an unwanted distraction for those wanting to use neodash as a public facing information portal for less technical users. It also unnecessarily exposes connection information.
Describe the solution you'd like 1.) Add a configuration key to the config.json that allows neo-dash to auto connect if the other required keys are present. (username, password, dashboard name, database, connection etc.)
2.) Alternatively, provide a configuration key that provides a 'stripped' connection splash screen with only a description field and connect button. Not as elegant as 1, but less confronting for non technical users.
Describe alternatives you've considered None