Consider using git or another SCM instead. You don't need a centralized server, you can push/pull between any two machines with ssh (or a handful of other protocols). Encrypted end to end. Supports branches, useful for stuff like dotfiles on different machines. You don't need commit messages, just make an alias to add all changes and commit with and empty message. You have a full history, can revert back to any state, inspect any old version, diff versions, etc. There's git clients for mobile. Free as in beer and freedom. Check-summed. Puts you in control of when to sync, supports offline. Future-proof, acquisition-proof, VC-proof. Familiar.
My one-liner Linux Dropbox client
91–100 of 165 posts
Re: My one-liner Linux Dropbox client
#92rclone is great, but I find syncing manually in intervals to be ideal since you get to see what is changing from your destination/remote. I use CrashPlan Pro to back up everything automatically, and then a few times a week I'll run rclone on my data drive so that I can see what has changed.
Re: My one-liner Linux Dropbox client
#93Consider using git or another SCM instead. You don't need a centralized server, you can push/pull between any two machines with ssh (or a handful of other protocols). Encrypted end to end. Supports branches, useful for stuff like dotfiles on different machines. You don't need commit messages, just make an alias to add all changes and commit with and empty message. You have a full history, can revert back to any state…
I do this, but 90% of the time I forget to pull on the other machine and have to deal with conflicts.
Re: My one-liner Linux Dropbox client
#94Earlier quoted context omitted.
I've used Syncthing and it's excellent. But for me, the lack of a mobile app was a dealbreaker. Even though it's not open source, I switched to Resilio Sync[1] (formerly known as btsync). It ticks all the other boxes, and just works amazingly well. I want to support them so I sprang for the $20 one time Pro license which adds selective sync and a few other nice features. [1] https://www.resilio.com/individuals/
Syncthing does have a mobile app https://f-droid.org/packages/com.nutomic.syncthingandroid/
For Android yes, but the GP is likely using iOS where no such client seems to exist.
Re: My one-liner Linux Dropbox client
#95Earlier quoted context omitted.
In principle I agree with you, and many could argue the the app is broken. But in all fairness it is not so easy. Then there are lots of little details and corner cases where filesystems that implement a POSIX fs have slightly different semantics. This is important for example when dealing with sync'ing files to disk/backend. Encryption is another problem. Error handling. See for an example the annoying details here:…
Encryption is another problem. I thought the whole point of an encrypting filesystem was that applications using it would not need to care about such things? Unless you're going below the FS abstraction and actually accessing blocks of the device directly, it shouldn't matter.
With LUKS it doesn't matter. But not all encryption methods are like that. That was just really an example of potential differences. In fact, when this (Dropbox dropping non ext4 support) happened the problem that triggered this was encryption related IIRC.
Re: My one-liner Linux Dropbox client
#96Earlier quoted context omitted.
I too was a bit surprised by that statement. But according to Dropbox, full disk encryption should work fine. ”If you received a notification on Linux and you are running ext4, it may be because you are also running ecryptfs. ecrypfts is not supported. However, we support full disk encryption systems, such as LUKS for Linux users.” Source: https://www.dropboxforum.com/t5/Error-messages/Dropbox-clien...
Perfect, thank you for the -forum- link! :)
De nada :)
Re: My one-liner Linux Dropbox client
#97Consider using git or another SCM instead. You don't need a centralized server, you can push/pull between any two machines with ssh (or a handful of other protocols). Encrypted end to end. Supports branches, useful for stuff like dotfiles on different machines. You don't need commit messages, just make an alias to add all changes and commit with and empty message. You have a full history, can revert back to any state…
I do this, but 90% of the time I forget to pull on the other machine and have to deal with conflicts.
Check out Sparkleshare.
Re: My one-liner Linux Dropbox client
#98Earlier quoted context omitted.
Just sync an encrypted image if your threat model includes disgruntled employees motivated enough to mess with your account.
Could be problematic if the image is huge.
Anyone have experience with Boxcryptor? Haven't tried it since a few years ago (https://www.boxcryptor.com/en/)
Re: My one-liner Linux Dropbox client
#99I setup Syncthing [1] to do the same for my vimwiki folder. It was surprisingly easy, and doesn't require any external storage services. And it can even automatically sync files without internet, over the local network. [1] https://syncthing.net/
I'm sorry if this is a stupid question:
If I have my desktop and my laptop, both using syncthing, does one (my desktop) need to always be online for me to sync files from my other device (my laptop)?
I'd love to use something else besides Dropbox, but it's convenient that Dropbox works as the middleman that is always operating.
Re: My one-liner Linux Dropbox client
#100Consider using git or another SCM instead. You don't need a centralized server, you can push/pull between any two machines with ssh (or a handful of other protocols). Encrypted end to end. Supports branches, useful for stuff like dotfiles on different machines. You don't need commit messages, just make an alias to add all changes and commit with and empty message. You have a full history, can revert back to any state…
I do this, but 90% of the time I forget to pull on the other machine and have to deal with conflicts.
Yes, you'd have to automate the pull for this to work, and then you'd have a way to notify on conflicts so that they are resolved ASAP.
Come to think of it, Dropbox isn't really so great at the notification aspect of this either. It creates a 'conflicted' file but there is no notification that I'm aware of. I have to remind myself to periodically check for conflicts.