mirror/komodo
1
0
Fork 0
mirror of https://github.com/moghtech/komodo.git synced 2026-05-20 05:08:37 -05:00
Code Issues Packages Projects Releases Wiki Activity

docs

Browse Source
This commit is contained in:
mbecker20
2024-07-04 19:08:48 -07:00
parent f913be7a0b
commit efa7c13286
2 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docsite/docs/connecting-servers/setup-periphery.md
+1 -1
View File
@@ -1,6 +1,6 @@
# Setup Monitor Periphery
The easiest way to setup periphery is to use the setup script:
The easiest way to setup periphery is to use the setup script (as root user):
```sh
curl -sSL https://raw.githubusercontent.com/mbecker20/monitor/main/scripts/setup-periphery.py | python3
docsite/docs/resources.md
+3 -5
View File
@@ -1,10 +1,8 @@
# Resources
Entities like `Server`, `Deployment`, and `Build` are abstracted under a `Resource`. A server is a type of resource, a build is a type of resource, and so on.
All resources have common traits, such as a globally unique `name` and `id` amongst all other resources of the same resource type.
All resources can also be assigned `tags`, which can be used to group related resources.
For example, they can be grouped by environment (using `dev` or `prod` tags), or by function (`auth` or `ingress`),
or really by any way that fits best for your infra (they are all user defined).
Entities like `Server`, `Deployment`, and `Build` all fall under the `Resource` abstraction. A server is a type of resource, a build is a type of resource, and so on.
All resources have common traits, such as a unique `name` and `id` amongst all other resources of the same resource type.
All resources can be assigned `tags`, which can be used to group related resources.
Here is a list of the resources and their description:
- `Server`: Represents a connected server.