Russell Centanni

Hello! Thanks for reaching out. `autoReload` is replaced by the `run_watch` pipeline function. Here's an example of adding a command that uses `run_watch` based on your current configuration: ```yaml commands:...

We have this [example](https://github.com/loft-sh/devspace/tree/main/examples/redeploy-instead-of-hot-reload), but I agree that showing a practical usage in the docs would be an improvement. The command approach should work with the older config format, however...

@BirknerAlex Thanks for reporting this. It seems the readiness / liveness probes are not being removed. Could you provide more details of your `devspace.yaml` configuration? Typically if you're using the...

@BirknerAlex @ComaVN I'm looking into this deeper and was wondering if either of you have tried the [delay container start](https://devspace.sh/docs/configuration/dev/connections/file-sync#delay-container-start) example with the the readiness / liveness probes in place?

@BirknerAlex [waitInitialSync: false](https://devspace.sh/docs/configuration/dev/connections/file-sync#wait-for-initial-sync) may be the missing configuration that will help with this.

@madhavajay Apologies for the slow response. There is `devspace init` support for docker-compose, but it's intended as a one time conversion from `docker-compose.yaml` to `devspace.yaml` and should deploy to any...

@soggycactus I think the variable wound up being named `DEVSPACE_INJECT_REMOTE` instead of `DEVSPACE_INJECT_LOCAL`. Can you give that a try?

@Naveen-oops Thanks for submitting this request! I came up with an example using `commands` that may give you some ideas. If it doesn't suit your needs, then lets continue discussing,...

@MaxSchambach I was trying to figure out what that pattern is supposed to match.. but it appears it may have been a typo that made its way into the wild....

Ah, thank you. Helps if I read the whole thread. This will take some additional debugging, since these patterns are matched by a 3rd party library, and its not clear...