platform self-update on dockerfile will be cached? about ddev-platformsh HOT 7 CLOSED

hooks:
  post-start:
    - exec: 'platform self:update -qy || true'

probably best

from ddev-platformsh.

Thanks, and glad you're using some parts. I didn't quite understand what update notification you were talking about?

from ddev-platformsh.

Oh you're saying that the platform tool inside is wanting the self-update when you use it. Yeah, it only gets done the one time during build, but the build cache in Docker then doesn't try it again :(

IMO it would be best to disable that.

from ddev-platformsh.

We could do the self-update in start.sh, or implement your auto-add-to-start.sh and put it there. Seems like a sad thing to do, but these things always pestering about getting an update are a bit annoying.

from ddev-platformsh.

the auto add to start could be the hook, you could add a config.platformsh.yml with a post-start hook, although you'll have to add it to the git repo as well as a post_install action as it will otherwise be ignored.

from ddev-platformsh.

hooks:
  post-start:
    - exec: 'platform self:update -qy'

I added this to my project.

from ddev-platformsh.

Hello
I agree, best would probably be to do this during post-start like @hanoii is suggesting.
Anyway, this will soon change with the Platform CLI v4 as we'll distribute it in a different way (apt, brew...)

from ddev-platformsh.