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

Automatic local backup #122

Open
aaannndddyyy opened this issue Dec 8, 2023 · 5 comments
Open

Automatic local backup #122

aaannndddyyy opened this issue Dec 8, 2023 · 5 comments

Comments

@aaannndddyyy
Copy link

A tree is a lot of work and may also mean a lot to its owner. But some of use are lazy and don't do manual backups, and some of us are not fond of sending personal data into the cloud.
But local backups are useless if the phone on which the backups are is lost.

Therefore, I think family gem should make daily local or cloud backups (maybe asked on first run whether cloud or local), unless the user disables them in the settings

Backups older than a week should then be deleted automatically

@jer194
Copy link

jer194 commented Dec 8, 2023

I personally don't maintain trees via FamilyGem (or any app).
I have more trust in my laptop, and I find it much easier to maintain the trees there.
(I'm using geneweb for that).

@aaannndddyyy
Copy link
Author

aaannndddyyy commented Dec 8, 2023

Thanks. I'll look into it
Previously, I had started on laptop with gramps.

However , not carrying it around , I never had the trees at hand when with family members who could contribute, and ended up having stuff on paper, and after a while I didn't continue there anymore.

@jer194
Copy link

jer194 commented Dec 9, 2023

One possible solution for this situation has been proposed in issue #72.

@michelesalvador
Copy link
Owner

Yes, I agree that creating our trees is a lot of work, and losing them could be a disaster.

The automatic Google backup system is already implemented.
And one can always save each tree as a ZIP backup.
But maybe this is not enough.

@jer194 Sorry, I don't understand how #72 could be related.

@jer194
Copy link

jer194 commented Feb 10, 2024

@jer194 Sorry, I don't understand how #72 could be related.

I think I tried to address this side comment:

However , not carrying it around , I never had the trees at hand when with family members who could contribute, and ended up having stuff on paper, and after a while I didn't continue there anymore.

With #72, one could avoid carrying around paper.
Instead, changes to FamilyGem trees added while not at home could be backported to the real trees when back at home.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants