mackup VS client

Also checkout Mackup.

I am using mackup to sync application preferences between devices over Dropbox. Now if any application with synced preferences is started I will get a question if given application is allowed to access Dropbox files (because it tries to access its preferences). Examples below.

Hello there! I use https://github.com/lra/mackup Not sure if its the BEST but it works well for me. * What does it do - Back ups your application settings in a safe directory (e.g. Dropbox) - Syncs your application settings among all your workstations - Restores your configuration on any fresh install in one command line

Yeah, I went through a similar process when I finally upgraded my MBP after 8 years on a 2013 MBP. In light of the transition from Intel to Apple Silicon, I decided to do some spring cleaning with a fresh install. I ended up curating my own setup/bootstrap scripts as well as using mackup to backup and sync my dotfiles and app configs.

I use Mackup which syncs a many app settings including Raycast to your choice of location.

I moved away from using a dotfiles repo a few years ago because I kept forgetting to add/commit files as I changed them.

Instead I use mackup[0] which automatically manages symlinks to your Dropbox/Drive/Share and has support for a huge amount of software by default. You can also manually add “extra” files you wish to track if you like.

[0] https://github.com/lra/mackup

Brew bundle will install fresh copies of your package list. If you have any configuration files that you want to reuse, you’d have to transfer those separately. This might help https://github.com/lra/mackup

Well, owncloud run into similar issues with their client before the functionality was rolled into Qt and it mentions APFS as well as non-utf8 linux locals so... https://github.com/owncloud/client/issues/5650 https://github.com/owncloud/client/pull/5875

Why is koofr not able to get a working sync application whereas ownloud has one that works perfectly since ages? And it is even open source, so koofr devs can look and see what they are doing wrong! https://github.com/owncloud/client

There was a delta sync implementation based on zsync that got merged in the master branch of oc10, and the $1,755k bounty was paid, see Welcome Delta Sync for ownCloud - ownCloud, the client issue, one of the central client PRs , the server side PR ... sadly that feature never made it through QA. And it crashed the client .

https://github.com/owncloud/client/issues/567#issue-13530273

I agree with you guys that systemd would be better suited for this job than cron. That being said, I didn't create this tool. I simply tried it out, saw that it solved my problem, and decided to add it to the AUR. This was more of an AUR learning exercise than anything. Ideally, nextcloud implements a proper sync client daemon as requested in https://github.com/owncloud/client/issues/2002. Then there would be no need for any of this hackery!