Fabian Kramm

@leventogut thanks for creating this issue! Yes makes sense, I think we can add this

@sgreene570 thanks for creating this issue! Yes we should be able to use something similar to our backend solution.

@joshuamanns thanks for reporting this issue! The problem seems to be that you first exec into the container and then it will be replaced by the dev configuration. Would reordering...

Hey @joshuamanns ! I see, with DevSpace v6.1.0 you can do that via: ``` dev: web-server: labelSelector: app.kubernetes.io/component: web-server app.kubernetes.io/name: frontend devImage: ghcr.io/loft-sh/devspace-containers/typescript:17-alpine sync: - path: .:. disableDownload: true excludeFile:...

@joshuamanns but isn't that what you want? Or do you want to start the container first and then run the init script?

@DanArlowski thanks for creating this issue! Yes, I see your point, but I believe this does not always work, however we might want to add an option to load the...

@blaisertm thanks for reporting this! I'm thing about adding support to target all pods that match a selector to the dev config, so that syncing to multiple pods would work...

@alexissellier they were a couple of problems combined with Kubernetes and docker/distribution, but I believe we can revisit that and check if its still necessary

@tobalsgithub thanks for reporting this issue! Mhh, I believe this is caused because DevSpace initially resolves the variables, but then when the profile was applied is not updating those anymore...

@hariprasadiit thanks for creating this issue! We will take a look and see if we can fix the problem with the next version