Private
Public Access
Migration Client hinzugefügt
@@ -0,0 +1,54 @@
|
||||
# Migration Client
|
||||
|
||||
The migration client is the source-side helper for guided migrations from existing Romexis installations.
|
||||
|
||||
Current direction:
|
||||
|
||||
```text
|
||||
Windows client first
|
||||
Future: evaluate C# for broader platform support
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Responsibilities
|
||||
|
||||
The client should help with:
|
||||
|
||||
- detecting local Romexis installation paths
|
||||
- detecting SQL Server connection settings
|
||||
- creating a database backup
|
||||
- detecting Romexis image and ergo data directories
|
||||
- creating a migration job through the migration service API
|
||||
- uploading data through rclone/SFTP
|
||||
- calling API endpoints to advance workflow state
|
||||
- displaying progress and logs
|
||||
|
||||
---
|
||||
|
||||
## Why rclone?
|
||||
|
||||
rclone is suitable for large migrations because it supports:
|
||||
|
||||
- SFTP
|
||||
- progress output
|
||||
- retries
|
||||
- resumable workflows
|
||||
- directory synchronization
|
||||
- configurable transfers/checkers
|
||||
|
||||
---
|
||||
|
||||
## Python vs C# Direction
|
||||
|
||||
The initial client is Python-based because it is fast to develop and easy to integrate with existing scripts.
|
||||
|
||||
For future macOS support, C# may become the better long-term option because it can provide:
|
||||
|
||||
- native Windows build
|
||||
- possible macOS build
|
||||
- stronger GUI options
|
||||
- easier single-binary packaging
|
||||
- better long-term maintainability for a desktop migration client
|
||||
|
||||
The README should keep this as an architectural direction, not as a completed feature.
|
||||
Reference in New Issue
Block a user