There are currently several manual (and largely undocumented) steps to follow when starting up a new CloudTAK instance -- especially if attempting to run it locally.
This PR introduces the following measures to attempt to make initial server configuration straightforward for less technical users - and conveniently means I don't have to write reams of documentation ;)
Actions
[x] Add empty server state to signify no users or server config exist
[x] Frontend redirects to System Admin user creation when server is in empty state
[x] Frontend then allows user to login which will return an unconfigured state -- redirecting to the admin page
NOTE: task-{{SHA}} ECR Image has been renamed data-{{SHA}}
Context
There are currently several manual (and largely undocumented) steps to follow when starting up a new CloudTAK instance -- especially if attempting to run it locally.
This PR introduces the following measures to attempt to make initial server configuration straightforward for less technical users - and conveniently means I don't have to write reams of documentation ;)
Actions
emptyserver state to signify no users or server config existemptystateunconfiguredstate -- redirecting to the admin pageNOTE:
task-{{SHA}}ECR Image has been renameddata-{{SHA}}