This seems to setup user and permission for backups, but not yet the actual backup functionality. According to #38 we can use sanoid/syncoid for this. I have a working setup that i could integrate into this branch. Just let me know if that is fine for you.
This seems to setup user and permission for backups, but not yet the actual backup functionality. According to #38 we can use sanoid/syncoid for this. I have a working setup that i could integrate into this branch. Just let me know if that is fine for you.
Alright, then we can start off this way and merge this so that we can start using nextcloud within the collective.
But i would like to migrate to syncoid/sanoid or restic in the near future, i will propose a starting point soon and then we can discuss what/how we want it from there.
Alright, then we can start off this way and merge this so that we can start using nextcloud within the collective.
But i would like to migrate to syncoid/sanoid or restic in the near future, i will propose a starting point soon and then we can discuss what/how we want it from there.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
part of #38
Ive added my server key for pulls for now
6a55dd26f8toe4f6cf2595This seems to setup user and permission for backups, but not yet the actual backup functionality. According to #38 we can use sanoid/syncoid for this. I have a working setup that i could integrate into this branch. Just let me know if that is fine for you.
Oh, i didnt even think about sanoid snaps
My plan was just pulling the current state every 6-12 hours or so
Alright, then we can start off this way and merge this so that we can start using nextcloud within the collective.
But i would like to migrate to syncoid/sanoid or restic in the near future, i will propose a starting point soon and then we can discuss what/how we want it from there.
e4f6cf2595to1083949c87