I think this should be a single command - server start
not sure if it makes a difference, im still trying to figure this out myself. Especially the mountain of passwords…
This is kind of bad thing to do, someone wrote a couple of words about it here. Just bad security practise. Not sure why they put it into their example configs when its neither necessary nor recommended…
I think it’s the other way round:
the USER variable is the WebUser (at least to the things others have put into their docker files), in my case its labeled “repo user” and as a comment it says “This is the user that gets to use the repository”. I have no idea what its supposed to do because it doesn’t work.
I also feel like there is a mix between what you need to set on a client vs server config.
You can follow my own post here since our problems seem to overlap
The only thing i think i have figured out by now is that the Repo Key is only needed by the Server. The client doesn’t need to know it because the client access used the API instead of accessing the repo directly. That however still leaves three passwords to figure out:
server-passwordNot sure but i think you need this to connect the client to the server however what are user passwords created when using kopia server user addused for then?
server-controll-passwordWhy is this used? Does this replace the recular USER und KOPIA_PASSWORD when running in server mode?