MoonHome: Remote Development Environment
moonhome.io
MoonHome: Remote Development Environment
1–10 of 97 posts
Re: MoonHome: Remote Development Environment
#2Re: MoonHome: Remote Development Environment
#3Re: MoonHome: Remote Development Environment
#4How can I independently verify the accuracy of this claim?
Re: MoonHome: Remote Development Environment
#5I've been doing a lot of this lately. I got the cheapest Macbook Air and SSH into my machine at the office. Tmux attach and go! Lag is never an issue for me. I could get used to this.
Re: MoonHome: Remote Development Environment
#6Ease of use counts for something, of course, but the market for this is developers that probably either know how to use DigitalOcean or don't know what SSH is and will stick with Codespaces or its alternatives. Static IPs are also interesting, but given the use case for me is being able to nuke my dev environment just like I nuke a git branch, as long as it's accessible somewhere I don't know how much that matters.
(I'm not trying to be down on this at all, I don't know where I'd start with launching a VPS provider. But I think there's something missing from this landing page.)
Re: MoonHome: Remote Development Environment
#7What kind of security is sitting around my source code? How would I guarantee when I stopped using the service that a copy wasn't kept somewhere?
Is it backed up / a snapshot done regularly? What kind of control do I have over those snapshots, the timing of them and deleting them if I decide to stop using the service?
Re: MoonHome: Remote Development Environment
#8Re: MoonHome: Remote Development Environment
#9> When not used, Moonhome is disconnected from the network for maximum protection. When running, it sits safely behind the built-in network firewall.
So does this mean when I ssh in it proxies and forwards the connection to the actual host which is otherwise unexposed to the public internet? Seems like a reasonable thing to do, I guess.
> We update system images every night, so you don’t have to worry about any of that.
Okay, this seems fine at first glance but it’s really unclear. If I have Go installed, for example, will that be updated automatically or are my own development tools fully under my control and up to me to update? Also, what is the underlying distribution behind all of this? Is it just running ‘apt upgrade’ on a cron job or are you doing something else?
Is it a giant stack of Docker containers with some persistent storage?
Is this open source? Can I run a single command on a North American Digital Ocean droplet and run this closer to home? I don’t see much point in putting my dev env on the other side of an ocean.
Re: MoonHome: Remote Development Environment
#10"We do not have access to your data" How can I independently verify the accuracy of this claim?