Mark Larsen

Hey @pascalbreuninger 😄 we had originally tried using prebuilds, but due to our large docker context (which contains all our Kotlin monorepo codebase) + the way the PrebuildHash is based...

Hey there, We're interested in this functionality as well. Our use case is that we are running `devspace deploy` inside of our CI process (a GitHub CI runner), and then...

@lizardruss thanks for the response. I gave `start_dev` / `stop_dev` a try, but I think the issue I am running into is specific to our project's setup. We have a...

@lizardruss We are using `dependencies` because we have a lot of deployments (10+) and wanted to have some separation of concerns // avoid bloating the root `devspace.yaml`. I could pull...

@lizardruss I think I might try out keeping `dev:` in the `dependencies` files (which has ports, filesyncs, commands... etc), but _also_ having a `dev:` at the root (which has *only*...

Hey @lizardruss — just reporting back to let you know that it's working now with only the port-forwards copied up to the root devspace.yaml. Thanks for all your help!