@@ -51,19 +51,19 @@ pages:

 # User Guide:

 - ['userguide/index.md', 'User Guide', 'The Docker User Guide' ]

-- ['userguide/dockerhub.md', 'User Guide', 'Getting Started with Docker Hub' ]

+- ['userguide/dockerio.md', 'User Guide', 'Getting Started with Docker.io' ]

 - ['userguide/dockerizing.md', 'User Guide', 'Dockerizing Applications' ]

 - ['userguide/usingdocker.md', 'User Guide', 'Working with Containers' ]

 - ['userguide/dockerimages.md', 'User Guide', 'Working with Docker Images' ]

 - ['userguide/dockerlinks.md', 'User Guide', 'Linking containers together' ]

 - ['userguide/dockervolumes.md', 'User Guide', 'Managing data in containers' ]

-- ['userguide/dockerrepos.md', 'User Guide', 'Working with Docker Hub' ]

+- ['userguide/dockerrepos.md', 'User Guide', 'Working with Docker.io' ]

-# Docker Hub docs:

-- ['docker-hub/index.md', 'Docker Hub', 'Docker Hub' ]

-- ['docker-hub/accounts.md', 'Docker Hub', 'Accounts']

-- ['docker-hub/repos.md', 'Docker Hub', 'Repositories']

-- ['docker-hub/builds.md', 'Docker Hub', 'Automated Builds']

+# Docker.io docs:

+- ['docker-io/index.md', 'Docker.io', 'Docker.io' ]

+- ['docker-io/accounts.md', 'Docker.io', 'Accounts']

+- ['docker-io/repos.md', 'Docker.io', 'Repositories']

+- ['docker-io/builds.md', 'Docker.io', 'Automated Builds']

 # Examples:

 - ['examples/index.md', '**HIDDEN**']

@@ -99,7 +99,7 @@ pages:

 - ['faq.md', 'Reference', 'FAQ']

 - ['reference/run.md', 'Reference', 'Run Reference']

 - ['reference/api/index.md', '**HIDDEN**']

-- ['reference/api/docker-io_api.md', 'Reference', 'Docker Hub API']

+- ['reference/api/docker-io_api.md', 'Reference', 'Docker.io API']

 - ['reference/api/registry_api.md', 'Reference', 'Docker Registry API']

 - ['reference/api/registry_index_spec.md', 'Reference', 'Registry & Index Spec']

 - ['reference/api/docker_remote_api.md', 'Reference', 'Docker Remote API']

@@ -18,8 +18,7 @@

     { "Condition": { "KeyPrefixEquals": "use/working_with_links_names/" }, "Redirect": { "HostName": "$BUCKET", "ReplaceKeyPrefixWith": "userguide/dockerlinks/" } },

     { "Condition": { "KeyPrefixEquals": "use/workingwithrepository/" }, "Redirect": { "HostName": "$BUCKET", "ReplaceKeyPrefixWith": "userguide/dockerrepos/" } },

     { "Condition": { "KeyPrefixEquals": "use/port_redirection" }, "Redirect": { "HostName": "$BUCKET", "ReplaceKeyPrefixWith": "userguide/dockerlinks/" } },

-    { "Condition": { "KeyPrefixEquals": "use/" }, "Redirect": { "HostName": "$BUCKET", "ReplaceKeyPrefixWith": "examples/" } },

-    { "Condition": { "KeyPrefixEquals": "docker-io/" }, "Redirect": { "HostName": "$BUCKET", "ReplaceKeyPrefixWith": "docker-hub/" } }

+    { "Condition": { "KeyPrefixEquals": "use/" }, "Redirect": { "HostName": "$BUCKET", "ReplaceKeyPrefixWith": "examples/" } }

   ]

 }

@@ -26,8 +26,8 @@ for installation instructions.

     $ sudo docker pull ubuntu

 This will find the `ubuntu` image by name on

-[*Docker Hub*](/userguide/dockerrepos/#find-public-images-on-docker-hub)

-and download it from [Docker Hub](https://hub.docker.com) to a local

+[*Docker.io*](/userguide/dockerrepos/#find-public-images-on-dockerio)

+and download it from [Docker.io](https://index.docker.io) to a local

 image cache.

 > **Note**:

deleted file mode 100644

@@ -1,31 +0,0 @@

-page_title: Accounts on Docker Hub

-page_description: Docker Hub accounts

-page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, documentation

-

-# Accounts on Docker Hub

-

-## Docker Hub Accounts

-

-You can `search` for Docker images and `pull` them from [Docker Hub](https://hub.docker.com)

-without signing in or even having an account. However, in order to `push` images,

-leave comments or to *star* a repository, you are going to need a [Docker Hub](https://hub.docker.com) account.

-

-### Registration for a Docker Hub Account

-

-You can get a [Docker Hub](https://hub.docker.com) account by

-[signing up for one here](https://hub.docker.com/account/signup/). A valid

-email address is required to register, which you will need to verify for

-account activation.

-

-### Email activation process

-

-You need to have at least one verified email address to be able to use your

-[Docker Hub](https://hub.docker.com) account. If you can't find the validation email,

-you can request another by visiting the [Resend Email Confirmation](

-https://hub.docker.com/account/resend-email-confirmation/) page.

-

-### Password reset process

-

-If you can't access your account for some reason, you can reset your password

-from the [*Password Reset*](https://hub.docker.com/account/forgot-password/)

-page.

deleted file mode 100644

@@ -1,209 +0,0 @@

-page_title: Automated Builds on Docker Hub

-page_description: Docker Hub Automated Builds

-page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, documentation, trusted, builds, trusted builds, automated builds

-# Automated Builds on Docker Hub

-

-## Automated Builds

-

-*Automated Builds* is a special feature allowing you to specify a source

-repository with a `Dockerfile` to be built by the

-[Docker Hub](https://hub.docker.com) build clusters. The system will

-clone your repository and build the `Dockerfile` using the repository as

-the context. The resulting image will then be uploaded to the registry

-and marked as an *Automated Build*.

-

-Automated Builds have a number of advantages. For example, users of

-*your* Automated Build can be certain that the resulting image was built

-exactly how it claims to be.

-

-Furthermore, the `Dockerfile` will be available to anyone browsing your repository

-on the registry. Another advantage of the Automated Builds feature is the automated

-builds. This makes sure that your repository is always up to date.

-

-Automated Builds are supported for both public and private repositories

-on both [GitHub](http://github.com) and

-[BitBucket](https://bitbucket.org/).

-

-### Setting up Automated Builds with GitHub

-

-In order to setup an Automated Build, you need to first link your

-[Docker Hub](https://hub.docker.com) account with a GitHub one. This

-will allow the registry to see your repositories.

-

-> *Note:* 

-> We currently request access for *read* and *write* since

-> [Docker Hub](https://hub.docker.com) needs to setup a GitHub service

-> hook. Although nothing else is done with your account, this is how

-> GitHub manages permissions, sorry!

-

-Click on the [Automated Builds

-tab](https://registry.hub.docker.com/builds/) to get started and then

-select [+ Add New](https://registry.hub.docker.com/builds/add/).

-

-Select the [GitHub service](https://registry.hub.docker.com/associate/github/).

-

-Then follow the instructions to authorize and link your GitHub account

-to Docker Hub.

-

-#### Creating an Automated Build

-

-You can [create an Automated Build](https://registry.hub.docker.com/builds/github/select/)

-from any of your public or private GitHub repositories with a `Dockerfile`.

-

-#### GitHub organizations

-

-GitHub organizations appear once your membership to that organization is

-made public on GitHub. To verify, you can look at the members tab for your

-organization on GitHub.

-

-#### GitHub service hooks

-

-You can follow the below steps to configure the GitHub service hooks for your

-Automated Build:

-

-<table class="table table-bordered">

-  <thead>

-    <tr>

-      <th>Step</th>

-      <th>Screenshot</th>

-      <th>Description</th>

-    </tr>

-  </thead>

-  <tbody>

-    <tr>

-      <td>1.</td>

-      <td><img src="https://d207aa93qlcgug.cloudfront.net/0.8/img/github_settings.png"></td>

-      <td>Login to Github.com, and visit your Repository page. Click on the repository "Settings" link. You will need admin rights to the repository in order to do this. So if you don't have admin rights, you will need to ask someone who does.</td>

-    </tr>

-    <tr>

-      <td>2.</td>

-      <td><img src="https://d207aa93qlcgug.cloudfront.net/0.8/img/github_service_hooks.png" alt="Service Hooks"></td>

-      <td>Click on the "Service Hooks" link</td></tr><tr><td>3.</td><td><img src="https://d207aa93qlcgug.cloudfront.net/0.8/img/github_docker_service_hook.png" alt="Find the service hook labeled Docker"></td><td>Find the service hook labeled "Docker" and click on it.</td></tr><tr><td>4.</td><td><img src="https://d207aa93qlcgug.cloudfront.net/0.8/img/github_service_hook_docker_activate.png" alt="Activate Service Hooks"></td>

-      <td>Click on the "Active" checkbox and then the "Update settings" button, to save changes.</td>

-    </tr>

-  </tbody>

-</table>

-

-### Setting up Automated Builds with BitBucket

-

-In order to setup an Automated Build, you need to first link your

-[Docker Hub](https://hub.docker.com) account with a BitBucket one. This

-will allow the registry to see your repositories.

-

-Click on the [Automated Builds tab](https://registry.hub.docker.com/builds/) to

-get started and then select [+ Add

-New](https://registry.hub.docker.com/builds/add/).

-

-Select the [BitBucket

-service](https://registry.hub.docker.com/associate/bitbucket/).

-

-Then follow the instructions to authorize and link your BitBucket account

-to Docker Hub.

-

-#### Creating an Automated Build

-

-<<<<<<< HEAD:docs/sources/docker-io/builds.md

-You can [create an Automated

-Build](https://index.docker.io/builds/bitbucket/select/) from any of

-your public or private BitBucket repositories with a `Dockerfile`.

-=======

-You can [create a Trusted

-Build](https://registry.hub.docker.com/builds/bitbucket/select/)

-from any of your public or private BitBucket repositories with a

-`Dockerfile`.

->>>>>>> Initial links for Docker Hub rename:docs/sources/docker-hub/builds.md

-

-### The Dockerfile and Automated Builds

-

-During the build process, we copy the contents of your `Dockerfile`. We also

-add it to the [Docker Hub](https://hub.docker.com) for the Docker community

-to see on the repository page.

-

-### README.md

-

-If you have a `README.md` file in your repository, we will use that as the

-repository's full description.

-

-> **Warning:**

-> If you change the full description after a build, it will be

-> rewritten the next time the Automated Build has been built. To make changes,

-> modify the README.md from the Git repository. We will look for a README.md

-> in the same directory as your `Dockerfile`.

-

-### Build triggers

-

-If you need another way to trigger your Automated Builds outside of GitHub

-or BitBucket, you can setup a build trigger. When you turn on the build

-trigger for an Automated Build, it will give you a URL to which you can

-send POST requests. This will trigger the Automated Build process, which

-is similar to GitHub webhooks.

-

-Build Triggers are available under the Settings tab of each Automated Build.

-

-> **Note:** 

-> You can only trigger one build at a time and no more than one

-> every five minutes. If you have a build already pending, or if you already

-> recently submitted a build request, those requests *will be ignored*.

-> You can find the logs of last 10 triggers on the settings page to verify

-> if everything is working correctly.

-

-### Webhooks

-

-Also available for Automated Builds are Webhooks. Webhooks can be called

-after a successful repository push is made.

-

-The webhook call will generate a HTTP POST with the following JSON

-payload:

-

-```

-{

-   "push_data":{

-      "pushed_at":1385141110,

-      "images":[

-         "imagehash1",

-         "imagehash2",

-         "imagehash3"

-      ],

-      "pusher":"username"

-   },

-   "repository":{

-      "status":"Active",

-      "description":"my docker repo that does cool things",

-      "is_automated":false,

-      "full_description":"This is my full description",

-      "repo_url":"https://registry.hub.docker.com/u/username/reponame/",

-      "owner":"username",

-      "is_official":false,

-      "is_private":false,

-      "name":"reponame",

-      "namespace":"username",

-      "star_count":1,

-      "comment_count":1,

-      "date_created":1370174400,

-      "dockerfile":"my full dockerfile is listed here",

-      "repo_name":"username/reponame"

-   }

-}

-```

-

-Webhooks are available under the Settings tab of each Automated

-Build.

-

-> **Note:** If you want to test your webhook out then we recommend using

-> a tool like [requestb.in](http://requestb.in/).

-

-

-### Repository links

-

-Repository links are a way to associate one Automated Build with another. If one

-gets updated, linking system also triggers a build for the other Automated Build.

-This makes it easy to keep your Automated Builds up to date.

-

-To add a link, go to the settings page of an Automated Build and click on

-*Repository Links*. Then enter the name of the repository that you want have

-linked.

-

-> **Warning:**

-> You can add more than one repository link, however, you should

-> be very careful. Creating a two way relationship between Automated Builds will

-> cause a never ending build loop.

deleted file mode 100644

@@ -1,13 +0,0 @@

-page_title: The Docker Hub Registry Help

-page_description: The Docker Registry help documentation home

-page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, documentation

-

-# The Docker Hub Registry Help

-

-## Introduction

-

-For your questions about the [Docker Hub](https://hub.docker.com) registry you

-can use [this documentation](docs.md).

-

-If you can not find something you are looking for, please feel free to

-[contact us](https://docker.com/resources/support/).

deleted file mode 100644

@@ -1,8 +0,0 @@

-# Docker Hub

-

-## Contents:

-

-- [Accounts](accounts/)

-- [Repositories](repos/)

-- [Automated Builds](builds/)

-

deleted file mode 100644

@@ -1,97 +0,0 @@

-page_title: Repositories and Images on Docker Hub

-page_description: Repositories and Images on Docker Hub

-page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, documentation

-

-# Repositories and Images on Docker Hub

-

-## Searching for repositories and images

-

-You can `search` for all the publicly available repositories and images using

-Docker. If a repository is not public (i.e., 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

-

-### Stars

-

-Stars are a way to show that you like a repository. They are also an easy way

-of bookmark your favorites.

-

-### 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 the admins' review.

-

-### Private Docker Repositories

-

-To work with a private repository on [Docker Hub](https://hub.docker.com), you

-will need to add one via the [Add Repository](https://registry.hub.docker.com/account/repositories/add/)

-link. Once the private repository is created, you can `push` and `pull` images

-to and from it using Docker.

-

-> *Note:* You need to be signed in and have access to work with a private

-> repository.

-

-Private repositories are just like public ones. However, it isn't possible to

-browse them or search their content on the public registry. They do not get cached

-the same way as a public repository either.

-

-It is possible to give access to a private repository to those whom you 

-designate (i.e., collaborators) from its settings page.

-

-From there, you can also switch repository status (*public* to *private*, or

-viceversa). You will need to have an available private repository slot open

-before you can do such a switch. If you don't have any, you can always upgrade

-your [Docker Hub](https://registry.hub.docker.com/plans/) plan.

-

-### Collaborators and their role

-

-A collaborator is someone you want to give access to a private repository. Once

-designated, they can `push` and `pull`. Although, they will not be allowed to

-perform any administrative tasks such as deleting the repository or changing its

-status from private to public.

-

-> **Note:** A collaborator can not add other collaborators. Only the owner of

-> the repository has administrative access.

-

-### Webhooks

-

-You can configure webhooks on the repository settings page. 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.

-

-> **Note:** For testing, you can try an HTTP request tool like

-> [requestb.in](http://requestb.in/).

-

-*Example webhook JSON payload:*

-

-    {

-       "push_data":{

-          "pushed_at":1385141110,

-          "images":[

-             "imagehash1",

-             "imagehash2",

-             "imagehash3"

-          ],

-          "pusher":"username"

-       },

-       "repository":{

-          "status":"Active",

-          "description":"my docker repo that does cool things",

-          "is_automated":false,

-          "full_description":"This is my full description",

-          "repo_url":"https://registry.hub.docker.com/u/username/reponame/",

-          "owner":"username",

-          "is_official":false,

-          "is_private":false,

-          "name":"reponame",

-          "namespace":"username",

-          "star_count":1,

-          "comment_count":1,

-          "date_created":1370174400,

-          "dockerfile":"my full dockerfile is listed here",

-          "repo_name":"username/reponame"

-       }

-    }

new file mode 100644

@@ -0,0 +1,32 @@

+page_title: Accounts on Docker.io

+page_description: Docker.io accounts

+page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker.io, docs, documentation

+

+# Accounts on Docker.io

+

+## Docker.io Accounts

+

+You can `search` for Docker images and `pull` them from [Docker.io](https://index.docker.io)

+without signing in or even having an account. However, in order to `push` images,

+leave comments or to *star* a repository, you are going to need a [Docker.io](

+https://www.docker.io) account.

+

+### Registration for a Docker.io Account

+

+You can get a [Docker.io](https://index.docker.io) account by

+[signing up for one here](https://www.docker.io/account/signup/). A valid

+email address is required to register, which you will need to verify for

+account activation.

+

+### Email activation process

+

+You need to have at least one verified email address to be able to use your

+[Docker.io](https://index.docker.io) account. If you can't find the validation email,

+you can request another by visiting the [Resend Email Confirmation](

+https://www.docker.io/account/resend-email-confirmation/) page.

+

+### Password reset process

+

+If you can't access your account for some reason, you can reset your password

+from the [*Password Reset*](https://www.docker.io/account/forgot-password/)

+page.

\ No newline at end of file

new file mode 100644

@@ -0,0 +1,201 @@

+page_title: Automated Builds on Docker.io

+page_description: Docker.io Automated Builds

+page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker.io, docs, documentation, trusted, builds, trusted builds, automated, automated builds

+# Automated Builds on Docker.io

+

+## Automated Builds

+

+*Automated Builds* is a special feature allowing you to specify a source

+repository with a `Dockerfile` to be built by the

+[Docker.io](https://index.docker.io) build clusters. The system will

+clone your repository and build the `Dockerfile` using the repository as

+the context. The resulting image will then be uploaded to the registry

+and marked as an *Automated Build*.

+

+Automated Builds have a number of advantages. For example, users of

+*your* Automated Build can be certain that the resulting image was built

+exactly how it claims to be.

+

+Furthermore, the `Dockerfile` will be available to anyone browsing your repository

+on the registry. Another advantage of the Automated Builds feature is the automated

+builds. This makes sure that your repository is always up to date.

+

+Automated Builds are supported for both public and private repositories

+on both [GitHub](http://github.com) and

+[BitBucket](https://bitbucket.org/).

+

+### Setting up Automated Builds with GitHub

+

+In order to setup an Automated Build, you need to first link your [Docker.io](

+https://index.docker.io) account with a GitHub one. This will allow the registry

+to see your repositories.

+

+> *Note:* We currently request access for *read* and *write* since [Docker.io](

+> https://index.docker.io) needs to setup a GitHub service hook. Although nothing

+> else is done with your account, this is how GitHub manages permissions, sorry!

+

+Click on the [Automated Builds tab](https://index.docker.io/builds/) to

+get started and then select [+ Add

+New](https://index.docker.io/builds/add/).

+

+Select the [GitHub

+service](https://index.docker.io/associate/github/).

+

+Then follow the instructions to authorize and link your GitHub account

+to Docker.io.

+

+#### Creating an Automated Build

+

+You can [create an Automated Build](https://index.docker.io/builds/github/select/)

+from any of your public or private GitHub repositories with a `Dockerfile`.

+

+#### GitHub organizations

+

+GitHub organizations appear once your membership to that organization is

+made public on GitHub. To verify, you can look at the members tab for your

+organization on GitHub.

+

+#### GitHub service hooks

+

+You can follow the below steps to configure the GitHub service hooks for your

+Automated Build:

+

+<table class="table table-bordered">

+  <thead>

+    <tr>

+      <th>Step</th>

+      <th>Screenshot</th>

+      <th>Description</th>

+    </tr>

+  </thead>

+  <tbody>

+    <tr>

+      <td>1.</td>

+      <td><img src="https://d207aa93qlcgug.cloudfront.net/0.8/img/github_settings.png"></td>

+      <td>Login to Github.com, and visit your Repository page. Click on the repository "Settings" link. You will need admin rights to the repository in order to do this. So if you don't have admin rights, you will need to ask someone who does.</td>

+    </tr>

+    <tr>

+      <td>2.</td>

+      <td><img src="https://d207aa93qlcgug.cloudfront.net/0.8/img/github_service_hooks.png" alt="Service Hooks"></td>

+      <td>Click on the "Service Hooks" link</td></tr><tr><td>3.</td><td><img src="https://d207aa93qlcgug.cloudfront.net/0.8/img/github_docker_service_hook.png" alt="Find the service hook labeled Docker"></td><td>Find the service hook labeled "Docker" and click on it.</td></tr><tr><td>4.</td><td><img src="https://d207aa93qlcgug.cloudfront.net/0.8/img/github_service_hook_docker_activate.png" alt="Activate Service Hooks"></td>

+      <td>Click on the "Active" checkbox and then the "Update settings" button, to save changes.</td>

+    </tr>

+  </tbody>

+</table>

+

+### Setting up Automated Builds with BitBucket

+

+In order to setup an Automated Build, you need to first link your

+[Docker.io]( https://index.docker.io) account with a BitBucket one. This

+will allow the registry to see your repositories.

+

+Click on the [Automated Builds tab](https://index.docker.io/builds/) to

+get started and then select [+ Add

+New](https://index.docker.io/builds/add/).

+

+Select the [BitBucket

+service](https://index.docker.io/associate/bitbucket/).

+

+Then follow the instructions to authorize and link your BitBucket account

+to Docker.io.

+

+#### Creating an Automated Build

+

+You can [create an Automated

+Build](https://index.docker.io/builds/bitbucket/select/) from any of

+your public or private BitBucket repositories with a `Dockerfile`.

+

+### The Dockerfile and Automated Builds

+

+During the build process, we copy the contents of your `Dockerfile`. We also

+add it to the [Docker.io](https://index.docker.io) for the Docker community

+to see on the repository page.

+

+### README.md

+

+If you have a `README.md` file in your repository, we will use that as the

+repository's full description.

+

+> **Warning:**

+> If you change the full description after a build, it will be

+> rewritten the next time the Automated Build has been built. To make changes,

+> modify the README.md from the Git repository. We will look for a README.md

+> in the same directory as your `Dockerfile`.

+

+### Build triggers

+

+If you need another way to trigger your Automated Builds outside of GitHub

+or BitBucket, you can setup a build trigger. When you turn on the build

+trigger for an Automated Build, it will give you a URL to which you can

+send POST requests. This will trigger the Automated Build process, which

+is similar to GitHub webhooks.

+

+Build Triggers are available under the Settings tab of each Automated Build.

+

+> **Note:** 

+> You can only trigger one build at a time and no more than one

+> every five minutes. If you have a build already pending, or if you already

+> recently submitted a build request, those requests *will be ignored*.

+> You can find the logs of last 10 triggers on the settings page to verify

+> if everything is working correctly.

+

+### Webhooks

+

+Also available for Automated Builds are Webhooks. Webhooks can be called

+after a successful repository push is made.

+

+The webhook call will generate a HTTP POST with the following JSON

+payload:

+

+```

+{

+   "push_data":{

+      "pushed_at":1385141110,

+      "images":[

+         "imagehash1",

+         "imagehash2",

+         "imagehash3"

+      ],

+      "pusher":"username"

+   },

+   "repository":{

+      "status":"Active",

+      "description":"my docker repo that does cool things",

+      "is_automated":false,

+      "full_description":"This is my full description",

+      "repo_url":"https://index.docker.io/u/username/reponame/",

+      "owner":"username",

+      "is_official":false,

+      "is_private":false,

+      "name":"reponame",

+      "namespace":"username",

+      "star_count":1,

+      "comment_count":1,

+      "date_created":1370174400,

+      "dockerfile":"my full dockerfile is listed here",

+      "repo_name":"username/reponame"

+   }

+}

+```

+

+Webhooks are available under the Settings tab of each Automated

+Build.

+

+> **Note:** If you want to test your webhook out then we recommend using

+> a tool like [requestb.in](http://requestb.in/).

+

+

+### Repository links

+

+Repository links are a way to associate one Automated Build with another. If one

+gets updated, linking system also triggers a build for the other Automated Build.

+This makes it easy to keep your Automated Builds up to date.

+

+To add a link, go to the settings page of an Automated Build and click on

+*Repository Links*. Then enter the name of the repository that you want have

+linked.

+

+> **Warning:**

+> You can add more than one repository link, however, you should

+> be very careful. Creating a two way relationship between Automated Builds will

+> cause a never ending build loop.

new file mode 100644

@@ -0,0 +1,13 @@

+page_title: The Docker.io Registry Help

+page_description: The Docker Registry help documentation home

+page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker.io, docs, documentation

+

+# The Docker.io Registry Help

+

+## Introduction

+

+For your questions about the [Docker.io](https://index.docker.io) registry you

+can use [this documentation](docs.md).

+

+If you can not find something you are looking for, please feel free to

+[contact us](https://index.docker.io/help/support/).

\ No newline at end of file

new file mode 100644

@@ -0,0 +1,8 @@

+# Docker.io

+

+## Contents:

+

+- [Accounts](accounts/)

+- [Repositories](repos/)

+- [Automated Builds](builds/)

+

new file mode 100644

@@ -0,0 +1,98 @@

+page_title: Repositories and Images on Docker.io

+page_description: Repositories and Images on Docker.io

+page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker.io, docs, documentation

+

+# Repositories and Images on Docker.io

+

+## Searching for repositories and images

+

+You can `search` for all the publicly available repositories and images using

+Docker. If a repository is not public (i.e., private), it won't be listed on

+the repository search results. To see repository statuses, you can look at your

+[profile page](https://index.docker.io/account/) on [Docker.io](

+https://index.docker.io).

+

+## Repositories

+

+### Stars

+

+Stars are a way to show that you like a repository. They are also an easy way

+of bookmark your favorites.

+

+### 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 the admins' review.

+

+### Private Docker Repositories

+

+To work with a private repository on [Docker.io](https://index.docker.io), you

+will need to add one via the [Add Repository](https://index.docker.io/account/repositories/add)

+link. Once the private repository is created, you can `push` and `pull` images

+to and from it using Docker.

+

+> *Note:* You need to be signed in and have access to work with a private

+> repository.

+

+Private repositories are just like public ones. However, it isn't possible to

+browse them or search their content on the public registry. They do not get cached

+the same way as a public repository either.

+

+It is possible to give access to a private repository to those whom you 

+designate (i.e., collaborators) from its settings page.

+

+From there, you can also switch repository status (*public* to *private*, or

+viceversa). You will need to have an available private repository slot open

+before you can do such a switch. If you don't have any, you can always upgrade

+your [Docker.io](https://index.docker.io/plans/) plan.

+

+### Collaborators and their role

+

+A collaborator is someone you want to give access to a private repository. Once

+designated, they can `push` and `pull`. Although, they will not be allowed to

+perform any administrative tasks such as deleting the repository or changing its

+status from private to public.

+

+> **Note:** A collaborator can not add other collaborators. Only the owner of

+> the repository has administrative access.

+

+### Webhooks

+

+You can configure webhooks on the repository settings page. 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.

+

+> **Note:** For testing, you can try an HTTP request tool like

+> [requestb.in](http://requestb.in/).

+

+*Example webhook JSON payload:*

+

+    {

+       "push_data":{

+          "pushed_at":1385141110,

+          "images":[

+             "imagehash1",

+             "imagehash2",

+             "imagehash3"

+          ],

+          "pusher":"username"

+       },

+       "repository":{

+          "status":"Active",

+          "description":"my docker repo that does cool things",

+          "is_automated":false,

+          "full_description":"This is my full description",

+          "repo_url":"https://index.docker.io/u/username/reponame/",

+          "owner":"username",

+          "is_official":false,

+          "is_private":false,

+          "name":"reponame",

+          "namespace":"username",

+          "star_count":1,

+          "comment_count":1,

+          "date_created":1370174400,

+          "dockerfile":"my full dockerfile is listed here",

+          "repo_name":"username/reponame"

+       }

+    }

@@ -1,14 +1,15 @@

 page_title: Dockerizing MongoDB

-page_description: Creating a Docker image with MongoDB pre-installed using a Dockerfile and sharing the image on Docker Hub

+page_description: Creating a Docker image with MongoDB pre-installed using a Dockerfile and sharing the image on Docker.io

 page_keywords: docker, dockerize, dockerizing, article, example, docker.io, platform, package, installation, networking, mongodb, containers, images, image, sharing, dockerfile, build, auto-building, virtualization, framework

 # Dockerizing MongoDB

 ## Introduction

-In this example, we are going to learn how to build a Docker image with

-MongoDB pre-installed.  We'll also see how to `push` that image to the

-[Docker Hub registry](https://hub.docker.com) and share it with others!

+In this example, we are going to learn how to build a Docker image

+with MongoDB pre-installed.

+We'll also see how to `push` that image to the [Docker.io registry](

+https://index.docker.io) and share it with others!

 Using Docker and containers for deploying [MongoDB](https://www.mongodb.org/)

 instances will bring several benefits, such as:

@@ -40,7 +41,7 @@ Although optional, it is handy to have comments at the beginning of a

 > the *parent* of your *Dockerized MongoDB* image.

 We will build our image using the latest version of Ubuntu from the

-[Docker Hub Ubuntu](https://registry.hub.docker.com/_/ubuntu/) repository.

+[Docker.io Ubuntu](https://index.docker.io/_/ubuntu/) repository.

     # Format: FROM    repository[:version]

     FROM       ubuntu:latest

@@ -108,10 +109,10 @@ experimenting, it is always a good practice to tag Docker images by passing the

 Once this command is issued, Docker will go through the `Dockerfile` and build

 the image. The final image will be tagged `my/repo`.

-## Pushing the MongoDB image to Docker Hub

+## Pushing the MongoDB image to Docker.io

 All Docker image repositories can be hosted and shared on

-[Docker Hub](https://hub.docker.com) with the `docker push` command. For this,

+[Docker.io](https://index.docker.io) with the `docker push` command. For this,

 you need to be logged-in.

     # Log-in

@@ -65,9 +65,9 @@ requires to build (this example uses Docker 0.3.4):

     # DOCKER-VERSION 0.3.4

 Next, define the parent image you want to use to build your own image on

-top of. Here, we'll use

-[CentOS](https://registry.hub.docker.com/_/centos/) (tag: `6.4`)

-available on the [Docker Hub](https://hub.docker.com/):

+top of. Here, we'll use [CentOS](https://index.docker.io/_/centos/)

+(tag: `6.4`) available on the [Docker

+index](https://index.docker.io/):

     FROM    centos:6.4

@@ -11,7 +11,7 @@ page_keywords: docker, example, package installation, postgresql

 ## Installing PostgreSQL on Docker

 Assuming there is no Docker image that suits your needs on the [Docker