|
|
@@ -1,42 +1,37 @@
|
|
|
-page_title: Repositories and images on Docker Hub
|
|
|
-page_description: Repositories and images on Docker Hub
|
|
|
+page_title: Your Repositories on Docker Hub
|
|
|
+page_description: Your Repositories on Docker Hub
|
|
|
page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, webhooks, docs, documentation
|
|
|
|
|
|
-# Repositories and images on Docker Hub
|
|
|
+# Your Hub repositories
|
|
|
|
|
|
-
|
|
|
-
|
|
|
-## Searching for repositories and images
|
|
|
-
|
|
|
-You can `search` for all the publicly available repositories and images using
|
|
|
-Docker.
|
|
|
-
|
|
|
- $ docker search ubuntu
|
|
|
+Docker Hub repositories make it possible for you to share images with co-workers,
|
|
|
+customers or the Docker community at large. If you're building your images internally,
|
|
|
+either on your own Docker daemon, or using your own Continuous integration services,
|
|
|
+you can push them to a Docker Hub repository that you add to your Docker Hub user or
|
|
|
+organization account.
|
|
|
|
|
|
-This will show you a list of the currently available repositories on the
|
|
|
-Docker Hub which match the provided keyword.
|
|
|
+Alternativly, if the source code for your Docker image is on GitHub or Bitbucket,
|
|
|
+you can use an "Automated build" repository, which is built by the Docker Hub
|
|
|
+services. See the [automated builds documentation](./builds.md) to read about
|
|
|
+the extra functionality provided by those services.
|
|
|
|
|
|
-If a repository is private it won't be listed on the repository search
|
|
|
-results. To see repository statuses, you can look at your [profile
|
|
|
-page](https://hub.docker.com) on [Docker Hub](https://hub.docker.com).
|
|
|
-
|
|
|
-## Repositories
|
|
|
+
|
|
|
|
|
|
Your Docker Hub repositories have a number of useful features.
|
|
|
|
|
|
-### Stars
|
|
|
+## Stars
|
|
|
|
|
|
Your repositories can be starred and you can star repositories in
|
|
|
return. Stars are a way to show that you like a repository. They are
|
|
|
also an easy way of bookmarking your favorites.
|
|
|
|
|
|
-### Comments
|
|
|
+## Comments
|
|
|
|
|
|
You can interact with other members of the Docker community and maintainers by
|
|
|
leaving comments on repositories. If you find any comments that are not
|
|
|
appropriate, you can flag them for review.
|
|
|
|
|
|
-### Collaborators and their role
|
|
|
+## Collaborators and their role
|
|
|
|
|
|
A collaborator is someone you want to give access to a private
|
|
|
repository. Once designated, they can `push` and `pull` to your
|
|
|
@@ -48,24 +43,9 @@ private to public.
|
|
|
> A collaborator cannot add other collaborators. Only the owner of
|
|
|
> the repository has administrative access.
|
|
|
|
|
|
-You can also collaborate on Docker Hub with organizations and groups.
|
|
|
-You can read more about that [here](accounts/).
|
|
|
-
|
|
|
-## Official Repositories
|
|
|
-
|
|
|
-The Docker Hub contains a number of [Official
|
|
|
-Repositories](http://registry.hub.docker.com/official). These are
|
|
|
-certified repositories from vendors and contributors to Docker. They
|
|
|
-contain Docker images from vendors like Canonical, Oracle, and Red Hat
|
|
|
-that you can use to build applications and services.
|
|
|
-
|
|
|
-If you use Official Repositories you know you're using a supported,
|
|
|
-optimized and up-to-date image to power your applications.
|
|
|
-
|
|
|
-> **Note:**
|
|
|
-> If you would like to contribute an Official Repository for your
|
|
|
-> organization, see [Official Repositories on Docker
|
|
|
-> Hub](/docker-hub/official_repos) for more information.
|
|
|
+You can also assign more granular collaborator rights ("Read", "Write", or "Admin")
|
|
|
+on Docker Hub by using organizations and groups. For more information
|
|
|
+see the [accounts documentation](accounts/).
|
|
|
|
|
|
## Private repositories
|
|
|
|
|
|
@@ -100,8 +80,15 @@ Hub](https://registry.hub.docker.com/plans/) plan.
|
|
|
|
|
|
## Webhooks
|
|
|
|
|
|
-You can configure webhooks for your repositories on the Repository
|
|
|
-Settings page. A webhook is called only after a successful `push` is
|
|
|
+A webhook is an HTTP call-back triggered by a specific event.
|
|
|
+You can use a Hub repository webhook to notify people, services, and other
|
|
|
+applications after a new image is pushed to your repository (this also happens
|
|
|
+for Automated builds). For example, you can trigger an automated test or
|
|
|
+deployment to happen as soon as the image is available.
|
|
|
+
|
|
|
+To get started adding webhooks, go to the desired repository in the Hub,
|
|
|
+and click "Webhooks" under the "Settings" box.
|
|
|
+A webhook is called only after a successful `push` is
|
|
|
made. The webhook calls are HTTP POST requests with a JSON payload
|
|
|
similar to the example shown below.
|
|
|
|
|
|
@@ -137,13 +124,9 @@ similar to the example shown below.
|
|
|
}
|
|
|
```
|
|
|
|
|
|
-Webhooks allow you to notify people, services and other applications of
|
|
|
-new updates to your images and repositories. To get started adding webhooks,
|
|
|
-go to the desired repository in the Hub, and click "Webhooks" under the "Settings"
|
|
|
-box.
|
|
|
+<TODO: does it tell you what tag was updated?>
|
|
|
|
|
|
-> **Note:** For testing, you can try an HTTP request tool like
|
|
|
-> [requestb.in](http://requestb.in/).
|
|
|
+For testing, you can try an HTTP request tool like [requestb.in](http://requestb.in/).
|
|
|
|
|
|
> **Note**: The Docker Hub servers are currently in the IP range
|
|
|
> `162.242.195.64 - 162.242.195.127`, so you can restrict your webhooks to
|
|
|
@@ -161,7 +144,7 @@ in your chain.
|
|
|
The first webhook in a chain will be called after a successful push. Subsequent
|
|
|
URLs will be contacted after the callback has been validated.
|
|
|
|
|
|
-#### Validating a callback
|
|
|
+### Validating a callback
|
|
|
|
|
|
In order to validate a callback in a webhook chain, you need to
|
|
|
|
|
|
@@ -195,3 +178,10 @@ The following parameters are recognized in callback data:
|
|
|
"context": "Continuous integration by Acme CI",
|
|
|
"target_url": "http://ci.acme.com/results/afd339c1c3d27"
|
|
|
}
|
|
|
+
|
|
|
+## Mark as unlisted
|
|
|
+
|
|
|
+By marking a repository as unlisted, you can create a publically pullable repository
|
|
|
+which will not be in the Hub or commandline search. This allows you to have a limited
|
|
|
+release, but does not restrict access to anyone that is told, or guesses the repository
|
|
|
+name.
|
Sven Dowideit
