Everybody who runs a docker image of ds-host will have the same setup_key. This goes against the idea of a secret setup key.
The problem is the key is generated in the initial migration step. This is incorrect because creating a setup_key not a migration task anyways.
The solution might be to let the setup key controller have an Init function called when starting ds-host that checks the DB for the presence of an admin, and creates the setup key if none.
Everybody who runs a docker image of ds-host will have the same
setup_key
. This goes against the idea of a secret setup key.The problem is the key is generated in the initial migration step. This is incorrect because creating a
setup_key
not a migration task anyways.The solution might be to let the setup key controller have an Init function called when starting ds-host that checks the DB for the presence of an admin, and creates the setup key if none.