This repository has been archived by the owner on Jun 18, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Backing Up and Moving
Connor Bell (Makeshift) edited this page Nov 8, 2021
·
3 revisions
While it may be easier to just tar
the entire thing to move it (make sure you docker-compose down
first to unmount gdrive!), sometimes you only want to back up runtime config. Here's an idea of where things are stored and what you should back up.
File | Description | Back up? |
---|---|---|
.env |
Contains env vars used in the compose file itself | Yes |
rclone.env |
rclone required for Rclone to run | Yes |
service_accounts/ |
Generated service accounts run | Yes |
runtime_conf/ |
Contains all the service-specific config generated after first startup and during use | Yes |
rclone_conf/ |
If you've made any tweaks to the mount settings, you might want to back this up | Maybe |
traktarr.json |
If you're using traktarr, you'll probably need this config file. | Maybe |
shared/separate |
Individual mounts for downloaders (You can back these up if you care about losing unsorted or in-progress downloads) and in-progress uploads | Maybe |
shared/caches |
Contains Rclone's disk caches | Maybe |
shared/merged |
Union mount containing Google Drive, download and merged upload directories | No |
shared/plex |
Mount containing Google Drive for Plex specifically | No |
plex.env |
This isn't used after initial setup. | No |