Closed r748 closed 3 months ago
Hi @r748 , I've been using the docker version for several months now. I'm rebuilding BorgWarehouse in a Debian environment and I'll tell you how it goes.
Thanks! Maybe this might also be related to issue #171...
I've just reassembled a Debian environment without Docker and I can confirm that the documentation and operation are OK ✅ !
The command copied is the right one. And if you want to know the technical details, the authorized path is in the authorized_keys
file. Your backups are located in /home/borgwarehouse/repos
when you run one.
Did you run a backup and check where it was afterwards before opening this issue ? Or did you open this issue just by seeing the command in the quicksetting ? 😀
Actually, I did perform a backup and the repository was created in the /home/borgwarehouse
directory, as described above. However I found the problem now, thanks to you pointer to the authorized_keys
file... I was using an incorrect SSH key on my client and therefore command="cd /home/borgwarehouse/repos
wasn't applied.
I have setup borgwarehouse 2.2.0 according to the Debian deployment guide. After creating a repository, when I copy the link via the button on the top right corner of the repository view, the path reads
ssh://borgwarehouse@myserver:myport/./328aa97e
. This leads to the repository being created under/home/borgwarehouse/328aa97a
instead of/home/borgwarehouse/repos/328aa97a
.