Move staging container to gcr, check in Dockerfile.

2016-09-20 10:17:53 -07:00
parent b4b944b785
commit 6d4ea99b12
3 changed files with 19 additions and 6 deletions
@@ -37,14 +37,14 @@ git fetch upstream
 git reset --hard upstream/docsv2
 ```

-### Step 3: Make sure you can serve rendered docs 
+### Step 3: Make sure you can serve rendered docs

 One option is to simply rename your fork's repo on GitHub.com to `yourusername.github.io`, which will auto-stage your commits at that URL. 

 Or, just use Docker! Run this from within your local `kubernetes.github.io` directory and you should be good:

 ```shell
-docker run -ti --rm -v "$PWD":/k8sdocs -p 4000:4000 johndmulhausen/k8sdocs
+docker run -ti --rm -v "$PWD":/k8sdocs -p 4000:4000 gcr.io/google-samples/k8sdocs:1.0
 ```

 The site will then be viewable at [http://localhost:4000/](http://localhost:4000/).
@@ -246,4 +246,4 @@ You probably shouldn't be using this, but we also have templates which consume Y

 ### Adding page to navigation

-Once your page is saved, somewhere in the `/docs/` directory, add a reference to the `reference.yml` file under `/_data/` so that it will appear in the left-hand navigation of the site. This is also where you add a title to the page.
+Once your page is saved, somewhere in the `/docs/` directory, add a reference to the `reference.yml` file under `/_data/` so that it will appear in the left-hand navigation of the site. This is also where you add a title to the page.