As @leetnewb@beehaw.org mentioned, I’m not sure either is what you’re necessarily looking for.
As @leetnewb@beehaw.org mentioned, I’m not sure either is what you’re necessarily looking for.
Yeah, I know, “RTFM.”
Sorry, I didn’t mean to come across in a condescending way, if that’s how it read. I’ve only ever used rclone
for Google Drive, and its been quite a while since I’ve personally set it up, as I no longer daily-drive linux (outside of WSL).
A “remote” presumably means a remote folder/share/whatever in the cloud, in this case on Proton Drive, yes?
Yes, following the documentation, you would run rclone config
, then answer as follows:
n
proton
protondrive
username@protonmail.com
y
to enter your password; then enter your password twice as prompted<Enter>
to skipy
This should create a proton-drive remote called “proton”, which you can reference in further rclone
commands. For example:
# Check if out of sync
rclone check 'proton:' ~/proton 2>&1 | grep --quiet ' ERROR :'
# Sync local/remote
rclone sync 'proton:' ~/proton
If I want to set Rclone to automaticlly sync, say, my home folder to Proton Drive, Rclone has to run as a service on startup for this to work.
In the past, I wrote a script to handle the check/sync job, and scheduled it to run with crontab
, as it was easier for me to work with. Here’s an example of the script to run rclone
using the proton:
remote defined above:
#!/usr/bin/env bash
# Ensure connected to the internet
ping -c 1 8.8.8.8 |& grep --quiet --ignore-case "unreachable" && exit 0
# If in-sync, skip sync procedure
rclone check 'proton:' "${HOME}" |& grep --quiet ' ERROR :' || exit 0
# Run sync operation
rclone --quiet sync 'proton:' "${HOME}"
If scheduling with crontab
, running crontab -e
will open your user’s schedule in the $VISUAL
, $EDITOR
or /usr/bin/editor
text editor. Here, you could enter something like
0,30 * * * * /home/your_user_name/proton_sync.sh
Which would try to sync once every 30 minutes (crontab-guru).
you can use systemd to set up rclone as a system or user service
This is also an option, assuming your system is using systemd
; which most distributions have moved to – you typically have to go out of your way to avoid it. I also don’t have much experience in writing my own service/timer files; but it looks like systemd-run
may have you covered as well (source):
# Run every 30 minutes
systemd-run --user --on-calendar '*:0/30' /home/your_user_name/proton-sync.sh
While I know writing config files and working with the terminal can be intimidating (it was for me in the beginning, anyway); I’d really recommend against running random ‘scripts’ you find online unless you either 100% trust the source, or can read/understand what they are doing. I have personally been caught-out recently from a trusted source doing jank shit in their scripts, which I didn’t notice until reading through them…and Linux Admin/DevOps is my day job…
Looks like they have an official tutorial.
I’ve also heard good things about bitwig, though it’s not FOSS, annoyingly.
I’m the sysadmin (and transitioning to DevOps) at work, but the DBs are 100% in control of our two devs (one of which being the head of IT).
Apparently we’re going to hire a third Dev, who will moonlight as our DBA – oh, and for 30K/yr.
I’m sure this will go well.
Had the displeasure of using the modern EA app the other week – completely refuses to launch my copy of Jedi: Fallen Order in the foreground after a single play-session (Steam -> EA just doesn’t work for some people).
At work we’re using Bitwarden for the group benefits; though I still have KeePassXC running to simplify SSH keys (Windows, naturally) for native & PuTTY.
Personally, I use KeePassXC & KeePass android (currently); and sync’d through GDrive; which is good enough for my needs.