Client-Server Architecture

[dlommm]

What's your idea?

I must say the application is fantastic I have some suggestions that may be way to involved to make changes too but I figured I would mention it anyway. In line with being able to pull the cloud saves from Steam recommended by TheFrenchGhosty Storing the files into a centralized location ex. docker and being able to use rsync or something similar to ensure the files are synced between agents would be fantastic. Also possibly download and create all of the file directories from the manifest even if not in use and store them into the docker volume and as an agent comes online and there is a game that needs to be uploaded it auto uploads it into the correct location within the docker volume. With a Webgui for the centralized server to be able to check agent status and sync errors etc.

Benefits for running Client Server Architecture

1. Centralized Server:

• Runs as a Docker container for easy deployment and centralized management
• Acts as the central hub for all save file synchronization
• Maintains a database of registered agents and their configurations
• Handles path mapping between different operating systems and usernames (Ex. C:\Users\JohnDoe* & C:\Users\JaneDoe* )
• Manages file versioning and conflict resolution
• API for agent communication
• Webui sync conflicts user action delete / move / version
• Multi User support ability to support different user game saves. (Ex User 1 game saves to user 1 directory / User2 game saves to user 2 directory)

2. Client Agents:

• Run as background services/daemons on user machines
• Monitor file system changes in game save directories
• Handle automatic upload of changed files or when new agent is added and computer already has game saves
• Manage download and placement of saves from other machines
• Account for platform-specific path differences
• Run on startup and maintain persistent connection