Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Lapdev, a new open-source remote dev environment management software

github.com

Post reply on HN
Print view View original

61–70 of 71 posts

Re: Show HN: Lapdev, a new open-source remote dev environment management software

#61

Post by giobox »

shantnutiwari wrote: post #60

Requirements: Postgres This immediately killed it for me. I need to install a Postgres server just to try out a tool? And if I recommend it to my team, do we need to run and maintain a Postgres instance? OP- you are creating too much work for me. And don’t ask me to use your hosted version, the easiest solution is to use Vs code devcontainers

Running a Postgres container from docker compose (or whatever method you want) is up there with easiest one-and-done 2 minute development setup tasks I can think of.

Re: Show HN: Lapdev, a new open-source remote dev environment management software

#62

Post by garyrob »

lyang2821 wrote: post #9
johnchristopher wrote: post #6

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.

This is totally new to me, so let me ask an extremely basic question.

The way I'm hearing what you're saying is: Lapdev sets up a remote environment that I access with my terminal via SSH, and do editing in using something like VSCode running on my local machine, accessing the remote environment with something like VSCode's Remote-SSH extension.

So by using lapped I can replicate the remote environment I normally access through those things easily on remote servers and cloud services? Is that right?

Re: Show HN: Lapdev, a new open-source remote dev environment management software

#63

Post by lyang2821 »

garyrob wrote: post #62
lyang2821 wrote: post #9

Earlier quoted context omitted.

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.

This is totally new to me, so let me ask an extremely basic question. The way I'm hearing what you're saying is: Lapdev sets up a remote environment that I access with my terminal via SSH, and do editing in using something like VSCode running on my local machine, accessing the remote environment with something like VSCode's Remote-SSH extension. So by using lapped I can replicate the remote environment I normally acc…

Yes that's correct.

To start with, I would suggest you to try VSCode Remote out with your own Linux box if you've got one, just to get a feel of "remote" development. You might like it or might not.

Re: Show HN: Lapdev, a new open-source remote dev environment management software

#64

Post by rcarmo »

shantnutiwari wrote: post #58
rcarmo wrote: post #57

Nice, but with a Proxmox setup I can clone an existing VM/container (and there are already dozens of templates), point VSCode at it, and I’m done. What does this add, really? It’s not automation (I can automate a couple of clicks in Proxmox), it’s not resource management (Proxmox handles storage, etc.). Is it developer identity? Because that’s the only thing I’d need a (relatively simple) script to deploy SSH keys to…

Do you work for Promox? Because it looks like a very corporaty over engineered solution. Lap dev looks like a much simpler tool

It looks like a much simpler, incomplete tool.

But you could have gotten your answer by just checking my profile. But no. I just use Proxmox to manage all of my infra: https://taoofmac.com/space/blog/2023/12/17/2000

Don’t assume people have business motives for stating technical facts - and don’t downvote because they ask pointed questions. There are good reasons for pointed questions.

Re: Show HN: Lapdev, a new open-source remote dev environment management software

#65

Post by tristan957 »

sneak wrote: post #47

This 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.

AGPL is Free Software according to the FSF, so I'm not sure who at all would contest that it isn't.

Re: Show HN: Lapdev, a new open-source remote dev environment management software

#66

Post by lyang2821 »

rcarmo wrote: post #57

Nice, but with a Proxmox setup I can clone an existing VM/container (and there are already dozens of templates), point VSCode at it, and I’m done. What does this add, really? It’s not automation (I can automate a couple of clicks in Proxmox), it’s not resource management (Proxmox handles storage, etc.). Is it developer identity? Because that’s the only thing I’d need a (relatively simple) script to deploy SSH keys to…

A few things Lapdev can probably do better:

Devcontainer spec is probably more developer centric than Proxmox templates

I would guess with your Proxmox setup in a team setup, you'd need to assign a hostname/ip for different developers, where with Lapdev you have a single point of access.

Lapdev can proxy http traffic to the workspace containers with authentication, which makes it easy to preview things with security.

Re: Show HN: Lapdev, a new open-source remote dev environment management software

#67

Post by rcarmo »

lyang2821 wrote: post #66
rcarmo wrote: post #57

Nice, but with a Proxmox setup I can clone an existing VM/container (and there are already dozens of templates), point VSCode at it, and I’m done. What does this add, really? It’s not automation (I can automate a couple of clicks in Proxmox), it’s not resource management (Proxmox handles storage, etc.). Is it developer identity? Because that’s the only thing I’d need a (relatively simple) script to deploy SSH keys to…

A few things Lapdev can probably do better: Devcontainer spec is probably more developer centric than Proxmox templates I would guess with your Proxmox setup in a team setup, you'd need to assign a hostname/ip for different developers, where with Lapdev you have a single point of access. Lapdev can proxy http traffic to the workspace containers with authentication, which makes it easy to preview things with security.

Thanks, that is the kind of useful answer I was looking for. But I can share VM hosts and IPs among developers, that's trivial. The auth piece, not so much.

Re: Show HN: Lapdev, a new open-source remote dev environment management software

#69

Post by sneak »

tristan957 wrote: post #65
sneak wrote: post #47

This 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.

AGPL is Free Software according to the FSF, so I'm not sure who at all would contest that it isn't.

https://news.ycombinator.com/item?id=30495737

https://news.ycombinator.com/item?id=30496091

The FSF are anticapitalist zealots that think the ability to run a SaaS business using free software is a "loophole" in the GPL that needs to be closed. The AGPL is an unenforceable mess that's trying to be an EULA (but can't be).

Re: Show HN: Lapdev, a new open-source remote dev environment management software

#70

Post by tristan957 »

sneak wrote: post #69
tristan957 wrote: post #65

Earlier quoted context omitted.

AGPL is Free Software according to the FSF, so I'm not sure who at all would contest that it isn't.

https://news.ycombinator.com/item?id=30495737 https://news.ycombinator.com/item?id=30496091 The FSF are anticapitalist zealots that think the ability to run a SaaS business using free software is a "loophole" in the GPL that needs to be closed. The AGPL is an unenforceable mess that's trying to be an EULA (but can't be).

How is freedom anticapitalist?
Post reply on HN