Lsyncd VS Mosh

I've discovered inotify-tools and lsyncd as options and POC proves that it's possible to detect filesystem changes on a shared emptydir in a pod. Now it's just time to truly prove it out.

Try lsnyncd .

https://github.com/lsyncd/lsyncd might work for you.

Here is the github link, will explain how to use it: https://github.com/lsyncd/lsyncd

I found lsyncd on my research, I'll take a look at rclone, also thanks for the bitwarden link I wanted to do it as well.

If so, bidirectional file sync can be implemented using lsyncd on top of rsync https://github.com/axkibe/lsyncd

To sync files between NAS hosts/network locations, you can use rsync. It allows synchronizing files and folders, building a 1:1 data structure. https://man7.org/linux/man-pages/man1/rsync.1.html If you need bidirectional file sync, you can use lsyncd on top of rsync https://github.com/axkibe/lsyncd

Actually, you can use lsyncd to configure automatic bidirectional file synchronization between your workstations. https://github.com/axkibe/lsyncd

To sync files between two disks, you can use rsync. It allows synchronizing files and folders, building a 1:1 data structure. On top of rsync, Lsyncd allows configuring automatic bidirectional file synchronization if needed. https://github.com/axkibe/lsyncd If you need a GUI-based tool, you can use FreeFileSync, Syncthing, MSP360. They also allow you to perform differential sync between two drives. https://www.vmwareblog.org/single-cloud-enough-secure-backups-5-cool-cross-cloud-solutions-consider/

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.