Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Add synchronization between multiple ROMM instance #1322

Open
y-streibel-uiris opened this issue Nov 28, 2024 · 0 comments
Open

[Feature] Add synchronization between multiple ROMM instance #1322

y-streibel-uiris opened this issue Nov 28, 2024 · 0 comments
Labels
feature New feature or request

Comments

@y-streibel-uiris
Copy link

Is your feature request related to a problem? Please describe.
I am using ROMM in a container, and I would like to share the container's content with another ROMM instance hosted remotely. Currently, there is no straightforward way to synchronize content between multiple instances.

Describe the solution you'd like
I propose adding a feature in the configuration panel to enable seamless sharing and synchronization of content across multiple ROMM instances. This functionality could include options for automatic or manual synchronization, as well as settings for managing conflicts and bandwidth usage.

Describe alternatives you've considered
One alternative is using rsync to manually synchronize the content between ROMM instances. However, this requires additional setup, scripting, and maintenance, which makes it less convenient than a built-in feature.

Additional context
This feature would greatly improve the usability of ROMM for users running multiple instances, especially in distributed environments. It could be useful for teams or individuals needing consistent access to shared content.

@y-streibel-uiris y-streibel-uiris added the feature New feature or request label Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant