You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docker image contains a registry of the top X crates. The way it is currently setup, the registry is rebuilt every time there is a build/deploy. That might be a bit overkill, and it is slightly annoying when working locally.
I think this is related to #37#40. If the supported crates are pinned to specific versions, we could use a hash over the supported_crates file as a cache buster. I might try to pick up the work on the stale PR when I get the time.
@ErikSchierboom I cannot reproduce this locally. When I simply run docker build . twice in a row, the second build is fully cached. Is this not a problem anymore or do I need to do something else to reproduce this?
The docker image contains a registry of the top X crates. The way it is currently setup, the registry is rebuilt every time there is a build/deploy. That might be a bit overkill, and it is slightly annoying when working locally.
One option to fix this would be to use cache buster argument, and then pass some semi-stable value to it each time the image is built (e.g. causing the registry to only be built once a day). We use this pattern in the website. See https://github.com/exercism/website/blob/main/docker/rails.Dockerfile#L4 and https://github.com/exercism/website/blob/cb1b829bbe232e94bc593946fb00cacb2ee9f6f8/.github/workflows/deploy.yml#L78
The text was updated successfully, but these errors were encountered: