Commit a2db7fbb authored by Ludvig Bohlin's avatar Ludvig Bohlin

Fixed spacing after details environment

parent 8a1d1fa3
......@@ -96,7 +96,7 @@ Below are descriptions of the variables that can be configured in the file `grou
| <div style="width:250px">Task Variables</div>| Description |
|----------|:-------------|
| <blockquote><i>The below variables can take the values `True` or `False` to define what to install.</i></blockquote>| <blockquote><i>We recommend to have all variables `True` in the first run. In subsequent runs you can set them to `False`, except for `run_create_deploys`.</i> </blockquote>|
| <i>The below variables can take the values `True` or `False` to define what to install.</i>| <i>We recommend to have all variables `True` in the first run. In subsequent runs you can set them to `False`, except for `run_create_deploys`.</i>|
| `run_install_packages` | Task that updates the server and installs certain packages, for example git, aptitude, python3, pip, and locale. |
| `run_install_requirements` | Task that creates the user and group shimmercat, and uploads the installer for [sc_pack](../../sc_pack/intro_sc_pack). |
| `run_install_haproxy` | Task that installs and configures the <a href="http://www.haproxy.org" target="_blank">haproxy load balancer</a>. This is demonized. |
......@@ -120,7 +120,7 @@ Below are descriptions of the variables that can be configured in the file `grou
| <div style="width:250px">Deployment Variables</div> | Description |
|----------|:-------------|
| <blockquote>Note that with `instance_1` and `instance_2` we are indicating that two instances of `sc_pack` will be installed in the respective `install_dir`, on each of the servers defined in the `production` inventory.</blockquote> |<blockquote>Having more than one deployment per edge server can come in handy for experimentation, rolling upgrades and configuring high-availability setups. For testing only one instance is sufficient, but in production two is recommended.</blockquote> |
| Note that with `instance_1` and `instance_2` we are indicating that two instances of `sc_pack` will be installed in the respective `install_dir`, on each of the servers defined in the `production` inventory. |Having more than one deployment per edge server can come in handy for experimentation, rolling upgrades and configuring high-availability setups. For testing only one instance is sufficient, but in production two is recommended. |
| `install_dir` | The directory for ShimmerCat, celery, and all the services that sc_pack includes. All the log files and directories needed to run the services, including configuration files for ShimmerCat and supervisord, will be in this directory.|
| `http_port` | `8010`, `8011`, `8012`, etc. HTTP port where ShimmerCat listen. |
| `https_port` | `4010`, `4011`, `4012`, etc. HTTPS port where ShimmerCat listen. |
......
......@@ -11,8 +11,10 @@
</ul>
</details>
>__Docker/Ansible setup overview__
> <p>Typically the Control Node would be a local PC, and the Managed Node(s) edge servers.</p>
**Docker/Ansible setup overview**
Typically the Control Node would be a local PC, and the Managed Node(s) edge servers.
![docker_explained](images/docker_explained.png)
......@@ -93,7 +95,7 @@ Below are descriptions of the variables that can be configured in the file `grou
| <div style="width:250px">Task Variables</div>| Description |
|----------|:-------------|
| <blockquote><i>The below variables can take the values `True` or `False` to define what to install.</i></blockquote>| <blockquote><i>We recommend to have all variables `True` in the first run. In subsequent runs you can set them to `False`, except for `run_create_deploys`.</i> </blockquote>|
| <i>The below variables can take the values `True` or `False` to define what to install.</i>| <i>We recommend to have all variables `True` in the first run. In subsequent runs you can set them to `False`, except for `run_create_deploys`.</i> |
| `run_install_packages` | Task that updates the server and installs certain packages, for example git, aptitude, python3, pip, and locale. |
| `run_install_requirements` | Task that creates the user and group shimmercat, and uploads the installer for [sc_pack](../../sc_pack/intro_sc_pack). |
| `run_install_haproxy` | Task that installs and configures the <a href="http://www.haproxy.org" target="_blank">haproxy load balancer</a>. This is demonized. |
......@@ -117,7 +119,7 @@ Below are descriptions of the variables that can be configured in the file `grou
| <div style="width:250px">Deployment Variables</div> | Description |
|----------|:-------------|
| <blockquote>Note that with `instance_1` and `instance_2` we are indicating that two instances of `sc_pack` will be installed in the respective `install_dir`, on each of the servers defined in the `production` inventory.</blockquote> |<blockquote>Having more than one deployment per edge server can come in handy for experimentation, rolling upgrades and configuring high-availability setups. For testing only one instance is sufficient, but in production two is recommended.</blockquote> |
| Note that with `instance_1` and `instance_2` we are indicating that two instances of `sc_pack` will be installed in the respective `install_dir`, on each of the servers defined in the `production` inventory. |Having more than one deployment per edge server can come in handy for experimentation, rolling upgrades and configuring high-availability setups. For testing only one instance is sufficient, but in production two is recommended. |
| `install_dir` | The directory for ShimmerCat, celery, and all the services that sc_pack includes. All the log files and directories needed to run the services, including configuration files for ShimmerCat and supervisord, will be in this directory.|
| `http_port` | `8010`, `8011`, `8012`, etc. HTTP port where ShimmerCat listen. |
| `https_port` | `4010`, `4011`, `4012`, etc. HTTPS port where ShimmerCat listen. |
......
......@@ -12045,4 +12045,9 @@ a:hover {
color: white;
}
details {
margin-bottom: 20px;
}
/*# sourceMappingURL=theme.css.map */
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