|
|
|
|
|
by rcarmo
824 days ago
|
|
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 an environment. |
|
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.