From 8be8be3648244779d632d0190e103e77396da661 Mon Sep 17 00:00:00 2001 From: varac Date: Fri, 6 Mar 2015 14:14:30 +0100 Subject: shortened single node email guide, moved additional provider configuration to separate file --- .../docs/platform/tutorials/configure-provider.md | 31 ++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 pages/docs/platform/tutorials/configure-provider.md (limited to 'pages/docs/platform/tutorials/configure-provider.md') diff --git a/pages/docs/platform/tutorials/configure-provider.md b/pages/docs/platform/tutorials/configure-provider.md new file mode 100644 index 0000000..969d541 --- /dev/null +++ b/pages/docs/platform/tutorials/configure-provider.md @@ -0,0 +1,31 @@ +@title = 'Configure provider tutorial' +@nav_title = 'Configure Provider' +@summary = 'Explore how to configure your provider after the initial setup' + + +Edit provider.json configuration +-------------------------------------- + +There are a few required settings in provider.json. At a minimum, you must have: + + { + "domain": "example.org", + "name": "Example", + "contacts": { + "default": "email1@example.org" + } + } + +For a full list of possible settings, you can use `leap inspect` to see how provider.json is evaluated after including the inherited defaults: + + $ leap inspect provider.json + + +Examine Certs +============= + +To see details about the keys and certs that the prior two commands created, you can use `leap inspect` like so: + + $ leap inspect files/ca/ca.crt + +NOTE: the files `files/ca/*.key` are extremely sensitive and must be carefully protected. The other key files are much less sensitive and can simply be regenerated if needed. -- cgit v1.2.3