rclone failed to create config file about bitwarden_gcloud HOT 2 CLOSED

That's not a bad solution, except I'm worried about those who have it in the old location getting a new docker-compose and not updating their .env and moving the file.

I'd like a solution that keeps backwards compatibility, especially when it comes to backups, but not sure there is one without being excessively hacky.

I did try to add a mount from ${PWD}/bitwarden/rclone.conf:/data/rclone/rclone.conf, however that fails to start when there is no rclone.conf in that location.

In the meantime I'm going to update the bitwarden mount to not be writable.

from bitwarden_gcloud.

I took another look at this, and came up with the changes as you suggested @whyb0rn-

Changes:

• .env.template: move to new location
  • BACKUP_RCLONE_CONF=/data/rclone/rclone.conf
• docker-compose.yml: make data read only, mount new rclone folder
  • ${PWD}/bitwarden:/data:ro
  • ${PWD}/bitwarden/rclone:/data/rclone
  • ${PWD}/bitwarden/backups:/data/backups

There are likely scenarios that I could imagine:

• New users - use new compose and new env template: OK
• Old users get the new compose - use new compose and old env: Probably OK
  • rclone.conf is still in /data which is READ ONLY. This will continue to work for backups until they update their rclone conf using the instructions in the wiki.
  • Resolution: Most old users won't have an issue. If they update their rclone.conf they will get a read-only error, and hopefully find the fix in the wiki.

I'm happy with this solution, and will be pushing the changes. Thanks @whyb0rn.

from bitwarden_gcloud.