Fast file synchronization and network forwarding for remote development
1–10 of 64 posts
Re: Fast file synchronization and network forwarding for remote development
#2This sounds like my dream tool - I've always loved how quickly and well local tools work and remote environments cut into that good experience significantly. For me to be productive, I really need an instant feedback loop where tools work fast and I can immediately experience the result of some small piece of work.
Has anyone tried this for a real-world project and can share feedback?
Re: Fast file synchronization and network forwarding for remote development
#3Mutagen also has a Docker extension. Really easy to set up. I installed it recently after searching for ways to speed up Docker on an Apple M1. It did work in my case.
Re: Fast file synchronization and network forwarding for remote development
#4In past I have used lsyncd to develop locally and synchronize the changes to a remote host over ssh where the code base was compiled. This worked nicely even over GPRS network connection with a speed like 30 Kbit/s. As the link had high latency it was important to use emacs shell for the remote connection. This way I could type the command locally and send it to the remote host when pressing enter.
Re: Fast file synchronization and network forwarding for remote development
#5This sounds like my dream tool - I've always loved how quickly and well local tools work and remote environments cut into that good experience significantly. For me to be productive, I really need an instant feedback loop where tools work fast and I can immediately experience the result of some small piece of work. Has anyone tried this for a real-world project and can share feedback?
I generally find systems that aren't setup to let you dev locally and require a dev in prod or remote also don't let you work in tiny tight feedback loops either. I generally focus making it work everywhere the same instead of fast sync but that's just me. Well and the systems I have control over.
Re: Fast file synchronization and network forwarding for remote development
#6This sounds like my dream tool - I've always loved how quickly and well local tools work and remote environments cut into that good experience significantly. For me to be productive, I really need an instant feedback loop where tools work fast and I can immediately experience the result of some small piece of work. Has anyone tried this for a real-world project and can share feedback?
I find that VS Code's Remote-* extensions work well. I'm currently writing a Terraform provider on a remote Linux box using Remote-SSH and everything feels local. Compilation, etc happens on the remote and if I were serving requests it's dead easy to forward a port.
Re: Fast file synchronization and network forwarding for remote development
#7How's that compared to sshfs (wth cache/kernel_cache enabled) ? I've used it few times where I had need to dev like that and it was generally just fine for just editing a file, where performance tanked was doing a lot of file I/O at once (say updating git repo)
Re: Fast file synchronization and network forwarding for remote development
#8I’d like to know more about the theory behind the synchronisation — how the syncing is known to be safe and non-destructive.
Re: Fast file synchronization and network forwarding for remote development
#9Mutagen author here — happy to answer any questions about Mutagen[0], its Docker Desktop extension[1], its Compose integration[2], or anything else!
[0]: https://mutagen.io/ [1]: https://mutagen.io/documentation/docker-desktop-extension [2]: https://mutagen.io/documentation/orchestration/compose
Re: Fast file synchronization and network forwarding for remote development
#10This sounds useful. But one question that comes to mind right away:
Does Mutagen handle the case where “local tools” (running on a completely different architecture than the remote) still need to “know” about include/header/library/etc. files from the remote machine in order to provide working “intelligence” capabilities?
It’s one thing to efficiently sync “code”, but it’s another to make local tools fully-aware of the remote system’s header files, libraries, etc.