Thank you! Daytona is an automation tool that soon will support configuration files such as devcontainer or nix, both on the to-do list.
Daytona automates the creation of the development environment on any hardware, whether local or remote. It connects it to a local instance of VS Code (or to a browser if preferred), creates a VPN tunnel to the development environment, and adds a reverse proxy so you can share it as well.
Furthermore, it is acknowledged that an architecture diagram is missing, which would significantly aid in providing a clearer explanation. Efforts will be made to address this as soon as possible.
Even just this little explanation would be helpful on the daytona README. It wasn't obvious to me what exactly you meant by "creation of the development environment" ... that can mean a lot of different things that are fairly specific to each project and each developer as well.
Comments
Thank you! Daytona is an automation tool that soon will support configuration files such as devcontainer or nix, both on the to-do list.
Daytona automates the creation of the development environment on any hardware, whether local or remote. It connects it to a local instance of VS Code (or to a browser if preferred), creates a VPN tunnel to the development environment, and adds a reverse proxy so you can share it as well.
Furthermore, it is acknowledged that an architecture diagram is missing, which would significantly aid in providing a clearer explanation. Efforts will be made to address this as soon as possible.
Even just this little explanation would be helpful on the daytona README. It wasn't obvious to me what exactly you meant by "creation of the development environment" ... that can mean a lot of different things that are fairly specific to each project and each developer as well.
It does under Why Daytona https://github.com/daytonaio/daytona?tab=readme-ov-file#why-...
Or do u suggest we move this all the way up?
Thanks