summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-10-08typovarac
2013-10-01add nicknym to the dns outputMicah Anderson
2013-09-30make minor adjustments to the documentation to clarify some thignsMicah Anderson
2013-09-30make a note that 'leap cert ca' will create both certificate authoritiesMicah Anderson
2013-09-30add missing step in cloning the platformMicah Anderson
2013-09-30add bzip2 as a prerequisiteMicah Anderson
2013-09-27minor fixes to languageMicah Anderson
2013-09-27updated requirements, added /etc/hosts workaroundvarac
2013-09-27increase verbosityvarac
2013-09-27added Limitations to development guidevarac
2013-09-27added vpn nodevarac
2013-09-27added meta tags to troubleshooting.mdvarac
2013-09-27improved troubleshooting.mdvarac
2013-09-27added troubleshooting.md to the menuvarac
2013-09-27layout cosmeticsvarac
2013-09-27added faq.md to the menuvarac
2013-09-27added TOC, vagrant troubleshooting and working combinationsvarac
2013-09-27removed false linkvarac
2013-09-27added link to first vagrant referencevarac
2013-09-26linked shelr screencastsvarac
2013-09-26fixed cmd to show puppet managed resourcesvarac
2013-09-26minor improvements of quick-start.mdvarac
2013-09-26changes hostnames in quick-start to match shelr demovarac
2013-09-26--noping doesn't exist anymore in leap_clivarac
2013-09-26replace example.net with example.org cause the contact emails in the quick ↵varac
start and the first shelr video use example.org
2013-09-25update nav-title for coherenceKali Kaneko
2013-09-25fix typoKali Kaneko
2013-09-25Merge branch 'master' of ssh://leap.se/leap_docKali Kaneko
2013-09-25remove broken internal refsKali Kaneko
2013-09-25update client menu to latest structureKali Kaneko
2013-09-25fix repo path in user-installKali Kaneko
2013-09-25add prompt to leap list and singularizeMicah Anderson
2013-09-25add information about how much disk space is sufficient.Micah Anderson
I based this on looking at the production webapp node and saw that it was created with 5gb and has 37% used, and a couchdb node that was allocated 10gb and had 16% used, and an openvpn node which was created with 12gb and had 11% used. So that seemed to me to indicate that 10gb would be sufficient for an initial start and then some growth.
2013-09-25update client docsKali Kaneko
This are the most important pages in the bitmask documentation. I have converted .rst files using pandoc, since the .rst does not seem to be supported like the README says. I have added @nav_title and @title headers.
2013-09-25fix pythonhosted linkKali Kaneko
2013-09-25update bitmask landing pageKali Kaneko
2013-09-25add master doc for updated client docs, in rst format.Kali Kaneko
2013-09-25corrcting transifex url for client translationskwadronaut
2013-09-19clarify what virtualization technologies work in the quickstart guideMicah Anderson
2013-09-19removed the services-diagram image, it wasn't displaying properly, and it ↵Micah Anderson
was not clear how to get it to do that (see #3897)
2013-09-19add a missing space and some details about VCS configuration trackingMicah Anderson
2013-09-19add a missing promptMicah Anderson
2013-09-19make things show up in a more cleanly sorted way so the TOC is not a huge blobMicah Anderson
2013-09-19more spacing changes for code-blocksMicah Anderson
standardize on including the shell prompt so it is clear
2013-09-19add link to the quick-startMicah Anderson
2013-09-19fix spacing for code blocksMicah Anderson
2013-09-19add the development document to the menutMicah Anderson
2013-09-19properly fix the examples menu itemMicah Anderson
2013-09-19fix examples so they dont show up in the navigationMicah Anderson
2013-09-19Due to the fact that so many people would start with the quickstart guide ↵Micah Anderson
(because we recommended it), and would get completely hung-up on vagrant not working and if they managed to succeed in fighting through those problems, ended up with a provider that wasn't able to actually do anything at all. So, the goal was to move the quickstart information into a development setup howto, and then revamp the quickstart to be a minimal provider setup from scratch configuration that results in you getting familiar with the concepts (provider, platform, cli, nodes, services, etc.) and leaves you at the end with a functional minimal provider.