Great name! waves
(not associated)
Mutagen – Cloud-based development using your local tools
31–40 of 58 posts
Re: Mutagen – Cloud-based development using your local tools
#32Looks like it handles two-way sync very well, but could it keep more than two participants in sync? I'm sort of "abusing" Syncthing to sync Docker volumes (mostly just configuration and helper scripts) across several hosts. It works well, and the only things I'm missing are file ownership preservation and low-latency "instant"-feeling sync. csync2 gets it right, but it's fragile and needs a lot of babysitting. I'm wondering if Mutagen might be a suitable alternative.
Re: Mutagen – Cloud-based development using your local tools
#33Mutagen is great (I really wish Skaffold implemented it for it's sync) and I want to point out that Jacob, the author is the project, is a really awesome and intelligent person - few people in our YC batch deserve the front-page more!
Re: Mutagen – Cloud-based development using your local tools
#34Author of Mutagen here, happy to answer any questions you might have, whether it's about its use with Docker, SSH, its historical integration into Docker Desktop, or its related Mutagen Compose[0][1] project. [0]: https://github.com/mutagen-io/mutagen-compose [1]: https://mutagen.io/documentation/orchestration/compose
Thank you for this great project! I’ve been using it for a while now and it has been rock solid and easy to use. Cheers!
Re: Mutagen – Cloud-based development using your local tools
#35We use Mutagen for Garden's hot reloading mechanism. (Garden is a dev tool for K8s and hot reloading enables users to sync changes directly to a prod like dev environment as opposed to doing a rebuild and re-deploy). It really is a fantastic piece of technology and completely transformed the whole experience (we were using good 'ol rsync before). In particular it works seamlessly across platforms. If anyone's interes…
This is a MASSIVE endorsement as far as I am concerned
I used Garden in the rsync days and it was already pretty good. The code behind Garden is some of the best TypeScript + Node I've ever seen, so if this was better and more performant than what you already had I'm sold.
Tell Jon I said hi =)
Re: Mutagen – Cloud-based development using your local tools
#36Just curious, when you develop for the Cloud where to you debug your code? In the cloud or on your work-station?
Re: Mutagen – Cloud-based development using your local tools
#37I have been using mutagen for few years. It has been a life saver.
I use it mostly to work on remote projects, mostly for development, rarely working on prod. So there I have my projects on some cloud linux instances and I work locally on windows, mostly phpstorm.
Having the webserver in the cloud and doing the heavy lifting is quite nice, especially if you work with phpstorm, which can be a resource monster for bigger projects, and working on remote projects with phpstorm built in sftp / file sync is a huge pain in the ass, really slow.
With mutagen it feels almost like I work locally. Thanks to the developer for this cool tool!
Re: Mutagen – Cloud-based development using your local tools
#38Earlier quoted context omitted.
There's no compiler here - it's a tool for bidirectionally synchronizing files (specifically code, assets, build products, etc.) and forwarding network traffic to and from remote systems. The idea behind Mutagen is to use your local tools (e.g. editor, IDE, browser, etc.) to work on remote hardware (where "remote" can mean anything you like, e.g. your local system, a Docker container (local or remote), a Raspberry Pi…
It sounds like sshfs on steroids?
with mutagen you have a 1:1 copy on your local machine and remote machine. If the connection drops, you have still all your files on eg your laptop, with sshfs your files are "gone" locally. If your connection is back again, mutagen will start the sync and upload/download files again (only changed) so there is again a 1:1 copy.
Re: Mutagen – Cloud-based development using your local tools
#39Author of Mutagen here, happy to answer any questions you might have, whether it's about its use with Docker, SSH, its historical integration into Docker Desktop, or its related Mutagen Compose[0][1] project. [0]: https://github.com/mutagen-io/mutagen-compose [1]: https://mutagen.io/documentation/orchestration/compose
Thank you for building this - it appears to solve a real problem that has been a pain in my butt for a couple of years.
What are the plans for funding the project? It looks like everything is OSS now, will there be any closed source elements in the future?
Re: Mutagen – Cloud-based development using your local tools
#40Just curious, when you develop for the Cloud where to you debug your code? In the cloud or on your work-station?
For integration tests and other code meant to run like external facing code I use my local machine for debugging. If my local machine is too slow (like running the whole integ test suite) I use a cloud VM.
For internal code or slow to build code I use a remote VM hooked up to the internal network. That allows me to build quickly and test in an integration environment.
I use a file synchronization tool like mutagen at work (for ninjas) and I use mutagen on my personal laptop for the same workflow.
I’m thinking of trying remote development from jetbrains soon though: https://www.jetbrains.com/remote-development/
I generally prefer using a remote vm for development and only using my laptop for git.
Also you can use spot VMs for development so it can be cheap to get a high CPU vm for building and debugging or a high mem VM for running data science scripts and debugging them.