diff --git a/docs/features/editor.mdx b/docs/features/editor.mdx index 99f77e4a..69ca0161 100644 --- a/docs/features/editor.mdx +++ b/docs/features/editor.mdx @@ -175,30 +175,26 @@ Sencho tries `/bin/bash` first and transparently falls back to `/bin/sh` if bash ## Troubleshooting - -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. - - - -A deploy is already running for this stack. Watch the action bar for the spinning state to clear, then save again. - - - -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. - - - -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. - - - -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. - - - -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. - - - -The WebSocket dropped silently. Close the modal and reopen it to start a fresh session; the bash modal does not reconnect automatically. - + + + 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. + + + A deploy is already running for this stack. Watch the action bar for the spinning state to clear, then save again. + + + 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. + + + 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. + + + 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. + + + 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. + + + The WebSocket dropped silently. Close the modal and reopen it to start a fresh session; the bash modal does not reconnect automatically. + + diff --git a/docs/features/stack-activity.mdx b/docs/features/stack-activity.mdx index afb93677..ee851116 100644 --- a/docs/features/stack-activity.mdx +++ b/docs/features/stack-activity.mdx @@ -63,10 +63,11 @@ Sencho attributes every recorded event to the user who was authenticated when th ## Troubleshooting - -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. - - - -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. - + + + 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. + + + 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. + +