Commit d29973a4 authored by Maarten de Waard's avatar Maarten de Waard 🤘🏻

clarify reference to API

parent d362c5c6
......@@ -23,9 +23,9 @@ documentation.](https://github.com/torvalds/linux/blob/master/Documentation/file
### Startup Notification
Some extra variables are used in Greenhost's case to be able to use the API to
send a message to the owner of a VPS after it has been restarted. These
variables are used in /scripts/local-top/cryptroot-api to make
Some extra variables are used in Greenhost's case to be able to use the Cosmos
Service Centre API to send a message to the owner of a VPS after it has been
restarted. These variables are used in /scripts/local-top/cryptroot-api to make
`$notification_command`.
If you don't run on Greenhost infrastructure, change
......@@ -35,9 +35,9 @@ If you do not have a notification_command, CryptOps will work fine, but when
your VPS reboots, you run the risk of not knowing this and your VPS will stay in
the initrd, waiting for you to unlock the disk.
- `api_key=<key>`: The *Bearer* authentication key for using the API
- `api_key=<key>`: The *Bearer* authentication key for using the Cosmos API
- `instance_id=###`: The unique identifier of the VPS
- `cosmos_url=https://management.greenhost.nl`: The URL to the API
- `cosmos_url=https://management.greenhost.nl`: The URL to the Cosmos API
A VPS is assumed to have one drive that needs to be encrypted (additional drives
can be encrypted manually from the booted operating system). The drive will be
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment