I don't understand. It's installed on a remote server, okay. But does it provide remote environments or local environments ? And what's an environment in this context ? A Docker compose file and a .env? Code or vim settings ? A vm à la vagrant ?
Hi, Lapdev dev here. Let me try to answer your question. It's installed on a remote server so it provides remote environments. If you use VSCode remote, then you can "open" it through VSCode remote ssh. The environment that Lapdev provides essentially is a container (other format is on the roadmap) with things pre-installed as defined in Devcontainer( https://containers.dev/ ) format.
Show HN: Lapdev, a new open-source remote dev environment management software
41–50 of 71 posts
Re: Show HN: Lapdev, a new open-source remote dev environment management software
#42I am interested in remote dev environments, but I'm not super excited about managing yet more software in the cloud. There were some headaches around the exact specifics since it wasn't designed for this, but I liked the idea of using skypilot to launch dev machines in the cloud since it has plugins to all the cloud APIs and so you don't need to manage a k8s cluster to launch a dev machine. Admittedly it worked bette…
Sorry it’s not meant to be a dig at you, but in I wish we could stop talking about the “cloud” and software running “in the cloud”. There is no cloud… it’s just software running on someone else’s computers that you don’t control. And that someone else is usually a megacorp like Microsoft or Amazon.
Re: Show HN: Lapdev, a new open-source remote dev environment management software
#43- Vagrant already supports VM or Container environments, and has a well defined system for building and distributing "base" boxes;
- Vagrant uses a Ruby file to define the environment, so it's much more powerful than a Yet Another Migraine Looming file.
Re: Show HN: Lapdev, a new open-source remote dev environment management software
#44Re: Show HN: Lapdev, a new open-source remote dev environment management software
#45Re: Show HN: Lapdev, a new open-source remote dev environment management software
#46It's always interesting to see new approaches but I don't see this replacing Vagrant for my projects any time soon: - Vagrant already supports VM or Container environments, and has a well defined system for building and distributing "base" boxes; - Vagrant uses a Ruby file to define the environment, so it's much more powerful than a Yet Another Migraine Looming file.
Re: Show HN: Lapdev, a new open-source remote dev environment management software
#47The remainder is AGPL, which many people (including myself) consider nonfree as well.
Re: Show HN: Lapdev, a new open-source remote dev environment management software
#48This isn’t open source; one of the directories is licensed under a proprietary, subscriptionware nonfree license. The remainder is AGPL, which many people (including myself) consider nonfree as well.
Re: Show HN: Lapdev, a new open-source remote dev environment management software
#49I don't understand. It's installed on a remote server, okay. But does it provide remote environments or local environments ? And what's an environment in this context ? A Docker compose file and a .env? Code or vim settings ? A vm à la vagrant ?
Re: Show HN: Lapdev, a new open-source remote dev environment management software
#50Can I connect to the environment over https? I'm looking for a good solution to use nvim from the browser on my iPad on the go.