Getting Started: 2. Configuring Marauder

These wiki pages are still under construction and may not work!

Configuring Marauder

Marauder uses a .env environment variable file to configure Rclone. This section will walk you through obtaining those.

By default, Marauder will use Rclone's crypt mount to encrypt all files (and their filenames) on the Team Drive. If you wish to change this behaviour you can edit the rclone_conf/rclone_multi_template file, but the defaults do work.

rclone.env

• Make a copy of the template file

cp rclone.env.template rclone.env

• Fill the template out with the below information.

rclone_encryption_password1 & rclone_encryption_password2

If you have a previous Rclone crypt setup

If you have previously set up Rclone with encryption, you can take password and password2 from your rclone.conf file and use them here.

Generating new encryption keys

If you need to generate new encryption keys, Marauder includes a container that borrows the script that Rclone uses to create its encrypted keys.

The following command will output two freshly generated encryption keys for you:

setup/generate_rclone_keys.sh

Note that if you ever lose these keys, you will lose access to all the data uploaded to Google Drive! Make sure you back these up safely!

rclone_gdrive_mount_folder

This is the top level encrypted folder. It should be encrypted.

rclone_team_drive_ids

This is a list of space-separated team drive IDs that you should have noted down when doing part 1.

Done!

You should now have an rclone.env that looks something like this:

# Rclone
SECRETS_SET=true
rclone_encryption_password1=7nMwYhDFUkikVuXezHM5IKIfTKzY1xRhTRJ7n2oFR4tH9CN_
rclone_encryption_password2=mPDwbGcnFW0pCttUhPAxYNfj4Ttalldgcic7v5xoAp1zv
rclone_gdrive_mount_folder=encrypted
rclone_team_drive_ids=0Afoobzlzsasfaf9PVA 0Abarbaroow9fooPVA 0ff-b1hhfNoXboo9PVA

Next

You can now move on to the next step, Starting the Stack.