github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-05-03 20:36:06 -05:00
Code Issues 3.5k Packages Projects Releases 103 Wiki Activity

1.13.2 (#35)

Browse Source 
* 1.13.2 add periphery disk report whitelist / blacklist

* improve setup docs

* publish 1.13.2 client
This commit is contained in:
Maxwell Becker
2024-08-17 18:28:01 -04:00
committed by GitHub
parent 3cded60166
commit 418f359492
8 changed files with 48 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docsite/docs/core-setup.md
View File

@@ -13,11 +13,13 @@ Monitor Core itself can really only run remote builds.
You also have to [**install the Monitor Periphery agent**](/docs/connecting-servers) on your hosts and connect them as **Servers**
in order to alert / deploy etc.
If you only need to connect on one server (the one you are deploying Monitor Core on), you can do it all dockerized,
and use the [all-in-one compose file](https://github.com/mbecker20/monitor/blob/main/config_example/aio.compose.yaml).
This will deploy Monitor Core and Periphery, and automatically add the local periphery as a connected server.
If you **only need to connect on one server** (the one you are deploying Monitor Core on), you can do it all dockerized,
and use the [**all-in-one compose file**](https://github.com/mbecker20/monitor/blob/main/config_example/aio.compose.yaml).
This will deploy Monitor Core and Periphery, and automatically add the local periphery as a connected server.
You can currently and always will be able to **connect as many servers an you like** using the Periphery agent.
Deploying with the AIO compose file **will not** stop you from connecting more servers later, and is really just for setup convenience.
You can currently and always will be able to **connect as many servers an you like** using the Periphery agent.
:::
### Configuration