Murena cloud synchronization behavior - how does it work?

Using /e/OS murenacloud
1

In the thread Murena cloud syncing in one or two directions? there has been a discussion about how the Murena cloud synchro actually behaves. In November 2023 I have posted there to summarize a few of the issues:

  1. At least in one of my own cases the synchro behaved in an unexpected way (at the start of my post)
  2. The official support guide is not detailed enough and outdated
  3. Listed a number of file operation cases which are high prio and less high prio to get a documentation about (points 1 to 6 in my post)

@Manoj was kind enough to say he would share the questions with the infra team and ask them to update the guide. Then the thread got auto-locked (which is why I had to post this now as a new topic - I have to say I hate auto-locking unresolved threads in forums), but without an answer and also it looks like the guide was not updated.

Could you please check in with them again whether they can document the sync (or no sync) behavior in these cases in either a forum post or update the guide accordingly? I believe it should not be hard for the team responsible for setting up and maintaining the system to answer how it works.

2

There have been updates to the Murena Workspace - earlier called Murena Cloud. The infra team is working on updating the documentation. Will put in a reminder.

Update: Shared the update with the infra team. They will be reviewing the current document and updating it ASAP.

1 Like
3

the thread is very long, closing and summarizing isn’t the worst. Auto-lock has up- and downsides.

eDrive has it’s own logic, tough the nextcloud client itself moved towards offering 2way sync via a setting with an early development version in August, for folks who specifically look for that feature - Internal 2way sync by tobiasKaminsky · Pull Request #13294 · nextcloud/android · GitHub

4

New in latest NC Hub 9

Two**-way sync for Android** :calling:

With two-way sync enabled for a folder, files added or updated on device automatically sync to your cloud, and the other way round. Currently, only internal folders created in Nextcloud are supported.

1 Like
5

May I remember that the dissymetric way that we have now does have supporters, me for instance, because it allows to repatriate pics automatically on my computer, then to delete them on the server (maintaining a reasonable volume there) while not risking to mirror the deletion on the computer nor re-uploading from the phone…
So, the current behavior looks perfectly sane for my use, and even : I suspect it was designed this way on purpose…
I hope it won’t evolve in a way that’d trash my process, which would drive me instantly out of Murena Cloud (I also have a NextBox that I could use exactly the same way)
TIA,
Hervé

6

Just posting here to keep the thread open. It would really be pointless to have to open yet another thread about the same topic just because of automatic forum behavior.

The question is still open, but I’m refraining from pinging anyone from the team due to the current murena.io issues. Firstly, I assume the infrastructure team is currently busy with fixing the issues. Secondly, after fixing them the cloud synchro may behave differently, so documentation now may be pointless.

It’s a bit unfortunate though that we’ve asked for documentation for over a year at this point and didn’t get info from the infra team.

7

Indeed, it’s quite worrying that murena.io be still unsolved after such a large delay.
I’m very fearful that this cloud info may surface, and by contagion hit dangerously the whole /e/ ecosystem, while it’s working and updating perfectly and for years on…