14 Commits (a7bdb362da73f6af62f765b542af39c2975845d2)

Author	SHA1	Message	Date
Przemo Nowaczyk	a156691e37	small docs fixes	2014-10-28 21:03:13 +01:00
Joe Beda	5c84cd21a4	Tweak vagrant README a little for new binary deploy world.	2014-10-11 15:37:06 -07:00
Joe Beda	38d5906044	Clean up READMEs and broken stuff. ... Move all support for clouds that are broken with this change into an `icebox` directory. We'll move that stuff back out as we fix it up.	2014-10-10 12:33:36 -07:00
KORNISTE	6462030a32	fix spelling : docs/getting-started-guides/vagrant.md	2014-09-28 00:54:35 +09:00
Brendan Burns	e8f3c3cb19	Fix a typo, add instructions for running make.	2014-09-26 14:52:03 -07:00
Joe Beda	7743f33359	Merge pull request #1379 from runseb/vagrant ... Modifications and improvements to the vagrant cluster README	2014-09-23 09:21:04 -07:00
Sebastien Goasguen	826680353d	Modifications and improvements to the vagrant cluster README	2014-09-23 15:39:16 +02:00
Brendan Burns	0c2ea0bcf2	rev versions to 0.3	2014-09-22 14:54:33 -07:00
brendandburns	84edb60bcd	slight wording change	2014-09-08 21:12:56 -07:00
brendandburns	56c8f43f0c	update vagrant to point at the 0.2 release	2014-09-08 21:12:36 -07:00
derekwaynecarr	10be80295c	apiserver listen on 0.0.0.0 in vagrant	2014-08-14 10:02:04 -04:00
Brad Wells	0ef6b9eb19	Add explicit instruction to vagrant example docs ... Building kubecfg is required for kubecfg.sh. kubecfg.sh will warn of this if it hasn't been built, but it's a better user experience to make people explicitly aware of all required steps.	2014-08-08 23:09:58 -06:00
Amy Unruh	f9bbddf892	minor docs/error msg cleanup	2014-08-06 15:43:27 -07:00
Kelsey Hightower	ebf89262eb	Move getting started guides to dedicated directory ... The project README is getting quite large mainly because of all the getting started guides embedded in the README. Create the docs/getting-started-guides directory and relocate all getting started guides. Update the README to link to each getting started guide.	2014-08-03 13:16:18 -07:00