Skip to main content
Edge can only see folders that Docker mounts beneath /scan inside the container. To back up more than one location, add one volume entry per folder. Your files stay where they are on your computer, including on other drives. Each entry has the form:
For example, "D:/Projects:/scan/projects" makes D:\Projects appear as /scan/projects in Edge. Use forward slashes in Compose, including for Windows paths.

Set it up

1

Open docker-compose.yml

Find the volumes: section under the edge service.
2

Replace the single-folder entry

Remove this line:
and add one entry per folder in its place. Give each a different name under /scan:
docker-compose.yml
Keep the other volume entries unchanged. The example Compose file includes these lines as comments; remove the # to activate them.On Linux, use paths such as "/home/alice:/scan/main" and "/mnt/data/projects:/scan/projects".
3

Update .env

Remove SCAN_DIR from .env, since the entries above now name the folders directly. If you set SCAN_ROOT, keep it at /scan.
4

Recreate the container

From the folder with the Compose file:
5

Choose what to back up

Refresh Edge’s UI. The folder browser now shows:
Create jobs for the folders you want. See Backup jobs.
Don’t make /scan itself a job. It would become one combined job covering every mounted folder.

Add another drive later

Add another line to the same volumes section, recreate the container, refresh Edge, and create a job for the new folder:
Adding a volume only makes a folder visible. It isn’t backed up until you create a job for it.

Things to know

  • Job names must be unique across all mounted folders. The main and projects labels don’t separate same-named jobs on Central, so use names like main-photos and projects-photos.
  • Mounts need write access for Edge to save markers and restore files.
  • Max Depth counts the extra level. The /scan/<name> folders add one level, so raise Max Depth in settings if your markers are deep.
  • Moving an existing folder under a new mount? Keep its job name so it continues its history on Central. Edge’s local state is keyed by path, so the next scan may upload it again.
These steps also apply to the development Compose file in edge/. Adding mounts does not require a Central storage migration: snapshots remain organized by edge_id/edge_instance_id/job_name.