Philip Obiora

@Tpuljak To understand the problem, we want daytona `start` and `stop` commands to display progress messages for a workspace, so when a workspace starts, it displays messages on how the...

> @Philip-21 the point is that the start and stop commands read workspace logs from their respective endpoints just as we read them when creating the workspace. > > We...

> @Philip-21 yes, but only logs relevant for that process. When starting, only the startup logs should be fetched. When stopping, only the logs that occur after the command was...

@Tpuljak please review, this is what i came up with so far

Alright, will do that

@lbrecic I've been abit occupied at work for the past days, I haven't had time to test things out .

So far i have been to implement the command `daytona target set -p "filename.json"` the configurations in the json file will be piped into the target values when creating a...

https://github.com/user-attachments/assets/29fa02cb-4d0b-497f-bc6b-b1693eaafd06 here is the docker target video this is what the json file looks Like ``` { "name": "my-docker-target" ,"options": "{ \"sockPath\": \"/var/run/docker.sock\" }" } ```

https://github.com/user-attachments/assets/99ead7ca-199e-49c6-927c-37bba233a3a3 This is the gcp-target and its JSON file ``` { "name": "my-gcp-target", "options": "{ \"remoteHostname\": \"192.168.1.100\", \"remotePassword\": \"password123\", \"remotePort\": 22, \"remoteUser\": \"myuser\", \"remotePrivateKeyPath\": \"/home/myuser/.ssh/id_rsa\" }" } ```

> @Philip-21 your PR is failing on the update CLI docs check. > > Please generate it with `./hack/generate-cli-docs.sh` and commit. CLI Documentation is out of sync! i have attended...