Rclone usage guide (Stratofusion defaults)

This project standardizes when to use copy vs copyto and applies safe, performant defaults.

API Documentation

The rclone service provides interactive API documentation via Swagger UI:

• Local Development: http://localhost:3001/docs.
• Production VM: https://rclone.stratofusion.io/docs when operator access and service policy permit it.
• Legacy Fly.io recovery: the development and production Fly endpoints are intentionally stopped; do not probe them during normal operation.
• OpenAPI Spec: http://localhost:3001/openapi.json.

The Swagger UI provides:

• Complete API endpoint documentation.
• Request/response schemas.
• Interactive API testing.
• Example requests and responses.

TL;DR

• Single file → copyto (we default to --no-traverse).
• Whole folder (recursive) → copy (we default to --fast-list).
• We always include metadata preservation and progress/stats unless overridden by options.

When to use which

• copy copies directory contents recursively. Ideal for folder→folder.
• copyto accepts an explicit destination path/filename. Ideal for single file copies and renames.

Both share the same flag families (filters, progress, checks, etc.).