gsadmin/sencho
1
0
Fork 0
mirror of https://github.com/Studio-Saelix/sencho.git synced 2026-08-27 18:57:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: align Community and Admiral assurance positioning (#1632)

Browse Source 
Reframe docs, OpenAPI registries copy, and License trial/expiry helpers
so Community is the full AGPLv3 product and Admiral leads with current
assurance (Hardened Build, Recovery Vault, support, governance).
Mesh, Secrets, and Host Console stay limited-availability without
Admiral sales framing.
This commit is contained in:
Anso
2026-07-14 19:44:28 -04:00
committed by GitHub
parent 678c198faa
commit 8096799e49
20 changed files with 168 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/host-console.mdx
+4 -5
View File
@@ -6,7 +6,7 @@ description: An interactive terminal on your host OS, directly in the browser -
The **Console** tab opens a full interactive terminal session on the machine running Sencho. It behaves exactly like an SSH session, but without needing an SSH server, client, or key management.
<Note>
The Host Console is a limited-availability operator surface. When it is enabled on an instance, it requires an **Admiral** license and the **admin** role. [Learn more about licensing](/features/licensing).
The Host Console is a limited-availability operator surface. When it is present on an instance, it requires the **admin** role. [Learn more about licensing](/features/licensing).
</Note>
<Frame>
@@ -74,8 +74,7 @@ Environment variables whose names suggest secrets (passwords, tokens, keys, cred
The Host Console is one of the most powerful features in Sencho and is treated as such:
- **Admin role required.** Only users with the **admin** role can open a console session.
- **Admiral license required when enabled.** The Host Console is a limited-availability surface that uses an Admiral license.
- **Admin role required when present.** The Host Console is a limited-availability surface; only users with the **admin** role can open a console session.
- **Browser sessions only.** Console sessions are only available from a signed-in browser session, not from API tokens.
- **Audited.** Every console session is recorded in the audit log. Opening and closing a session each write an entry capturing the user, node, client IP, and timestamp, so shell access is fully accountable.
@@ -98,7 +97,7 @@ The Host Console is one of the most powerful features in Sencho and is treated a
</Accordion>
<Accordion title="Session ends immediately after connecting">
This typically means the shell could not be found on the host. In a Docker deployment, ensure `bash` or `sh` is available inside the container. You can check by running `docker exec <container> which bash` from the host. Also verify that your user has the **admin** role and your instance has an active Admiral license.
This typically means the shell could not be found on the host. In a Docker deployment, ensure `bash` or `sh` is available inside the container. You can check by running `docker exec <container> which bash` from the host. Also verify that your user has the **admin** role and that Console is available on this instance.
</Accordion>
<Accordion title="Connection drops after a short time">
@@ -106,6 +105,6 @@ The Host Console is one of the most powerful features in Sencho and is treated a
</Accordion>
<Accordion title="Console tab is not visible">
Console appears only when the surface is enabled on the instance, and only for users with the **admin** role on an Admiral-licensed instance. Verify those conditions are met. If you recently activated an Admiral license, refresh the page.
Console appears only when the surface is present on the instance, and only for users with the **admin** role. Verify those conditions are met, then refresh the page.
</Accordion>
</AccordionGroup>