# 5. Folder Monitoring

Address: http://localhost:55000/configFolders tab

This is where you tell TotumService which local folders to watch, which files to match, and where to upload them in S3.


# What happens when you add a folder?

Prerequisite: enable a transfer provider (for example S3) on the Dashboard before uploads can succeed.

On a schedule (often every 30 seconds), TotumService scans the folder. When it finds a file that matches your include patterns:

  1. Detected — recorded in the tracking database
  2. Stable — waits until the file stops changing
  3. Uploading — sent to your bucket via the transfer provider (usually S3)
  4. Uploaded — success (optionally deletes the local file if you enabled that)

Changes you make here usually apply without restarting the service.

Track individual files in Database Explorer.

In the folder list, Detected is how many files the monitor has seen; Uploaded is how many reached cloud storage. Disable pauses scanning without deleting the configuration.


# Add a folder

  1. Open Configuration → Folders.
  2. Click Add Folder.
  3. Fill in the form (see field guide below).
  4. Click Save Folder.
  5. Confirm the folder appears in the list with status Active (if you left Enabled on).

# Empty list

If no folders are configured, use Add First Folder and follow the on-screen checklist:

  1. Enable a transfer provider on the Dashboard
  2. Add a folder pointing at a test path
  3. Drop a matching file into that folder
  4. Confirm progress in Database Explorer or Active Transfers

# Field guide

Field Required Guidance
Folder Name Yes Short label for logs and Database Explorer (not sent to S3). Cannot be changed after creation — delete and re-add to rename
Folder Path Yes Full Windows path the service account can read, e.g. C:\Data\Reports
Include Patterns Yes Globs such as *.pdf, *.docx. Use * for everything
Exclude Patterns No Skip temp files, e.g. *.tmp, ~$*
Destination Bucket Yes S3 bucket your provider credentials can write to (appsettings.json)
Destination Prefix No Path inside the bucket, e.g. reports/ → file becomes reports/myfile.pdf
Recursive No Also watch subfolders
Delete after upload No Removes the local file after a successful upload
Enabled No Start monitoring immediately after save

# Warning: Delete after upload

This is permanent for the local copy. Only enable it if you are sure files are backed up or no longer needed on disk.


# Pattern examples

Goal Include Exclude
PDFs only *.pdf (none)
Documents *.pdf, *.docx *.tmp
Images *.jpg, *.png (none)
Everything except temps * *.tmp, *.partial

Quick-add buttons on the form help you insert common patterns.


# Managing existing folders

From the folder list you can typically:

  • Enable / Disable monitoring without deleting the config
  • Edit path, patterns, bucket, options (folder name stays fixed)
  • Delete the configuration only — does not delete files on disk or objects already in S3

Use disable when you want to pause uploads temporarily.


# Permissions checklist

The Windows service usually runs as Local System. Ensure:

  • The path exists
  • System (or the service account) can read the folder
  • If delete-after-upload is on, it can also delete files
  • Antivirus is not locking files for long periods (can delay “stable”)

# Verify it works

  1. Place a small file that matches your include pattern into the folder.
  2. Wait for scan interval + stability wait (often under a minute total with defaults).
  3. Dashboard → Active Transfers should show activity.
  4. Database Explorer → file should move to Uploaded.
  5. Confirm the object appears in the S3 bucket under your prefix.

If nothing happens, see Troubleshooting.


# Providers tab

Configuration → Providers explains that enable/disable is done on the dashboard, and that connection settings live in appsettings.json. Full provider editing in the UI may still be marked “coming soon”.


# Next step

Plugin Settings →