Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix typo in clean-cache.md #1224

Merged
merged 1 commit into from
Mar 19, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion sections/docker/clean-cache.french.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@

Node package managers, npm & Yarn, cache the installed packages locally so that future projects which need the same libraries won't need to fetch from a remote repository. Although this duplicates the packages and consumes more storage - it pays off in a local development environment that typically keeps installing the same packages. In a Docker container this storage increase is worthless since it installs the dependency only once. By removing this cache, using a single line of code, tens of MB are shaved from the image. While doing so, ensure that it doesn't exit with non-zero code and fail the CI build because of caching issues - This can be avoided by including the --force flag.

*Please not that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*
*Please note that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*

<br/><br/>

Expand Down
2 changes: 1 addition & 1 deletion sections/docker/clean-cache.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@

Node package managers, npm & Yarn, cache the installed packages locally so that future projects which need the same libraries won't need to fetch from a remote repository. Although this duplicates the packages and consumes more storage - it pays off in a local development environment that typically keeps installing the same packages. In a Docker container this storage increase is worthless since it installs the dependency only once. By removing this cache, using a single line of code, tens of MB are shaved from the image. While doing so, ensure that it doesn't exit with non-zero code and fail the CI build because of caching issues - This can be avoided by including the --force flag.

*Please not that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*
*Please note that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*

<br/><br/>

Expand Down