Skip to content

Commit

Permalink
Wording nitpicks / de-duplication
Browse files Browse the repository at this point in the history
  • Loading branch information
jayaddison committed Sep 17, 2022
1 parent 60ad691 commit ed7ef80
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,9 +49,9 @@ GROCY_MODE=demo docker-compose up

Container images published by this repository currently have a human-readable format that begins with the Grocy PHP application version number and includes an incremental integer suffix to indicate the image-build revision.

When a container image release is published (for example, one tagged as `v3.3.1-6` using this version scheme), a "prefix-only" tag is also attached to the release (`v3.3.1`, to continue the example). This allows users who are comfortable with a version of Grocy to update to the latest container for that version without having to discover a specific version number.
When a container image is published (for example, one tagged as `v3.3.1-6` using this version scheme), a "prefix-only" tag is also attached to the release (`v3.3.1`, to continue the example). This allows users who are comfortable with a version of Grocy to update to the latest container for that version without having to discover a specific version number.

Each published image should have a corresponding `git` tag. This is to allow anyone running, inspecting, or planning to upgrade containers to retrieve and compare the build instructions for published containers (although this does not, in itself, provide a complete view of the contents of the relevant containers -- something that can vary depending on the time and environment in which they are built).
Each published image also has a corresponding `git` tag. This is to allow anyone running, inspecting, or planning to upgrade containers to retrieve and compare the build instructions for published containers (although this does not, in itself, provide a complete view of the contents of the relevant containers -- something that can vary depending on the time and environment in which they are built).

Revisions are necessary to allow the structure of the container to change. For example, we may upgrade the operating system components of the container to improve performance, functionality and security. This doesn't require any change to the Grocy application code, so the prefix remains the same.

Expand Down

0 comments on commit ed7ef80

Please sign in to comment.