Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
start and the first shelr video use example.org
|
|
|
|
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.
|
|
|
|
was not clear how to get it to do that (see #3897)
|
|
|
|
|
|
|
|
standardize on including the shell prompt so it is clear
|
|
|
|
|
|
|
|
|
|
(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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|