Support More Job Types: Copy, Move, Delete, Purge (Beyond Sync)

Feature
1

:page_facing_up: Description

RcloneView currently supports Sync and Bi-Directional Sync operations.

We’re now planning to expand to a wider range of Job Types, including:

  • :page_facing_up: Copy – One-way file duplication without deletion (coming next sprint)

  • :delivery_truck: Move – Copy then delete source (useful for organizing cloud storage)

  • :cross_mark: Delete – Remove files from a specific path or remote

  • :broom: Purge – Hard-delete entire folders (no trash, no versioning)

Each operation serves a distinct use-case and allows users more control over their file management strategy.

:hammer_and_wrench: Usage Scenarios

  • :white_check_mark: Copy

    A user wants to back up local files to both Dropbox and Google Drive — without affecting the source files.

    → Copy ensures one-way backup with zero risk of source loss.

  • :white_check_mark: Move

    A user wants to transfer processed files to cold storage (e.g., from NAS to B2).

    → Move clears up local space after cloud transfer.

  • :white_check_mark: Delete

    A user cleans up temporary logs or cache directories in a scheduled job.

    → Delete removes specific file types from a cloud path.

  • :white_check_mark: Purge

    A user wants to remove an entire backup folder from a cloud remote after archiving.

    → Purge removes all files instantly, including any leftover metadata or empty dirs.

:test_tube: Reference Behavior

  • rclone copy – preserves source, overwrites target if changed

  • rclone move – equivalent to copy + delete

  • rclone delete – deletes file(s) at target path only

  • rclone purge – aggressively deletes folder + all contents

These are standard Rclone commands, but not yet exposed in RcloneView via UI workflows.

:warning: Limitations to Note

Current Limitation Clarification
Copy is coming in the next sprint UI and logging logic being finalized
Move/Delete/Purge may require confirmation safeguards Extra UX validation is needed to prevent accidental deletion
Not all remotes support purge Rclone will fallback to recursive delete if unsupported

:date: Roadmap (Vision)

  • :white_check_mark: Add Copy as a selectable Job Type (next sprint)

  • :soon_arrow: Add Move with visual confirmation of delete-on-source

  • :wastebasket: Introduce Delete and Purge with “Dry Run” preview mode

  • :locked_with_key: Add safety toggles (e.g., “require confirmation for destructive jobs”)

  • :repeat_button: Allow batch job templates with mixed job types

:man_raising_hand: Want this feature?

Upvote this post if you want more flexible job types beyond Sync — like Copy, Move, or Purge — directly in RcloneView!

Have a specific use-case for these operations? Let us know below :backhand_index_pointing_down: