Generate random default reset token or prevent start

[tacerus]

A default token like "supersecret" is rather insecure, it is prone to users deploying without realizing this. I suggest to set a random value if the variable is not provided or to make the application refuse its startup.

[lkocman]

What's wrong on generating RESET_TOKEN in docker-file? Just keep in mind that random string will be unenterable by a common folk via mobile at the booth. Unless we'd generate something like "HorseChicken123"

[lkocman]

Actually I like the ChickenHorse thing. let me think also how would you tell the user what the string is?

[tacerus]

What's wrong on generating RESET_TOKEN in docker-file?

You would move the hardcoded token from the source code to the image, which is equally poor practice as everyone sharing the image will share a token.

[tacerus]

Random does not have to be complex. :)

[lkocman]

But let's say we do that, how does an operator of booth now what the password is? Would this be clarified in e.g. a request to admin@? Then I guess that would be fine.

[tacerus]

Good question, if it's deployed in the background, and the passphrase is only printed to the output, then an administrator would have to pass it on to the user who added the instance.

[lkocman]

I think that makes sense and could be acceptable workflow. If user really want something specific we can pass it explicitly.