gsadmin/sencho
1
0
Fork 0
mirror of https://github.com/Studio-Saelix/sencho.git synced 2026-07-27 20:29:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(features): wrap troubleshooting accordions in AccordionGroup

Browse Source 
Wraps the loose <Accordion> blocks in editor.mdx and stack-activity.mdx
in a single <AccordionGroup> to match the troubleshooting design used
by fleet-federation.mdx. Structural only; no content changes.
This commit is contained in:
SaelixCode
2026-05-07 16:36:53 -04:00
parent bd25458a26
commit 8ad5bb2e39
2 changed files with 31 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/editor.mdx
+23 -27
View File
@@ -175,30 +175,26 @@ Sencho tries `/bin/bash` first and transparently falls back to `/bin/sh` if bash
## Troubleshooting
<Accordion title="The compose editor is read-only and I can't type">
You have not entered edit mode yet. Click **edit** in the Anatomy panel header (or the **Edit** button at the top of the editor card) to enable typing. If the **Edit** button is missing entirely, your role lacks the `stack:edit` permission; ask an admin to grant it.
</Accordion>
<Accordion title="Save & Deploy is disabled">
A deploy is already running for this stack. Watch the action bar for the spinning state to clear, then save again.
</Accordion>
<Accordion title="The .env tab is greyed out">
The stack has no env file to edit. Add an `env_file:` entry to a service in `compose.yaml` and save, or create a `.env` file in the stack directory through the **Files** tab.
</Accordion>
<Accordion title='"Container is not running" error when opening a bash session'>
The container stopped between clicking the button and the exec starting. Start the container from the action bar (or the row's **Start service** option) and try again.
</Accordion>
<Accordion title='"Failed to start shell" error when opening a bash session'>
The container image has no shell binary at `/bin/bash` or `/bin/sh`. Use an image that includes a shell, or install one in your Dockerfile.
</Accordion>
<Accordion title='Bash session connects but immediately shows "Session ended"'>
The shell process inside the container exited as soon as it started. Check the container logs (the **View logs** button on the same row) for errors; the container's entrypoint may be overriding the shell, or the container itself may be in a crash loop.
</Accordion>
<Accordion title="Bash session is unresponsive">
The WebSocket dropped silently. Close the modal and reopen it to start a fresh session; the bash modal does not reconnect automatically.
</Accordion>
<AccordionGroup>
<Accordion title="The compose editor is read-only and I can't type">
You have not entered edit mode yet. Click **edit** in the Anatomy panel header (or the **Edit** button at the top of the editor card) to enable typing. If the **Edit** button is missing entirely, your role lacks the `stack:edit` permission; ask an admin to grant it.
</Accordion>
<Accordion title="Save & Deploy is disabled">
A deploy is already running for this stack. Watch the action bar for the spinning state to clear, then save again.
</Accordion>
<Accordion title="The .env tab is greyed out">
The stack has no env file to edit. Add an `env_file:` entry to a service in `compose.yaml` and save, or create a `.env` file in the stack directory through the **Files** tab.
</Accordion>
<Accordion title='"Container is not running" error when opening a bash session'>
The container stopped between clicking the button and the exec starting. Start the container from the action bar (or the row's **Start service** option) and try again.
</Accordion>
<Accordion title='"Failed to start shell" error when opening a bash session'>
The container image has no shell binary at `/bin/bash` or `/bin/sh`. Use an image that includes a shell, or install one in your Dockerfile.
</Accordion>
<Accordion title='Bash session connects but immediately shows "Session ended"'>
The shell process inside the container exited as soon as it started. Check the container logs (the **View logs** button on the same row) for errors; the container's entrypoint may be overriding the shell, or the container itself may be in a crash loop.
</Accordion>
<Accordion title="Bash session is unresponsive">
The WebSocket dropped silently. Close the modal and reopen it to start a fresh session; the bash modal does not reconnect automatically.
</Accordion>
</AccordionGroup>
docs/features/stack-activity.mdx
+8 -7
View File
@@ -63,10 +63,11 @@ Sencho attributes every recorded event to the user who was authenticated when th
## Troubleshooting
<Accordion title="The Activity tab shows 'No activity recorded yet'">
The activity log is populated by operations performed through Sencho on this stack: deploys, restarts, starts, stops, and image updates. Trigger one of those actions and the entry appears within a few seconds.
</Accordion>
<Accordion title="Operational events don't appear in the bell notification dropdown">
The notification dropdown surfaces system alerts and error-level events. User-initiated operational events (start, stop, restart, deploy, update) appear exclusively in the per-stack Activity tab, keeping the global tray focused on conditions that need your attention.
</Accordion>
<AccordionGroup>
<Accordion title="The Activity tab shows 'No activity recorded yet'">
The activity log is populated by operations performed through Sencho on this stack: deploys, restarts, starts, stops, and image updates. Trigger one of those actions and the entry appears within a few seconds.
</Accordion>
<Accordion title="Operational events don't appear in the bell notification dropdown">
The notification dropdown surfaces system alerts and error-level events. User-initiated operational events (start, stop, restart, deploy, update) appear exclusively in the per-stack Activity tab, keeping the global tray focused on conditions that need your attention.
</Accordion>
</AccordionGroup>