Rename "datadir init" to "datadir create"

Author: skrysmanski

README.md

@@ -93,13 +93,13 @@ The contents of this directory are:
 
 To create this directory from scratch, call:
 
-    $ ./ssh-env datadir init
+    $ ./ssh-env datadir create
 
 You'll be asked a series of questions.
 
 **Note:** When you're asked for the "passphrase" for the rsa key pair, it's highly recommended that use **a strong password** here.
 
-    $ ./ssh-env datadir init
+    $ ./ssh-env datadir create
     Do you have an SSH key pair (in case of doubt: no)? (y/n): n
 
     Who does this key pair belong to? [manski]:
@@ -311,11 +311,11 @@ As far as synchronizing is concerned, an ssh-env directory is comprised of three
 
 The root directory is (usually) already version controlled under Git - so you can use Git to put it on other computers.
 
-If you used `./ssh-env datadir init` to create your data directory, ssh-env gave you the option to create a Git repository for the data directory. In this case, you use Git to synchronize your ssh data between computers. On another computer you can then use this command to get your ssh data:
+If you used `./ssh-env datadir create` to create your data directory, ssh-env gave you the option to create a Git repository for the data directory. In this case, you use Git to synchronize your ssh data between computers. On another computer you can then use this command to get your ssh data:
 
     ./ssh-env datadir clone
 
-*Note:* While ssh-env uses Git internally for `datadir init/clone`, you can use any other version control system you like (like Mercurial or even Subversion) to version your ssh data directory. ssh-env doesn't mind.
+*Note:* While ssh-env uses Git internally for `datadir create/clone`, you can use any other version control system you like (like Mercurial or even Subversion) to version your ssh data directory. ssh-env doesn't mind.
 
 The third part (`./local/`) should not be synchronized. So there's nothing you need to do here.
 

app/SshAgent.psm1

@@ -246,7 +246,7 @@ function Add-SshKeyToRunningAgent([String] $SshPrivateKeyPath, [int] $KeyTimeToL
 
 function Assert-SshAgentState([String] $SshPrivateKeyPath) {
 	if (-Not (Test-Path $SshPrivateKeyPath)) {
-		Write-Error "Private SSH key doesn't exist at: $SshPrivateKeyPath`nDid you run: ./ssh-env datadir init/clone ?"
+		Write-Error "Private SSH key doesn't exist at: $SshPrivateKeyPath`nDid you run: ssh-env datadir create/clone ?"
 	}
 
 	$agentConf = Get-SshAgentConfig -CreateIfNotExists

app/SshEnvApp.ps1

@@ -93,7 +93,7 @@ function Invoke-SshEnvApp {
 					break
 				}
 
-				'init' {
+				'create' {
 					Initialize-DataDirFromScratch
 					break
 				}

app/_HELP.txt

@@ -1,7 +1,7 @@
 Usage:
   ssh-env [ssh] [<user>@]<ssh-server>
   ssh-env agent (status|stop|config)
-  ssh-env datadir (init|clone|global-install|global-uninstall)
+  ssh-env datadir (create|clone|global-install|global-uninstall)
   ssh-env key (create|install|check|load)
   ssh-env (help|--help|-h)
   ssh-env (version|--version|-v)
@@ -14,7 +14,7 @@ Commands:
   agent stop                 Stops the ssh-agent (removing any loaded private key from memory)
   agent config               Creates configuration file for ssh-agent (per computer and not shared)
 
-  datadir init               Creates a fresh ssh data dir (containing the ssh key pair and ssh config)
+  datadir create             Creates a fresh ssh data dir (containing the ssh key pair and ssh config)
   datadir clone              Clones an existing ssh data dir with git
   datadir status             Prints various information about the datadir
   datadir global-install     Makes the data dir available to all ssh processes for the current user