@arela/uploader 0.3.0 → 1.0.0

package/README.md

@@ -2,6 +2,14 @@
 
 CLI tool to upload files and directories to Arela API or Supabase Storage with automatic file processing, detection, and organization.
 
+## ✨ What's New in v0.4.0
+
+- 🏢 **Simplified Multi-Tenant API**: Only 3 targets: `default`, `agencia`, `cliente`
+- 🔀 **Cross-Tenant Mode**: Read from one API, write to another with `--source-api` and `--target-api`
+- ⚙️ **Dynamic Client Config**: Switch clients by updating `.env` - no code changes needed!
+- 👁️ **Enhanced Watch Mode**: Full cross-tenant support in automatic processing pipeline
+- ⚡ **Optimized Connections**: HTTP Agent with connection pooling for high performance
+
 ## 🚀 OPTIMIZED 4-PHASE WORKFLOW
 
 **New in v0.2.0**: The tool now supports an optimized 4-phase workflow designed for maximum performance when processing large file collections:
@@ -84,13 +92,76 @@ arela --upload-by-rfc        # Phase 4: Upload by RFC
 - 📋 **Upload files by specific RFC values**
 - 🔍 **Propagate arela_path from pedimento documents to related files**
 - ⚡ **4-Phase optimized workflow for maximum performance**
-- 👁️ **Watch Mode** ⭐ NEW - Monitor directories for changes and upload automatically
+- 👁️ **Watch Mode** - Monitor directories for changes and upload automatically
   - Multiple watch strategies (batch, individual, full-structure)
+  - **Multi-tenant and cross-tenant support** ⭐ NEW
   - Debounce and polling support
   - Auto-processing pipeline
   - Dry-run mode for testing
   - Pattern-based file ignoring
 
+## 🏢 Multi-Tenant API Support
+
+Connect to different API instances: **default**, **agencia**, or **cliente**.
+
+```bash
+# Upload to client API
+arela upload --api cliente --upload-by-rfc
+
+# Collect stats on agencia API
+arela stats --api agencia
+
+# Watch mode with specific API target
+arela watch --api cliente
+```
+
+### Cross-Tenant Mode
+
+Process files from one tenant and upload to another:
+
+```bash
+# Read data from agencia, upload files to client
+arela watch --source-api agencia --target-api cliente
+
+# Same for upload command
+arela upload --source-api agencia --target-api cliente --upload-by-rfc
+```
+
+**How Cross-Tenant Works:**
+| Phase | Description | API Used |
+|-------|-------------|----------|
+| Phase 1 | Stats Collection | `--source-api` |
+| Phase 2 | PDF Detection | `--source-api` |
+| Phase 3 | Path Propagation | `--source-api` |
+| Phase 4 | File Upload | `--target-api` |
+
+### Available API Targets
+
+Only 3 API targets are available: `default`, `agencia`, `cliente`
+
+Configure in your `.env` file:
+
+```env
+# Default API (--api default or no flag)
+ARELA_API_URL=http://localhost:3010
+ARELA_API_TOKEN=your_token
+
+# Agencia API (--api agencia)
+ARELA_API_AGENCIA_URL=http://localhost:4012
+ARELA_API_AGENCIA_TOKEN=your_agencia_token
+
+# Cliente API (--api cliente)
+# Configure the URL/Token for the specific client you need
+ARELA_API_CLIENTE_URL=http://localhost:4014
+ARELA_API_CLIENTE_TOKEN=your_cliente_token
+
+# Examples for different clients:
+# Cliente AUM9207011CA: ARELA_API_CLIENTE_URL=http://localhost:4014
+# Cliente KTJ931117P55: ARELA_API_CLIENTE_URL=http://localhost:4013
+```
+
+> 💡 **Tip**: To switch between clients, just update `ARELA_API_CLIENTE_URL` and `ARELA_API_CLIENTE_TOKEN` in your `.env` file. No code changes needed!
+
 ## Installation
 
 ```bash
@@ -170,6 +241,12 @@ arela detect --propagate-arela-path
 # Watch directories for changes with automatic upload
 arela watch --directories "/path/to/watch1,/path/to/watch2"
 
+# Watch with specific API target (single tenant)
+arela watch --api cliente
+
+# Watch with cross-tenant mode (read from agencia, upload to client)
+arela watch --source-api agencia --target-api cliente
+
 # Watch with custom upload strategy (default: batch)
 arela watch --directories "/path/to/watch" --strategy individual
 arela watch --directories "/path/to/watch" --strategy full-structure
@@ -198,6 +275,11 @@ arela watch --directories "/path/to/watch" --verbose
 - `individual`: Uploads each file immediately as it changes
 - `full-structure`: Preserves directory structure during upload
 
+**Multi-Tenant Options:**
+- `--api <target>`: Use a single API for all operations
+- `--source-api <target>`: API for reading/processing (phases 1-3)
+- `--target-api <target>`: API for uploading (phase 4)
+
 #### 5. **query** - Query database for file status
 ```bash
 # Show files ready for upload
@@ -263,6 +345,9 @@ arela --upload-by-rfc                 # Same as: arela upload --upload-by-rfc
   - `batch`: Groups files and uploads periodically
   - `individual`: Uploads each file immediately
   - `full-structure`: Preserves directory structure
+- `--api <target>`: Use a single API target for all operations
+- `--source-api <target>`: API for reading/processing (phases 1-3)
+- `--target-api <target>`: API for uploading (phase 4)
 - `--debounce <ms>`: Debounce delay in milliseconds (default: 1000)
 - `-b, --batch-size <size>`: Batch size for uploads (default: 10)
 - `--poll <ms>`: Use polling instead of native file system events (interval in ms)
@@ -278,10 +363,19 @@ arela --upload-by-rfc                 # Same as: arela upload --upload-by-rfc
 Create a `.env` file in your project root:
 
 ```env
-# For API Mode (recommended)
+# Default API (--api default or no flag)
 ARELA_API_URL=http://localhost:3010
 ARELA_API_TOKEN=your_api_token
 
+# Agencia API (--api agencia)
+ARELA_API_AGENCIA_URL=http://localhost:4012
+ARELA_API_AGENCIA_TOKEN=your_agencia_token
+
+# Cliente API (--api cliente)
+# Configure for the specific client you need
+ARELA_API_CLIENTE_URL=http://localhost:4014
+ARELA_API_CLIENTE_TOKEN=your_cliente_token
+
 # For Direct Supabase Mode (fallback)
 SUPABASE_URL=your_supabase_url
 SUPABASE_KEY=your_supabase_anon_key
@@ -294,18 +388,26 @@ UPLOAD_SOURCES=folder1|folder2|file.pdf
 # RFC-based Upload Configuration
 # Pipe-separated list of RFCs to upload files for
 UPLOAD_RFCS=MMJ0810145N1|ABC1234567XY|DEF9876543ZZ
+
+# Watch Mode Configuration (JSON format)
+WATCH_DIRECTORY_CONFIGS={"../../Documents/2022":"palco","../../Documents/2023":"palco"}
 ```
 
 **Environment Variable Details:**
 
-- `ARELA_API_URL`: Base URL for the Arela API service
-- `ARELA_API_TOKEN`: Authentication token for API access
+- `ARELA_API_URL`: Base URL for default API service
+- `ARELA_API_AGENCIA_URL`: URL for agencia API
+- `ARELA_API_CLIENTE_URL`: URL for client API (configure per client)
+- `ARELA_API_TOKEN`: Authentication token for default API
+- `ARELA_API_AGENCIA_TOKEN`: Token for agencia API
+- `ARELA_API_CLIENTE_TOKEN`: Token for client API
 - `SUPABASE_URL`: Your Supabase project URL
 - `SUPABASE_KEY`: Supabase anonymous key for direct uploads
 - `SUPABASE_BUCKET`: Target bucket name in Supabase Storage
 - `UPLOAD_BASE_PATH`: Root directory containing files to upload
 - `UPLOAD_SOURCES`: Pipe-separated list of folders/files to process
 - `UPLOAD_RFCS`: Pipe-separated list of RFC values for targeted uploads
+- `WATCH_DIRECTORY_CONFIGS`: JSON mapping directories to folder structures
 
 ## RFC-Based File Upload
 
@@ -510,7 +612,25 @@ The tool maintains comprehensive logs both locally and remotely:
 
 ## Version History
 
-**v2.0.0** - Latest Release
+**v0.4.0** - Current Release 🆕
+- ✨ **Simplified Multi-Tenant API**: Only 3 targets: `default`, `agencia`, `cliente`
+- ✨ **Cross-Tenant Mode**: Read from one API, upload to another
+- ✨ **Dynamic Client Config**: Change client by updating `.env` (no code changes)
+- ✨ New `--api` flag for single API target
+- ✨ New `--source-api` flag for source API (phases 1-3)
+- ✨ New `--target-api` flag for target API (phase 4)
+- ✨ `WATCH_DIRECTORY_CONFIGS` environment variable for watch mode
+- 🔧 Enhanced pipeline routing for cross-tenant operations
+- 📝 Simplified documentation for multi-tenant configuration
+
+**v0.3.0** - Watch Mode Release
+- ✨ Added watch command with chokidar integration
+- ✨ Automatic 4-step pipeline (stats → detect → propagate → upload)
+- ✨ Multiple upload strategies (batch, individual, full-structure)
+- ✨ Configurable debounce and polling options
+- 🔧 Signal handling for graceful shutdown
+
+**v0.2.0** - Pipeline Automation
 - ✨ Added smart year/pedimento auto-detection from file paths
 - ✨ Custom folder structure support with `--folder-structure` option
 - ✨ Client path tracking with `--client-path` option
@@ -522,6 +642,11 @@ The tool maintains comprehensive logs both locally and remotely:
 - 📝 Comprehensive logging with SANITIZED status
 - 🔧 Memory optimization for large file processing
 
+**v0.1.0** - Initial Release
+- 📦 Basic upload functionality
+- 🔌 API and Supabase direct mode support
+- 📂 RFC-based file upload
+
 ## Troubleshooting
 
 **Connection Issues:**