That sounds quite elegant, but seems this is only possible if you work out of a single machine almost always. Perhaps it could be made into a service? As long as explicit effort is taken that there's absolute minimum extra effort as possible!
For example, to run a remote command using an inline org-mode source block:
src_sh[:dir /ssh:host:]{some command}
Or to run code using a remote Jupyter kernel within Org-mode in Emacs: #+BEGIN_SRC jupyter-julia :session /ssh:ec2:/run/user/1000/jupyter/kernel-julia-0.6.json
...
#+END_SRC
https://github.com/dzop/emacs-jupyter/blob/master/README.org...To cover the more trivial point for the non-Emacs readers: Tramp in Emacs makes it so that there's almost no difference between opening a file (C-x C-f) like this:
/home/user/some-file.txt
and like this: /ssh:some-machine:/home/user/some-file.txt
and like this, if you need superuser rights: /ssh:some-machine|sudo:some-machine:/etc/someconfig
The subsystem in Emacs called Tramp makes this almost transparent; you edit your remote files as if they were local. There are occasional kinks with path translation in corner-case situations, like local Emacs editing remote source files and trying to load them into remote REPL, but those are rare and can be configured away. Dired (directory manager in Emacs) also works transparently over Tramp, so this essentially replaces SCP and graphical SFTP tools for me. You can even run GDB remotely over Tramp, which is a nice trick.I've gotten to the point that anything important enough to keep around I basically just put in a git repo somewhere.
Logitech folio keyboard and Apple Pencil. Drawings also pushed to cloud.
Local backup to my own NAS and a S3 storage.
Works as a charm