Is your feature request related to a problem? Please describe.
Currently, users can generate a devcontainer.json but have to manually set it up in their local environment. Integrating an automated start command for Daytona, which downloads and injects the generated devcontainer.json, will streamline the setup process for users.
Describe the solution you'd like
Add a command under the generated devcontainer.json that installs Daytona and starts a workspace with the injected devcontainer.json.
Integrate this feature to depend on the "Add New Route for Fetching Generated Devcontainer via URL Hash" #8.
The command should be a custom bash script that users can simply copy and run to initialize the environment in Daytona.
Describe alternatives you've considered
Manually outlining the steps in the documentation, but this is prone to user error and less convenient.
Providing separate scripts, which can fragment the user experience and complicate the process.
Additional context
The command should:
Handle the installation of Daytona if it's not already installed.
Create a new Daytona workspace.
Fetch the generated devcontainer.json using the new route with a URL hash.
Pipe the fetched devcontainer.json into the workspace initialization process.
Is your feature request related to a problem? Please describe. Currently, users can generate a
devcontainer.json
but have to manually set it up in their local environment. Integrating an automated start command for Daytona, which downloads and injects the generateddevcontainer.json
, will streamline the setup process for users.Describe the solution you'd like
devcontainer.json
that installs Daytona and starts a workspace with the injecteddevcontainer.json
.Describe alternatives you've considered
Additional context The command should:
devcontainer.json
using the new route with a URL hash.devcontainer.json
into the workspace initialization process.Example command: