|
|
|
@ -43,7 +43,7 @@ To create a `bootstrap.yml` file for the new host, the admin should perform the |
|
|
|
|
following command from their own host: |
|
|
|
|
|
|
|
|
|
``` |
|
|
|
|
cryptic-net hosts make-bootstrap \ |
|
|
|
|
cryptic-net hosts create-bootstrap \ |
|
|
|
|
--hostname <name> \ |
|
|
|
|
--ip <ip> \ |
|
|
|
|
--admin-path <path to admin.yml> \ |
|
|
|
@ -61,12 +61,12 @@ running their host's `cryptic-net daemon`. |
|
|
|
|
### Encrypted `admin.yml` |
|
|
|
|
|
|
|
|
|
If `admin.yml` is kept in an encrypted format on disk (it should be!) then the |
|
|
|
|
decrypted form can be piped into `make-bootstrap` over stdin. For example, if |
|
|
|
|
decrypted form can be piped into `create-bootstrap` over stdin. For example, if |
|
|
|
|
GPG is being used to secure `admin.yml` then the following could be used to |
|
|
|
|
generate a `bootstrap.yml`: |
|
|
|
|
|
|
|
|
|
``` |
|
|
|
|
gpg -d <path to admin.yml.gpg> | cryptic-net hosts make-boostrap \ |
|
|
|
|
gpg -d <path to admin.yml.gpg> | cryptic-net hosts create-bootstrap \ |
|
|
|
|
--hostname <name> \ |
|
|
|
|
--ip <ip> \ |
|
|
|
|
--admin-path - \ |
|
|
|
|