[johnchristopher]

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 ?

[lyang2821]

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.

[garyrob]

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?

[lyang2821]

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.

[johnchristopher]

Ah, I see. Thanks for the explanation !

I haven't yet made the jump to remote/cloud development, I don't have a clear mental picture of how the pieces fit.

[rovr138]

Remote environment with a thin client that can interface with it. Client is local, but it all ends up running remotely.

[arcastroe]

Can Labdev spin up a codeserver instance to access vscode from the browser without having to have vscode locally installed?

[nkko]

We've been focused on developing remote-first solutions for years (Codeanywhere). However, we ultimately concluded that, with Daytona, local will always be the primary environment, with remote serving to enhance specific needs like scaling and offloading is the right way to go. Therefore with Dayton you can spin your dev env on different targets and providers.