Thank you
nohup /usr/bin/rclone serve ftp --addr MYIP:2121 $PWD &>/dev/null &
No configuration needed (beyond rclone's per-cloud-storage-account config (noting that serving local dirs this way does not require any cloud storage config)) and some variation of that can be added to crontab like: @reboot /usr/bin/sleep 30 && ...the above command...
Noting that $PWD can be a cloud drive identifier (part of the rclone config) so it can proxy a remote cloud service this same way. So, for example: rclone serve ftp --addr MYIP:2121 mydropbox:
assuming "mydropbox" is the locally-configured name for your rclone dropbox connection, that will serve your whole dropbox.- startup only when the network is up
- proper logging
- automatic restarts on failure
- optional protection for your ssh keys and other data if there's a breach (refer to `systemd-analyze security`)
Run:
$ systemctl --user edit --full --force rclone-ftp.service
this opens a text editor; paste these lines: [Unit]
After=network-online.target
Wants=network-online.target
[Install]
WantedBy=default.target
[Service]
ExecStart=/usr/bin/rclone --your-flags /directory
and then enable and start the service: $ systemctl --user enable --now rclone-ftpsystemd is far from perfect, and Poettering is radically anti-user. But it's the best we got and it serves us well
What does that mean?
And i've yet to see a pi-native dropbox client for doing so.
PS: i actually do sync dropbox to my main workstation but selectively do so. The lion's share of my dropbox is stuff i don't need locally so don't bother to sync it. The rclone approach gives me easy access to the whole dropbox, when needed, from anywhere in my intranet, and i can use my local file manager instead of the dropbox web interface.