coolaj86
/
walnut.js
1
1
Fork 1
Code Issues Pull Requests Releases Activity

Update INSTALL.md

This commit is contained in:
Drew Warren 2017-09-08 14:55:33 -06:00
parent 3a6264939e
commit ae1b21bfb2
1 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
INSTALL.md
View File

@ -23,14 +23,14 @@ Pre-requisites:
Choose a domain Choose a domain
--------------- ---------------
For the purpose of this instruction we'll assume that your domain is `example.com`, For the purpose of this instruction we'll assume that your domain is `foo.com`,
but you can use, say, `johndoe.daplie.me` for testing through Daplie Domains. but you can use, say, `johndoe.daplie.me` for testing through Daplie Domains.
Anyway, go ahead and set the bash variable `$my_domain` for the purposes of the Anyway, go ahead and set the bash variable `$my_domain` for the purposes of the
rest of this tutorial: rest of this tutorial:
``` ```
my_domain=example.com my_domain=foo.com
``` ```
You can purchase a domain with daplie tools You can purchase a domain with daplie tools
@ -47,17 +47,17 @@ Subdomains
Auth will be loaded with the following domains Auth will be loaded with the following domains
``` ```
provider.example.com provider.foo.com
api.provider.example.com api.provider.foo.com
``` ```
The Hello World app will be loaded with the following domains The Hello World app will be loaded with the following domains
``` ```
example.com foo.com
www.example.com www.foo.com
api.example.com api.foo.com
assets.example.com assets.foo.com
``` ```
The domains can be setup through the Daplie Desktop App or with daplie-tools The domains can be setup through the Daplie Desktop App or with daplie-tools
@ -101,16 +101,16 @@ daplie-install-goldilocks
Example `/etc/goldilocks/goldilocks.yml`: Example `/etc/goldilocks/goldilocks.yml`:
```yml ```yml
tls: tls:
email: domains@example.com email: user@mailservice.com
servernames: servernames:
- example.com - foo.com
- www.example.com - www.foo.com
- api.example.com - api.foo.com
- assets.example.com - assets.foo.com
- cloud.example.com - cloud.foo.com
- api.cloud.example.com - api.cloud.foo.com
- provider.example.com - provider.foo.com
- api.provider.example.com - api.provider.foo.com
http: http:
trust_proxy: true trust_proxy: true