node is host
This commit is contained in:
@@ -46,13 +46,13 @@ help This help
|
||||
$ make bootstrap DOMAIN=domain.tld STACK=default
|
||||
```
|
||||
|
||||
* Start myos stack `node`
|
||||
* Start myos stack `host`
|
||||
|
||||
```shell
|
||||
$ make node
|
||||
$ make host
|
||||
```
|
||||
|
||||
`make node` starts the stack `node` with docker host services :
|
||||
`make host` starts the stack `host` with docker host services :
|
||||
- consul (service discovery)
|
||||
- fabio (load balancer)
|
||||
- registrator (docker/consul bridge)
|
||||
@@ -127,33 +127,33 @@ acme.${DOMAIN}. IN NS ${DOMAIN}.
|
||||
This will point domain ${DOMAIN} to the IP address ${DOCKER_HOST_INET4} of this server, and point all subdomains *.{DOMAIN} to the ip address pointed by ${DOMAIN}.
|
||||
|
||||
At this point, you should be able to generate a valid certificate for *.${DOMAIN} using certbot [dns standalone](https://github.com/siilike/certbot-dns-standalone) plugin.
|
||||
This task is done automatically when creating the node stack if SETUP_LETSENCRYPT variable is not empty.
|
||||
This task is done automatically when creating the host stack if SETUP_LETSENCRYPT variable is not empty.
|
||||
|
||||
If you already launched myos node stack before, the ${DOMAIN} certificates has been automatically generated by openssl and you should remove them before trying to generate them with letsencrypt.
|
||||
If you already launched myos host stack before, the ${DOMAIN} certificates has been automatically generated by openssl and you should remove them before trying to generate them with letsencrypt.
|
||||
|
||||
```
|
||||
$ make node-down
|
||||
$ docker volume rm node_myos
|
||||
$ make host-down
|
||||
$ docker volume rm $(hostname)
|
||||
```
|
||||
|
||||
You can then test the letsencrypt certificate generation using DEBUG mode that force to use the letsencrypt staging server.
|
||||
|
||||
```
|
||||
$ make node SETUP_LETSENCRYPT=true DEBUG=true
|
||||
$ make host SETUP_LETSENCRYPT=true DEBUG=true
|
||||
```
|
||||
|
||||
If letsencrypt certificate generation fails, you can retry the generation of a staging certificate.
|
||||
|
||||
```
|
||||
$ make node-certbot-staging
|
||||
$ make host-certbot-staging
|
||||
```
|
||||
|
||||
Once the certificate generation is working, you can ask for a valid certificate.
|
||||
|
||||
```
|
||||
$ make node-down
|
||||
$ docker volume rm node_myos
|
||||
$ make node SETUP_LETSENCRYPT=true
|
||||
$ make host-down
|
||||
$ docker volume rm $(hostname)
|
||||
$ make host SETUP_LETSENCRYPT=true
|
||||
```
|
||||
|
||||
### Debug
|
||||
@@ -165,7 +165,7 @@ $ make config
|
||||
```
|
||||
|
||||
`make config` show docker compose yaml config for stack `STACK`
|
||||
`make node-config` show docker compose yaml config for stack `node`
|
||||
`make host-config` show docker compose yaml config for stack `host`
|
||||
`make user-config` show docker compose yaml config for stack `User`
|
||||
`make stack-elastic-config` show docker compose yaml config for stack `elastic`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user