feat: notify self-hosted users that execution/site logs are unavailable

[ChiragAgg5k]

What

Self-hosted open-source Appwrite no longer stores function/site execution log and error output. This adds an informational notice in the console so users understand why the Logs and Errors sections may appear empty, instead of just seeing "No logs found."

How

• New component src/lib/components/logs/selfHostedLogsAlert.svelte — a product-aware (site | function) Alert.Inline status="info", mirroring the existing loggingAlert.svelte pattern.
• Updated src/lib/components/logs/logsResponse.svelte — the shared component that renders the Logs/Errors tabs for both functions and sites. Imports isSelfHosted from $lib/system and renders the new alert in the Logs and Errors branches when on self-hosted and no output is present (taking precedence over the old LoggingAlert / "No logs found." fallbacks).

Because the Logs/Errors rendering is shared, this single change covers both function executions (functions/.../executions/sheet.svelte) and site logs (sites/.../logs/sheet.svelte).

Behavior

• Shown only on self-hosted builds (isCloud users are unaffected).
• Always shown on self-hosted when there's no log/error output, regardless of the logging toggle, since logs are never persisted there.
• Copy is state-neutral ("...so this section may be empty") so it reads correctly for older executions that legitimately had empty logs, without implying their data was deleted.

Copy

Function:

Execution logs are unavailable on self-hosted Appwrite
To reduce storage overhead, self-hosted Appwrite no longer stores function logs or error output. As a result, this section may be empty. You can still view execution status, duration, and response code. Full execution logs remain available on Appwrite Cloud.

Site:

Logs are unavailable on self-hosted Appwrite
To reduce storage overhead, self-hosted Appwrite no longer stores logs or error output. As a result, this section may be empty. You can still view log status, duration, and response code. Full logs remain available on Appwrite Cloud.

Testing

• bun run format — clean
• bun run lint (eslint on touched files) — clean
• bun run check — no new errors from touched files (pre-existing @appwrite.io/console module-resolution errors are environment-only, SDK not installed locally)

[greptile-apps]

Greptile Summary

Adds a self-hosted informational alert to the shared logsResponse.svelte component so that function and site log sheets show a clear explanation instead of an empty state when running on self-hosted Appwrite (where execution/site logs are no longer persisted).

• New selfHostedLogsAlert.svelte — a Svelte 5 component that renders a product-aware Alert.Inline status="info" for both 'function' and 'site' contexts, correctly following the loggingAlert.svelte pattern.
• logsResponse.svelte — inserts the new alert as the first {:else if isSelfHosted} branch in both the Logs and Errors tabs, which appropriately short-circuits the logging-disabled alert and the generic "No logs found" placeholder on self-hosted builds without affecting cloud users.

Confidence Score: 5/5

Safe to merge — the change is additive, isolated to the shared log response component, and has no effect on cloud users.

Both changed files are narrow and well-scoped. The new component correctly uses Svelte 5 runes syntax consistent with the rest of the already-migrated logsResponse.svelte, the isSelfHosted guard is the established pattern for feature-gating in this codebase, and the branch ordering (self-hosted alert before logging-disabled alert) correctly avoids showing a misleading 'enable logging in settings' message on self-hosted builds where logging cannot persist output regardless.

No files require special attention.

Important Files Changed

Filename	Overview
src/lib/components/logs/selfHostedLogsAlert.svelte	New Svelte 5 component rendering an info alert for self-hosted builds when logs/errors are unavailable; mirrors the pattern of loggingAlert.svelte with correct runes syntax and proper product-conditional copy.
src/lib/components/logs/logsResponse.svelte	Imports isSelfHosted and SelfHostedLogsAlert, inserting the new alert as the first fallback in both the logs and errors branches when no output is present on self-hosted — correctly takes precedence over the logging-disabled alert and the "No logs found" placeholder.

_{Reviews (1): Last reviewed commit: "(feat): notify self-hosted users that ex..." | Re-trigger Greptile}