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
{{ message }}
This repository has been archived by the owner on May 21, 2021. It is now read-only.
For repositories with Dockerfiles that we publish on Docker Hub, it could be helpful to use the same repository name on both websites. When looking at one of our repos that uses newsdev/rails as a base, my first instinct is to look for that Dockerfile at github.com/newsdev/rails.
While it's certainly worth it to learn about Docker Hub so we all understand where to look for non-NYT Dockerfiles, it might reduce confusion if we either:
renamed this repo newsdev/rails, or
renamed the docker hub repository as newsdev/docker-rails
The text was updated successfully, but these errors were encountered:
To me, the reason for this naming convention is to indicate that the code contained in the repository is a Docker representation of the project, not the project itself. In this case, we haven't forked Rails but rather established a Docker image for using rails. On Docker Hub, using the docker prefix is redundant.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For repositories with Dockerfiles that we publish on Docker Hub, it could be helpful to use the same repository name on both websites. When looking at one of our repos that uses
newsdev/rails
as a base, my first instinct is to look for that Dockerfile atgithub.com/newsdev/rails
.While it's certainly worth it to learn about Docker Hub so we all understand where to look for non-NYT Dockerfiles, it might reduce confusion if we either:
newsdev/rails
, ornewsdev/docker-rails
The text was updated successfully, but these errors were encountered: