toz/MediLog
9
51
Fork
You've already forked MediLog
3

FeatureRequest: Allow Synchonisation between devices #459

Open
opened 2024年12月18日 11:54:40 +01:00 by toz · 1 comment
Owner
Copy link

ich habe Medilog auf einem Handy und einem Tablet installiert. Meist benutze ich das Handy. Am Tablet sind die grafischen Darstellungen übersichtlicher.
Jetzt möchte ich die Daten von Medilog auf beiden Geräte synchron halten.

Das mache ich schon für die Daten der Anwendung Obsidian mittels der Cloud von MEGA unter Zuhilfenahme der App Foldersync. Hier werden Verzeichnisse und deren Inhalte automatisch oder auch manuell synchronisiert.
Da ich nicht herausgefunden habe in welchem Verzeichnis MediLog die Daten speichert ist mir das nicht gelungen.
Wie muss ich vorgehen?

ich habe Medilog auf einem Handy und einem Tablet installiert. Meist benutze ich das Handy. Am Tablet sind die grafischen Darstellungen übersichtlicher. Jetzt möchte ich die Daten von Medilog auf beiden Geräte synchron halten. Das mache ich schon für die Daten der Anwendung Obsidian mittels der Cloud von MEGA unter Zuhilfenahme der App Foldersync. Hier werden Verzeichnisse und deren Inhalte automatisch oder auch manuell synchronisiert. Da ich nicht herausgefunden habe in welchem Verzeichnis MediLog die Daten speichert ist mir das nicht gelungen. Wie muss ich vorgehen?
Author
Owner
Copy link

Unfortunately this isn't trivial.
MediLog stores it's data inside the apps data folder. Which, by design, only the app can access.
If you got a routed device root level apps (backup, sync) could get access to it though.

The next hurdle is that MediLog's datafile is encrypted. So even if you managed to sync the file between devices you'd have to use the same key on all devices to be able to open the file.
Right now this key is a random string which get's created during app installation and there is no easy way to display and change the key. This is a security feature because, even if someone get's access to the data, it's of no value without the key.

I use tablet and phone myself and have been thinking the possibility sync the two. But I shied away from the effort this will take.
Not a trivial task if I want to get this right (secure)

Unfortunately this isn't trivial. MediLog stores it's data inside the apps data folder. Which, by design, only the app can access. If you got a routed device root level apps (backup, sync) could get access to it though. The next hurdle is that MediLog's datafile is encrypted. So even if you managed to sync the file between devices you'd have to use the same key on all devices to be able to open the file. Right now this key is a random string which get's created during app installation and there is no easy way to display and change the key. This is a security feature because, even if someone get's access to the data, it's of no value without the key. I use tablet and phone myself and have been thinking the possibility sync the two. But I shied away from the effort this will take. Not a trivial task if I want to get this right (secure)
Sign in to join this conversation.
No Branch/Tag specified
main
3.6.0
3.3.8
master
v3.3.2
v3.2.7
v3.2.5
v3.2.1
v3.2.0
v3.1.2
v3.1.0
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v2.7.4
v3.0.3
v3.0.1
v3.0.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.3
v2.6.2
v2.6.0
v2.5.11
v2.5.10
v2.5.9
v2.5.8
v2.5.7
v2.5.6
v2.5.5
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.4.8
v2.4.7
v2.4.6
v2.4.5
v2.4.4
v2.4.3
v2.4.2
v2.4.0
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v3.7.1
v3.6.5
v3.6.4
v3.6.3
v3.6.2
v3.6.0
v3.5.1
v3.5.0
v3.4.1
v3.4.0
v3.3.11
v3.3.10
v3.3.9
v3.3.8
v3.3.7
v3.3.6
v3.3.5
v3.3.4
v3.3.3
v3.3.2
v3.2.7
v3.2.6
v3.2.5
v3.2.4
v3.2.3
v3.2.1
v3.2.0
v3.1.2
v3.1.1
v3.1.0
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v3.0.3
v3.0.2
v3.0.1
v3.0.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.3
v2.6.2
v2.6.1
v2.6.0
v2.5.11
v2.5.10
v2.5.9
v2.5.8
v2.5.7
v2.5.6
v2.5.5
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.4.8
v2.4.7
v2.4.6
v2.4.5
v2.4.3
v2.4.2
v2.4.1
v2.4.0
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v2.3.0
v2.2.5
v2.2.4
v2.2.3
v2.2.1
v2.2.2
v2.2.0
v2.1.2
v2.1.1
v2.1.0
v2.0.6
v2.0.5
v2.0.1
v3.7.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
toz/MediLog#459
Reference in a new issue
toz/MediLog
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?