-
Notifications
You must be signed in to change notification settings - Fork 22
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
update readme with steps to create new release image #12
Conversation
c8ce0f9
to
bd415bb
Compare
Signed-off-by: Roshan Khatri <[email protected]>
bd415bb
to
2634e4b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, the README.md looks fine if everything succeeds in first attempt. But otherwise I don't understand the details, so asked a bunch of questions on PR.
@@ -3,3 +3,12 @@ This Project is the Git repo of the [Valkey "Official Image"](https://hub.docker | |||
The Project is now maintained by [the Valkey Community](https://github.com/valkey-io/valkey/) | |||
and it was forked from https://github.com/docker-library/redis. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want to keep this reference? The other project is still an active project and probably under the same license as Redis.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is maintained by dicker community and is under BSD, we can keep it.
@@ -3,3 +3,12 @@ This Project is the Git repo of the [Valkey "Official Image"](https://hub.docker | |||
The Project is now maintained by [the Valkey Community](https://github.com/valkey-io/valkey/) | |||
and it was forked from https://github.com/docker-library/redis. | |||
|
|||
## How to build and publish new version Docker Image? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, when to build and publish new version docker image?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we have a new version release from valkey
README.md
Outdated
@@ -3,3 +3,12 @@ This Project is the Git repo of the [Valkey "Official Image"](https://hub.docker | |||
The Project is now maintained by [the Valkey Community](https://github.com/valkey-io/valkey/) | |||
and it was forked from https://github.com/docker-library/redis. | |||
|
|||
## How to build and publish new version Docker Image? | |||
*Pre-requisites: Fork this repo, create a private dockerhup repo and setup the Github secrets to access the private dockerhup repo.* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
README.md
Outdated
@@ -3,3 +3,12 @@ This Project is the Git repo of the [Valkey "Official Image"](https://hub.docker | |||
The Project is now maintained by [the Valkey Community](https://github.com/valkey-io/valkey/) | |||
and it was forked from https://github.com/docker-library/redis. | |||
|
|||
## How to build and publish new version Docker Image? | |||
*Pre-requisites: Fork this repo, create a private dockerhup repo and setup the Github secrets to access the private dockerhup repo.* | |||
1. Validate if the metadata for the new version is updated at https://github.com/valkey-io/valkey-hashes/blob/main/README |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if the hashes file is not updated, but I want to release new docker image? May be explain the background behind each step?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am working on automating this process, so once a new release is pushed the hashes will be updated
README.md
Outdated
## How to build and publish new version Docker Image? | ||
*Pre-requisites: Fork this repo, create a private dockerhup repo and setup the Github secrets to access the private dockerhup repo.* | ||
1. Validate if the metadata for the new version is updated at https://github.com/valkey-io/valkey-hashes/blob/main/README | ||
2. If its a new major version create a new dir. For example `7.2`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
create a new dir where? Does it matter if I create it in /tmp? Is 7.2 a hyperlink?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the valkey-container directory. I will link the example PR
README.md
Outdated
*Pre-requisites: Fork this repo, create a private dockerhup repo and setup the Github secrets to access the private dockerhup repo.* | ||
1. Validate if the metadata for the new version is updated at https://github.com/valkey-io/valkey-hashes/blob/main/README | ||
2. If its a new major version create a new dir. For example `7.2`. | ||
3. Run the `update.sh` script locally, which will update the `versions.json` and also populate the Dockerfiles for the new versions in the repective directories. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of this sh files have 0 documentation or comments. May be elaborate on what is happening? Why is it needed?
README.md
Outdated
1. Validate if the metadata for the new version is updated at https://github.com/valkey-io/valkey-hashes/blob/main/README | ||
2. If its a new major version create a new dir. For example `7.2`. | ||
3. Run the `update.sh` script locally, which will update the `versions.json` and also populate the Dockerfiles for the new versions in the repective directories. | ||
4. Validate if the version and the info is populated correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how do I validate this?
README.md
Outdated
4. Validate if the version and the info is populated correctly. | ||
5. See if all the tests pass on your fork and the your private docker up has been updated. | ||
5. Publish a PR with these changes. For example: https://github.com/valkey-io/valkey-container/pull/8 | ||
6. Once the PR is merged, Sit back, relax and enjoy looking at your creation getting publish to the official Docker hub page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should explain a little more here. What goes into getting this published to official docker hub page? Are there any failures to look out for?
Also there is a typo - "getting published".
temp.sh
Outdated
@@ -0,0 +1,10 @@ | |||
#!/bin/bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this file for? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was a temp file where I was testing some stuff
Signed-off-by: Roshan Khatri <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Update readme with steps to create new release image
When to build and publish new Docker Image?
After a new major, minor or patch version of Valkey is released on https://github.com/valkey-io/valkey.
How to build and publish new version Docker Image?
Pre-requisites: Fork this repo, create a private dockerhup repo and setup the Github secrets to access the private dockerhup repo.
valkey-container
repo. For example7.2
.update.sh
script locally, which will update theversions.json
and also populate the Dockerfiles for the new versions in the respective directories. Running theupdate.sh
file, executes theversions.sh
which updates theversions.json
file with the required metadata from https://github.com/valkey-io/valkey-hashes/blob/main/README. Onceversions.json
is updated,apply-templates.sh
is executed which updates Docker files for all the versions directories in the repo (For example,7.2
).dockerhub-description.md
with the updated tags in your private docker hub and the Docker files links.