github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-03-08 23:02:40 -05:00
Code Issues 258 Packages Projects Releases 10 Wiki Activity

fix broken docs links before publish

Browse Source
This commit is contained in:
mbecker20
2025-08-17 18:21:01 -07:00
parent 2fa9d9ecce
commit 0ca126ff23
6 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docsite/docs/ecosystem/api.md
View File

@@ -2,7 +2,7 @@
Komodo Core exposes an RPC-like HTTP API to read data, write configuration, and execute actions.
There are typesafe clients available in
[**Rust**](/docs/api#rust-client) and [**Typescript**](/docs/api#typescript-client).
[**Rust**](/docs/ecosystem/api#rust-client) and [**Typescript**](/docs/ecosystem/api#typescript-client).
The full API documentation is [**available here**](https://docs.rs/komodo_client/latest/komodo_client/api/index.html).

2
docsite/docs/intro.md
View File

@@ -43,6 +43,6 @@ Komodo exposes powerful functionality over the Core's REST and Websocket API, en
## Permissioning
Komodo is a system designed to be used by many users, whether they are developers, operations personnel, or administrators. The ability to affect an applications state is very powerful, so Komodo has a granular permissioning system to only provide this functionality to the intended users. The permissioning system is explained in detail in the [permissioning](/docs/permissioning) section.
Komodo is a system designed to be used by many users, whether they are developers, operations personnel, or administrators. The ability to affect an applications state is very powerful, so Komodo has a granular permissioning system to only provide this functionality to the intended users. The permissioning system is explained in detail in the [permissioning](/docs/resources/permissioning) section.
User sign-on is possible using username / password, or with Oauth (Github and Google). See [Core Setup](./setup/index.mdx).

2
docsite/docs/resources/index.md
View File

@@ -10,7 +10,7 @@ Many resources need access to git repos / docker registries. There is an in-buil
All resources which depend on git repos / docker registries are able to use these credentials to access private repos.
:::
## [Server](connect-servers)
## [Server](setup/connect-servers)
- Configure the connection to periphery agents.
- Set alerting thresholds.

2
docsite/docs/resources/permissioning.md
View File

@@ -9,7 +9,7 @@ While Komodo can assign permissions to specific users directly, it is recommende
Users can then be **added to multiple User Groups** and they **inherit the group's permissions**, similar to linux permissions.
There is also an `Everyone` mode for User Groups, if this is enabled then **all users implicitly gain the groups permissions**.
For permissioning at scale, users can define [**User Groups in Resource Syncs**](/docs/sync-resources#user-group).
For permissioning at scale, users can define [**User Groups in Resource Syncs**](/docs/resources/sync-resources#user-group).
## Permission Levels

2
docsite/docs/resources/variables.md
View File

@@ -22,7 +22,7 @@ SOME_ENV_VAR = value_1
- **In the UI**, you can go to `Settings` page, `Variables` tab. Here, you can create some Variables to store in the Komodo database.
- There is a "secret" option you can check, this will **prevent the value from exposure in any updates / logs**, as well as prevent access to the value to any **non-admin** Komodo users.
- Variables can also be managed in ResourceSyncs (see [example](/docs/sync-resources#deployments)) but should only be done for non-secret variables, to avoid committing sensitive data. You should manage secrets using one of the following options.
- Variables can also be managed in ResourceSyncs (see [example](/docs/resources/sync-resources#deployments)) but should only be done for non-secret variables, to avoid committing sensitive data. You should manage secrets using one of the following options.
- **Mount a config file to Core**: https://komo.do/docs/setup/advanced#mount-a-config-file
- In the Komodo Core config file, you can configure `secrets` using a block like:

2
docsite/docs/setup/backup.md
View File

@@ -63,7 +63,7 @@ so you may want to encrypt the files before backing up remotely if your backup s
## Remote Backups
Since database backup is actually a function of the [Komodo CLI](../cli), you can also backup directly to
Since database backup is actually a function of the [Komodo CLI](../ecosystem/cli), you can also backup directly to
a remote server using the `ghcr.io/moghtech/komodo-cli` image. This service will backup once and then exit, so the scheduled deployment should still happen using a Procedure or Action:
```yaml