1
Fork 0
mirror of https://github.com/Steffo99/backup-duplicity.git synced 2024-12-21 19:24:18 +00:00

siiiiiiiiiiiiigh

This commit is contained in:
Steffo 2024-10-25 06:47:07 +02:00
parent 28ff2d87ee
commit 2c583d49e2
Signed by: steffo
GPG key ID: 5ADA3868646C3FC0

View file

@ -16,19 +16,6 @@ Backup solution for Docker volumes based on Duplicity
### Backup with Google Drive
> [!CAUTION]
>
> For authentication to work correctly after [Google's removal of the OOB Flow](https://developers.google.com/identity/protocols/oauth2/resources/oob-migration), your `http://localhost:80` address needs to match the `http://localhost:80` of the Gestalt Amadeus container.
>
> This is not an issue if you can launch a browser on the same machine you're configuring Gestalt Amadeus, but it might be troublesome for non-graphical servers, where this is not possible.
>
> As a quick band-aid to the issue, you can temporarily set up an SSH tunnel towards the server for the duration of the setup process:
>
> ```bash
> # This unfortunately requires root access, since the port we have to tunnel, 80, has a number lower than 1024.
> sudo ssh -L 80:80 yourserver
> ```
1. Create a new Docker volume with the name `ga_cache`, which Duplicity will use to temporarily store previous backups:
```bash
@ -147,4 +134,19 @@ Backup solution for Docker volumes based on Duplicity
Complete the authentication to proceed.
(Make sure to read the alert below if you're having issues!)
1. You should be done! Make sure backups are appearing in the Google Drive directory you've configured.
> [!CAUTION]
>
> For authentication to work correctly after [Google's removal of the OOB Flow](https://developers.google.com/identity/protocols/oauth2/resources/oob-migration), your `http://localhost:80` address needs to match the `http://localhost:80` of the Gestalt Amadeus container.
>
> This is not an issue if you can launch a browser on the same machine you're configuring Gestalt Amadeus, but it might be troublesome for non-graphical servers, where this is not possible.
>
> To apply a quick band-aid to the issue, you can temporarily set up an SSH tunnel towards the server for the duration of the setup process:
>
> ```bash
> # This unfortunately requires root access, since the port we have to tunnel, 80, has a number lower than 1024.
> sudo ssh -L 80:80 yourserver
> ```