fix: remove legacy apps/websocket and apps/tasks, exclude build artifacts from tsconfig

- Remove apps/websocket/ (merged into custom server in server.ts)
- Remove apps/tasks/ (merged into custom server in server.ts)
- Exclude customServer.cjs and customServer.css from tsconfig to prevent
  tsc errors when build artifacts are present
- Update pnpm-lock.yaml (removed 138 unnecessary packages)

Co-authored-by: ajnart <49837342+ajnart@users.noreply.github.com>
Agent-Logs-Url: https://github.com/homarr-labs/homarr/sessions/bd83b347-563b-494e-b8c6-91fcc199dd79

.agents/skills/codebase-context/SKILL.md

@@ -1,195 +0,0 @@
----
-name: codebase-context
-description: Comprehensive Homarr codebase architecture and conventions reference. Use when orienting in the monorepo, understanding package dependency layers, the three runtime services and ports, tRPC router structure, multi-database support, widget/integration/cron system architecture, routing, auth providers, env vars, or key patterns before writing code.
----
-
-# Homarr Codebase Context
-
-Homarr is an open-source, self-hosted dashboard for managing homelab services. It integrates with 50+ self-hosted apps (media servers, download clients, DNS, NAS, etc.) and provides a drag-and-drop widget-based UI.
-
-## Tech Stack
-
-- **Monorepo**: pnpm workspaces + Turborepo
-- **Framework**: Next.js (App Router, `output: "standalone"`) — T3 Stack
-- **Language**: TypeScript throughout
-- **ORM**: Drizzle (supports SQLite via better-sqlite3, MySQL, PostgreSQL)
-- **API**: tRPC (HTTP + WebSocket subscriptions) with superjson + OpenAPI bridge via `trpc-to-openapi`
-- **Auth**: NextAuth v5 (database sessions, Credentials/LDAP/OIDC providers)
-- **UI**: Mantine v9 (not Tailwind) + Tabler icons
-- **State**: Jotai (atoms), TanStack Query (server state via tRPC)
-- **Realtime**: WebSocket server (`ws`) for tRPC subscriptions, backed by Redis pub/sub
-- **Cron**: `node-cron` in a standalone Fastify service (`apps/tasks`)
-- **i18n**: next-intl with `[locale]` dynamic segment (prefix mode: `"never"`, locale from cookie)
-- **Testing**: Vitest + jsdom, Playwright for E2E
-- **Lint/Format**: oxlint + oxfmt (not ESLint/Prettier)
-- **Docs**: Docusaurus 3 in `apps/docs/` (`@homarr/docs`)
-- **Package manager**: pnpm 10.34.1, Node >= 24.16.0
-
-## Repository Structure
-
-```text
-homarr/
-├── apps/
-│   ├── nextjs/          # Main Next.js application (port 3000)
-│   ├── docs/            # Docusaurus 3 documentation site (@homarr/docs)
-│   ├── tasks/           # Cron job runner + Fastify tRPC API (port 3002)
-│   └── websocket/       # Standalone tRPC WebSocket server (port 3001)
-├── packages/
-│   ├── api/             # tRPC appRouter, procedures, OpenAPI
-│   ├── auth/            # NextAuth config, providers, session, API keys
-│   ├── db/              # Drizzle schema (3 DB drivers), migrations, queries
-│   ├── core/            # Env validation, DB/Redis driver factories, logging
-│   ├── definitions/     # Domain enums: WidgetKind, IntegrationKind, permissions
-│   ├── widgets/         # All 39 dashboard widgets (definitions + components)
-│   ├── integrations/    # Integration classes (HTTP clients to external apps)
-│   ├── redis/           # Redis pub/sub channels, caching abstractions
-│   ├── translation/     # next-intl setup, locale configs, lang JSON files
-│   ├── ui/              # Shared Mantine components, theme, hooks
-│   ├── validation/      # Shared zod schemas for API/forms
-│   ├── common/          # Shared utilities, IDs, errors
-│   ├── cron-jobs/       # Cron job implementations (25+ jobs)
-│   ├── cron-jobs-core/  # Cron scheduling primitives
-│   ├── cron-job-api/    # tRPC router for job management (start/stop/trigger)
-│   ├── cron-job-status/ # Cron status via Redis
-│   ├── boards/          # Board context, edit mode, cache updater
-│   ├── modals/          # Modal primitives on Mantine
-│   ├── modals-collection/ # Feature modals (apps, boards, docker, etc.)
-│   ├── form/            # useZodForm (Mantine + zod resolver)
-│   ├── forms-collection/# Reusable form UIs (new app, icon picker, upload)
-│   ├── spotlight/       # Command palette / search with multiple modes
-│   ├── request-handler/ # Server request handlers (feeds, integrations)
-│   ├── notifications/   # Mantine notifications wrapper
-│   ├── docker/          # Dockerode-based Docker access
-│   ├── icons/           # Icon DB/repo integration
-│   ├── image-proxy/     # Image proxy + caching
-│   ├── ping/            # Reachability / ping utilities
-│   ├── analytics/       # Server-side analytics (Umami)
-│   ├── server-settings/ # Server setting keys/types
-│   ├── settings/        # User-facing settings UI context
-│   └── cli/             # Node CLI for ops (brocli)
-├── tooling/
-│   ├── typescript/      # Base tsconfig
-│   └── github/          # CI setup action
-├── development/         # Dev docker-compose (Redis, MySQL, PostgreSQL)
-├── e2e/                 # E2E test specs
-└── Dockerfile           # Multi-stage production build
-```
-
-## Three Runtime Services
-
-| Service   | Port | Role                                         |
-| --------- | ---- | -------------------------------------------- |
-| Next.js   | 3000 | Main web app (SSR + API routes)              |
-| WebSocket | 3001 | tRPC subscriptions via `ws`                  |
-| Tasks     | 3002 | Cron job runner + management API via Fastify |
-
-In Docker, nginx listens on **7575** and proxies to all three. The tasks service authenticates via `CRON_JOB_API_KEY` header.
-
-## Package Dependency Layers
-
-1. **Foundation**: `core` (env, DB drivers, Redis client, logging) → no `@homarr` deps
-2. **Domain**: `definitions` → `common` → `core`
-3. **Data**: `db` → `core`, `definitions`, `common`
-4. **Auth**: `auth` → `db`, `definitions`, `core`, `validation`
-5. **Cross-cutting**: `translation`, `validation`, `redis`, `server-settings`
-6. **Feature backends**: `integrations`, `request-handler`, `cron-jobs`, `docker`, `ping`
-7. **API surface**: `api` → pulls in auth, db, redis, integrations, etc.
-8. **UI stack**: `ui`, `modals`, `form`, `notifications`, `boards`, `spotlight`
-9. **Composed features**: `widgets`, `modals-collection`, `forms-collection`
-
-## Key Patterns
-
-### tRPC
-
-- **Server caller** (RSC): `import { api } from "@homarr/api/server"` → cached caller with auth context
-- **Client hooks**: `import { clientApi } from "@homarr/api/client"` → React Query hooks
-- **Router structure**: `packages/api/src/root.ts` defines top-level namespaces (`user`, `board`, `widget`, `integration`, `docker`, `kubernetes`, etc.)
-- **Procedures**: `publicProcedure`, `protectedProcedure`, `permissionRequiredProcedure`, `onboardingProcedure`
-- **WebSocket subscriptions**: Client uses `wsLink` when `type === "subscription"`, connects to port 3001
-
-### Multi-Database Support
-
-Drizzle schemas exist in three parallel implementations:
-
-- `packages/db/schema/sqlite.ts`
-- `packages/db/schema/mysql.ts`
-- `packages/db/schema/postgresql.ts`
-
-Selected at runtime via `DB_DRIVER` env (`better-sqlite3` | `mysql2` | `node-postgres`). Migrations are per-engine in `packages/db/migrations/{sqlite,mysql,postgresql}/`.
-
-### Widget System
-
-Widgets are registered in `packages/widgets/src/index.tsx` as `widgetImports` (must satisfy `Record<WidgetKind, ...>`). Each widget:
-
-- Has a `definition` created via `createWidgetDefinition(kind, { icon, createOptions, supportedIntegrations? })`
-- Uses `optionsBuilder.from(factory => ({ ... }))` for typed options
-- Loads dynamically via `next/dynamic`
-- Fetches data via tRPC client hooks (backed by cron job caches)
-
-### Integration System
-
-Integrations are defined in `packages/definitions/src/integration.ts` (`integrationDefs`) and instantiated via `createIntegrationAsync` in `packages/integrations/src/base/creator.ts`. Each extends abstract `Integration` class with `testConnectionAsync` and typed methods.
-
-### Cron Job System
-
-Jobs defined in `packages/cron-jobs/src/jobs/`. Each job:
-
-- Uses `createCronJob` with a cron expression
-- Publishes results to Redis channels
-- Widget subscriptions consume those channels via tRPC subscriptions
-- Job management (start/stop/trigger) via `cronJobApi` HTTP client to port 3002
-
-### Modals
-
-Created with `createModal(component).withOptions({ defaultTitle })` from `@homarr/modals`. Opened via `useModalAction(SomeModal)`. Feature modals live in `packages/modals-collection/`.
-
-### Forms
-
-`useZodForm` from `@homarr/form` wraps Mantine `useForm` with zod validation. Shared form UIs in `packages/forms-collection/`.
-
-### Routing (App Router)
-
-- `apps/nextjs/src/app/[locale]/` — all UI routes under locale segment
-- Route groups: `(home)`, `(content)`, `(board)` — don't affect URLs
-- Key routes: `boards/[name]`, `manage/...` (admin), `auth/login`, `init` (onboarding), `widgets/[kind]`
-- Locale driven by cookie (no URL prefix)
-
-### Auth Providers
-
-Configured via `AUTH_PROVIDERS` env. Supports: `credentials` (local), `ldap`, `oidc`. Database sessions with httpOnly cookies. API key auth for programmatic access.
-
-## Environment Variables
-
-Key env vars (from `.env.example`):
-
-- `DB_DRIVER`: `better-sqlite3` | `mysql2` | `node-postgres`
-- `DB_URL`: Database connection string
-- `AUTH_SECRET`: NextAuth secret
-- `SECRET_ENCRYPTION_KEY`: AES-256-CBC for integration secrets
-- `AUTH_PROVIDERS`: Comma-separated (`credentials`, `ldap`, `oidc`)
-- `CRON_JOB_API_KEY`: Shared key between Next.js and tasks service
-- `REDIS_*`: Redis connection (host, port, password)
-- `ENABLE_KUBERNETES`: Optional Kubernetes integration
-
-## Development Commands
-
-- `pnpm dev` — runs all three services in parallel via Turborepo
-- `pnpm docker:dev` — starts Redis + MySQL + PostgreSQL containers
-- `pnpm db:push` — push schema to SQLite (dev)
-- `pnpm db:studio` — Drizzle Studio
-- `pnpm test` — Vitest unit tests
-- `pnpm test:e2e` — Playwright E2E
-- `pnpm lint` / `pnpm format` — oxlint + oxfmt
-- `pnpm dev:docs` — Docusaurus docs site (port 3003)
-- `pnpm typecheck` — tsc --noEmit across all packages
-
-## Conventions
-
-- Workspace packages use `@homarr/` scope
-- All versions managed via pnpm `catalog:` in workspace
-- Path alias `~/*` → `./src/*` in Next.js app
-- Mantine for all UI (no Tailwind) — primary color is red, `autoContrast: true`
-- Icons from `@tabler/icons-react`
-- Drag-and-drop via `@dnd-kit/*`
-- `typescript.ignoreBuildErrors: true` in next.config (types checked separately via `typecheck`)
-- `serverExternalPackages`: `dockerode`, `isomorphic-dompurify`, `jsdom`

.agents/skills/datatable-migration/SKILL.md

@@ -1,691 +0,0 @@
----
-name: datatable-migration
-description: Playbook for migrating tables from mantine-react-table (MRT) to mantine-datatable. Use when converting any table component from mantine-react-table to mantine-datatable, working on DataTable column/sort/expansion/context-menu code, or implementing responsive column visibility, column persistence, or transparent tables in widgets.
----
-
-# Migrating Tables from mantine-react-table to mantine-datatable
-
-This document captures every pattern, fix, and decision from the downloads widget rework (PR #6430). Use it as a playbook when porting other tables.
-
-## Migration Candidates
-
-Current `mantine-react-table` consumers that could be migrated:
-
-**Widgets (in `packages/widgets/`):**
-
-- `docker/component.tsx` — Docker container table
-- `media-server/component.tsx` — Media server sessions
-
-**Admin pages (in `apps/nextjs/src/app/[locale]/manage/`):**
-
-- `tools/docker/docker-table.tsx`
-- `tools/tasks/_components/tasks-table.tsx`
-- `tools/api/components/api-keys.tsx`
-- `users/_components/user-list.tsx`
-- `users/invites/_components/invite-list.tsx`
-- `tools/kubernetes/` — 8 Kubernetes resource tables
-
-**Modals:**
-
-- `packages/modals-collection/src/search-engines/request-media-modal.tsx`
-
-**Shared hook to remove once all migrated:**
-
-- `packages/ui/src/hooks/use-translated-mantine-react-table.ts`
-
-## 1. Core Migration: mantine-react-table → mantine-datatable
-
-### Import changes
-
-```typescript
-// BEFORE
-import { MantineReactTable, useMantineReactTable } from "mantine-react-table";
-import type { MRT_ColumnDef } from "mantine-react-table";
-
-// AFTER
-import { DataTable, useDataTableColumns } from "mantine-datatable";
-import type { DataTableColumn, DataTableSortStatus } from "mantine-datatable";
-```
-
-### Column definition shape
-
-```typescript
-// BEFORE (MRT)
-const columns: MRT_ColumnDef<MyRow>[] = [
-  {
-    accessorKey: "name",
-    header: "Name",
-    size: 200,
-    enableSorting: true,
-    Cell: ({ row }) => <Text>{row.original.name}</Text>,
-  },
-];
-
-// AFTER (mantine-datatable)
-const columns: DataTableColumn<MyRow>[] = [
-  {
-    accessor: "name",           // not accessorKey
-    title: "Name",              // not header
-    width: 200,                 // not size
-    sortable: true,             // not enableSorting
-    render: (record) => <Text>{record.name}</Text>,  // not Cell
-  },
-];
-```
-
-Key differences:
-
-- `accessorKey` → `accessor`
-- `header` → `title`
-- `size` → `width`
-- `Cell: ({ row }) =>` → `render: (record) =>`
-- `enableSorting` → `sortable`
-- `enableColumnActions` → does not exist (no column action menus)
-- `mantineTableBodyCellProps` → `cellsStyle` in `defaultColumnProps`
-
-### Table component
-
-```typescript
-// BEFORE
-const table = useTranslatedMantineReactTable({ columns, data, ... });
-return <MantineReactTable table={table} />;
-
-// AFTER
-return (
-  <DataTable
-    records={data}
-    columns={columns}
-    sortStatus={sortStatus}
-    onSortStatusChange={setSortStatus}
-    ...
-  />
-);
-```
-
-### Sorting is manual
-
-mantine-datatable does NOT sort for you. You must sort the data yourself:
-
-```typescript
-const [sortStatus, setSortStatus] = useState<DataTableSortStatus<MyRow>>({
-  columnAccessor: "name",
-  direction: "asc",
-});
-
-const sortedData = useMemo(() => {
-  const mult = sortStatus.direction === "desc" ? -1 : 1;
-  return [...data].toSorted((a, b) => {
-    const aVal = a[sortStatus.columnAccessor];
-    const bVal = b[sortStatus.columnAccessor];
-    if (typeof aVal === "string") return aVal.localeCompare(bVal as string) * mult;
-    return ((aVal as number) - (bVal as number)) * mult;
-  });
-}, [data, sortStatus]);
-
-// Pass sortedData to records, not data
-<DataTable records={sortedData} sortStatus={sortStatus} onSortStatusChange={setSortStatus} />
-```
-
-## 2. Making Tables Transparent (Widget Context)
-
-Widgets sit inside board cards that have user-controlled opacity. The table must be fully transparent so the card background shows through. mantine-datatable defaults to `var(--mantine-color-body)` which is opaque.
-
-Create a CSS file alongside the component:
-
-```css
-/* styles.css */
-.my-table,
-.my-table .mantine-datatable-table,
-.my-table .mantine-datatable-table thead,
-.my-table .mantine-datatable-table tbody,
-.my-table .mantine-datatable-table tfoot,
-.my-table th,
-.my-table td {
-  background-color: transparent !important;
-}
-
-.my-table .mantine-datatable-table tr {
-  background-color: transparent;
-}
-
-/* Hover: translucent instead of opaque */
-.my-table .mantine-datatable-table tbody tr:hover {
-  background-color: color-mix(
-    in srgb,
-    var(--mantine-color-default-hover) 40%,
-    transparent
-  ) !important;
-}
-
-/* Headers: frosted glass effect */
-.my-table th {
-  white-space: nowrap;
-  background-color: color-mix(
-    in srgb,
-    var(--mantine-color-body) 60%,
-    transparent
-  ) !important;
-  backdrop-filter: blur(8px);
-}
-
-/* Cell overflow */
-.my-table td {
-  white-space: nowrap;
-  overflow: hidden;
-  text-overflow: ellipsis;
-}
-
-/* Hide sort icon until hover */
-.my-table .mantine-datatable-header-cell-sortable-icon {
-  opacity: 0;
-  transition: opacity 150ms;
-}
-.my-table th:hover .mantine-datatable-header-cell-sortable-icon {
-  opacity: 1;
-}
-
-/* Row expansion area */
-.my-table .mantine-datatable-row-expansion-cell {
-  background-color: color-mix(
-    in srgb,
-    var(--mantine-color-body) 40%,
-    transparent
-  ) !important;
-}
-```
-
-Import it: `import "./styles.css";` and apply via `className="my-table"`.
-
-## 3. Responsive Column Visibility
-
-Use a lookup table of width breakpoints instead of media queries. The widget receives `width` as a prop.
-
-```typescript
-interface SizeConfig {
-  fontSize: "xs" | "sm";
-  iconSize: number;
-  cellPadding: number;
-  showSpeedColumns: boolean;
-  showTimeColumn: boolean;
-  showStateColumn: boolean;
-}
-
-const SIZE_BREAKPOINTS: { maxWidth: number; config: SizeConfig }[] = [
-  {
-    maxWidth: 300,
-    config: {
-      fontSize: "xs",
-      iconSize: 12,
-      cellPadding: 2,
-      showSpeedColumns: false,
-      showTimeColumn: false,
-      showStateColumn: false,
-    },
-  },
-  {
-    maxWidth: 500,
-    config: {
-      fontSize: "xs",
-      iconSize: 14,
-      cellPadding: 4,
-      showSpeedColumns: false,
-      showTimeColumn: true,
-      showStateColumn: false,
-    },
-  },
-];
-
-const DEFAULT_SIZE_CONFIG: SizeConfig = {
-  fontSize: "sm",
-  iconSize: 14,
-  cellPadding: 4,
-  showSpeedColumns: true,
-  showTimeColumn: true,
-  showStateColumn: true,
-};
-
-function getSizeConfig(width: number): SizeConfig {
-  for (const { maxWidth, config } of SIZE_BREAKPOINTS) {
-    if (width < maxWidth) return config;
-  }
-  return DEFAULT_SIZE_CONFIG;
-}
-
-// Usage: memoize it
-const size = useMemo(() => getSizeConfig(width), [width]);
-```
-
-Then use a visibility check lookup table for columns:
-
-```typescript
-const columnVisibilityChecks: Partial<
-  Record<string, (ctx: ColumnContext) => boolean>
-> = {
-  upSpeed: (ctx) => ctx.hasTorrents && ctx.size.showSpeedColumns,
-  downSpeed: (ctx) => ctx.size.showSpeedColumns,
-  time: (ctx) => ctx.size.showTimeColumn,
-  state: (ctx) => ctx.size.showStateColumn,
-};
-
-function shouldIncludeColumn(accessor: string, ctx: ColumnContext): boolean {
-  if (!ctx.optionsColumnSet.has(accessor)) return false;
-  const check = columnVisibilityChecks[accessor];
-  if (check && !check(ctx)) return false;
-  return true;
-}
-```
-
-## 4. Column Persistence (Drag/Resize → Server)
-
-`useDataTableColumns` stores column order and widths in localStorage by default. For widgets, this must persist server-side so it works across devices.
-
-### Hidden widget options
-
-In `index.ts`, add hidden text options:
-
-```typescript
-columnOrder: factory.text({ defaultValue: "" }),
-columnWidths: factory.text({ defaultValue: "" }),
-```
-
-With visibility override:
-
-```typescript
-{
-  columnOrder: { shouldHide: () => true },
-  columnWidths: { shouldHide: () => true },
-}
-```
-
-### Translation keys required
-
-Even hidden options need translation keys or the translation test fails:
-
-```json
-"widget.mywidget.option.columnOrder.label": "Column order",
-"widget.mywidget.option.columnWidths.label": "Column widths"
-```
-
-### Dynamic storeKey
-
-Use a key that includes `itemId` and sorted column names. This prevents cross-widget localStorage bleeding:
-
-```typescript
-const storeKey = `mytable-${itemId ?? "preview"}-${[...options.columns].toSorted().join(",")}`;
-```
-
-### Hydration from server → localStorage
-
-On mount, seed `useDataTableColumns` with server-persisted values. Use a `hydrated` ref to prevent the persist effect from immediately writing defaults back:
-
-```typescript
-const {
-  effectiveColumns,
-  columnsOrder,
-  columnsWidth,
-  setColumnsOrder,
-  setMultipleColumnWidths,
-} = useDataTableColumns<MyRow>({ key: storeKey, columns });
-
-const lastStoreKey = useRef(storeKey);
-const hydrated = useRef(false);
-
-useEffect(() => {
-  if (lastStoreKey.current !== storeKey) {
-    lastStoreKey.current = storeKey;
-    hydrated.current = false;
-  }
-  if (hydrated.current) return;
-  if (savedOrder.length > 0) setColumnsOrder(savedOrder);
-  if (Object.keys(savedWidths).length > 0) {
-    setMultipleColumnWidths(
-      Object.entries(savedWidths).map(([accessor, w]) => ({
-        accessor,
-        width: w,
-      })),
-    );
-  }
-  requestAnimationFrame(() => {
-    hydrated.current = true;
-  });
-}, [
-  storeKey,
-  savedOrder,
-  savedWidths,
-  setColumnsOrder,
-  setMultipleColumnWidths,
-]);
-```
-
-### Persist localStorage → server
-
-Watch for changes and write back:
-
-```typescript
-const prevOrder = useRef(columnsOrder);
-const prevWidths = useRef(columnsWidth);
-
-useEffect(() => {
-  if (!hydrated.current) return;
-  const orderChanged =
-    JSON.stringify(columnsOrder) !== JSON.stringify(prevOrder.current);
-  const widthsChanged =
-    JSON.stringify(columnsWidth) !== JSON.stringify(prevWidths.current);
-  prevOrder.current = columnsOrder;
-  prevWidths.current = columnsWidth;
-
-  if (!orderChanged && !widthsChanged) return;
-
-  if (orderChanged)
-    persistOption({ columnOrder: JSON.stringify(columnsOrder) });
-  if (widthsChanged) {
-    const widthMap: Record<string, number> = {};
-    for (const entry of columnsWidth) {
-      const key = Object.keys(entry)[0];
-      if (!key) continue;
-      const v = entry[key as keyof typeof entry];
-      if (typeof v === "number") widthMap[key] = v;
-      else if (typeof v === "string" && v.endsWith("px"))
-        widthMap[key] = parseInt(v, 10);
-    }
-    persistOption({ columnWidths: JSON.stringify(widthMap) });
-  }
-}, [columnsOrder, columnsWidth, persistOption]);
-```
-
-The `persistOption` helper calls both `setOptions` (local state) and `saveItemOptions` (server mutation).
-
-## 5. Context Menu (Right-Click)
-
-Do NOT install `mantine-contextmenu`. Use Mantine's `Menu` + `Portal` directly:
-
-```typescript
-interface ContextMenuState {
-  x: number;
-  y: number;
-  item: MyRow;
-}
-
-const [contextMenu, setContextMenu] = useState<ContextMenuState | null>(null);
-
-const handleContextMenu = useCallback(
-  ({ record, event }: { record: MyRow; event: React.MouseEvent }) => {
-    event.preventDefault();
-    setContextMenu({ x: event.clientX, y: event.clientY, item: record });
-  },
-  [],
-);
-
-// On DataTable:
-<DataTable onRowContextMenu={handleContextMenu} />
-
-// Render:
-{contextMenu && <RowContextMenu state={contextMenu} onClose={closeContextMenu} />}
-```
-
-The menu component uses `Portal` for correct z-index:
-
-```tsx
-function RowContextMenu({
-  state,
-  onClose,
-}: {
-  state: ContextMenuState;
-  onClose: () => void;
-}) {
-  return (
-    <Portal>
-      <Menu
-        opened
-        onClose={onClose}
-        closeOnItemClick={false}
-        position="right-start"
-        offset={0}
-      >
-        <Menu.Target>
-          <Box
-            style={{
-              position: "fixed",
-              left: state.x,
-              top: state.y,
-              width: 0,
-              height: 0,
-            }}
-          />
-        </Menu.Target>
-        <Menu.Dropdown>
-          <Menu.Item
-            onClick={() => {
-              /* action */ onClose();
-            }}
-          >
-            Action
-          </Menu.Item>
-        </Menu.Dropdown>
-      </Menu>
-    </Portal>
-  );
-}
-```
-
-**Key fix:** Use `closeOnItemClick={false}` if any menu item needs a two-step confirmation (like delete → confirm). Close the menu on scroll: `onScroll={() => { if (contextMenu) closeContextMenu(); }}`.
-
-## 6. Row Expansion
-
-```typescript
-<DataTable
-  rowExpansion={{
-    trigger: "click",
-    allowMultiple: true,
-    collapseProps: {
-      transitionDuration: 200,
-      animateOpacity: true,
-      transitionTimingFunction: "ease-out",
-    },
-    content: ({ record, collapse }) => <ExpandedRow item={record} collapse={collapse} />,
-  }}
-/>
-```
-
-**Critical:** Do NOT set `onRowClick` when using `rowExpansion` with `trigger: "click"`. They conflict and the expansion won't work.
-
-## 7. Common Pitfalls & Fixes
-
-### Status indicator dots
-
-Don't use `<Badge variant="dot" />` without children — it renders a pill with empty space. Use a plain `Box`:
-
-```tsx
-<Box
-  w={8}
-  h={8}
-  style={{
-    borderRadius: "50%",
-    backgroundColor: `var(--mantine-color-${color}-filled)`,
-    flexShrink: 0,
-  }}
-/>
-```
-
-### Tooltip overflow on long text columns
-
-When a column has `ellipsis: true`, the tooltip target element can still extend beyond the cell bounds if inner elements don't clip. Fix:
-
-```tsx
-<Tooltip position="bottom-start" ...>
-  <Group style={{ overflow: "hidden" }}>
-    ...
-  </Group>
-</Tooltip>
-```
-
-Use `position="bottom-start"` instead of `position="right"` so the tooltip never escapes the widget horizontally.
-
-### Dark mode tooltips
-
-Mantine tooltips default to the theme's tooltip color which may be white in light mode and stay white in dark mode. Always set `color="dark"` on informational tooltips inside widgets.
-
-### Division by zero
-
-Guard all ratio calculations:
-
-```typescript
-if (item.size > 0) ratio = item.sent / item.size;
-if (totalDown > 0) ratio = totalUp / totalDown;
-```
-
-### Composite idAccessor
-
-When rows can come from multiple integrations, IDs may collide. Use a composite key:
-
-```typescript
-idAccessor={(record) => `${record.integration.id}:${record.id}`}
-```
-
-### JSON option parsing
-
-Always wrap in try/catch:
-
-```typescript
-function parseJsonOption<T>(value: string | undefined, fallback: T): T {
-  if (!value) return fallback;
-  try {
-    return JSON.parse(value) as T;
-  } catch {
-    return fallback;
-  }
-}
-```
-
-### Clipboard API
-
-`navigator.clipboard.writeText()` can throw in non-HTTPS contexts. Always catch:
-
-```typescript
-void navigator.clipboard.writeText(text).catch(() => {});
-```
-
-### Sync sortStatus with widget options
-
-If the widget has configurable default sort, sync it:
-
-```typescript
-useEffect(() => {
-  setSortStatus({
-    columnAccessor: options.defaultSort,
-    direction: defaultSortDirection,
-  });
-}, [options.defaultSort, defaultSortDirection]);
-```
-
-## 8. Accessibility
-
-- All `ActionIcon` components need `aria-label`
-- Filter toggles (client badges, status badges) need `aria-pressed={isActive}`
-- `textSelectionDisabled` on DataTable prevents accidental text selection during drag/resize
-
-## 9. Error Handling
-
-- Every mutation needs an `onError` callback with `showErrorNotification`
-- The `saveItemOptions` mutation (column persistence) also needs `onError`
-- Check `isError` on the main query and show a fallback UI
-- Use a shared `mutationOptions` object to avoid repeating `onSettled`/`onError`:
-
-```typescript
-const mutationOptions = {
-  onSettled: () => void utils.myQuery.invalidate(),
-  onError: () =>
-    showErrorNotification({
-      title: t("errors.actionFailed"),
-      message: t("errors.actionFailedMessage"),
-    }),
-};
-```
-
-## 10. i18n
-
-- No hardcoded strings. Every user-visible string goes through `useScopedI18n`
-- Column titles: `t("items.{accessor}.columnTitle")`
-- Detail labels: `t("items.{accessor}.detailsTitle")`
-- States: `t("states.{state}")`
-- Actions: `t("actions.{action}")`
-- Errors: `t("errors.{errorKey}")`
-- Hidden options still need `.label` translation keys
-
-## 11. Edit Mode
-
-Disable pointer events on the table during edit mode to prevent conflicts with the board's drag-and-drop:
-
-```typescript
-let tablePointerEvents: React.CSSProperties["pointerEvents"];
-if (isEditMode) tablePointerEvents = "none";
-
-let rowContextMenuHandler = handleContextMenu;
-if (isEditMode) rowContextMenuHandler = undefined;
-
-<DataTable style={{ pointerEvents: tablePointerEvents }} />
-```
-
-## 12. DataTable Props Reference (Commonly Used)
-
-```typescript
-<DataTable
-  records={sortedData}
-  columns={effectiveColumns}
-  storeColumnsKey={storeKey}
-  withTableBorder={false}
-  borderRadius={0}
-  highlightOnHover
-  striped="odd"
-  stripedColor={{ dark: "dark.7", light: "gray.0" }}
-  highlightOnHoverColor={{ dark: "dark.5", light: "gray.1" }}
-  verticalAlign="center"
-  fetching={isFetching && data.length === 0}
-  loaderBackgroundBlur={2}
-  fz={size.fontSize}
-  textSelectionDisabled
-  sortStatus={sortStatus}
-  onSortStatusChange={setSortStatus}
-  noRecordsText={t("errors.noItems")}
-  idAccessor={(record) => record.uniqueKey}
-  height="100%"
-  className="my-table"
-  defaultColumnProps={{
-    noWrap: true,
-    draggable: true,
-    resizable: true,
-    cellsStyle: () => ({ padding: `${size.cellPadding}px 8px` }),
-  }}
-  scrollAreaProps={{ type: "auto", scrollbarSize: 6 }}
-  rowBackgroundColor={(record) => conditionalBgMap[record.state]}
-  onRowContextMenu={handleContextMenu}
-  rowExpansion={{ ... }}
-  onScroll={() => { if (contextMenu) closeContextMenu(); }}
-/>
-```
-
-## 13. Layout Stability
-
-- Don't use `table-layout: fixed` — it fights mantine-datatable's resize logic
-- Give non-name columns explicit `width` values so only the name column flexes
-- Use `ellipsis: true` on the name column — it handles `text-overflow: ellipsis` internally
-- Names should truncate at the cell boundary, not a character count, so the layout is stable regardless of content length
-- `flexShrink: 0` on badges/icons prevents them from being squeezed by long names
-
-## 14. Checklist for Each Migration
-
-1. Replace imports (`mantine-react-table` → `mantine-datatable`)
-2. Convert column definitions (`accessorKey` → `accessor`, `header` → `title`, `Cell` → `render`, etc.)
-3. Implement manual sorting with `useState` + `useMemo`
-4. Add CSS file for transparent backgrounds (if widget context)
-5. Add responsive column visibility (if widget context)
-6. Add hidden options + hydration logic (if column persistence needed)
-7. Add translation keys (including hidden option labels)
-8. Add context menu if row actions exist
-9. Add row expansion if detail view exists
-10. Add error handling on all mutations
-11. Add accessibility attributes
-12. Test at multiple widget widths
-13. Update docs in `apps/docs/docs/widgets/` if applicable
-14. Run `pnpm turbo typecheck`
-15. Run translation spec — catches missing keys

.agents/skills/documentation-sync/SKILL.md

@@ -1,44 +0,0 @@
----
-name: documentation-sync
-description: Keep Homarr documentation in sync with code changes. Use when modifying code that affects user-facing behavior, or when adding/modifying widgets, integrations, cron jobs, API routes, env vars, permissions, auth providers, or UI in apps/docs. Covers the docs/ mapping table, integration doc pattern, and widget doc pattern.
----
-
-# Documentation Sync
-
-When modifying code that affects user-facing behavior, you MUST also update the documentation in `apps/docs/`.
-
-## What triggers a doc update
-
-| Code change            | Doc location                                                |
-| ---------------------- | ----------------------------------------------------------- |
-| New integration        | `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts` |
-| New widget             | `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts`      |
-| Changed API surface    | `apps/docs/docs/management/api.mdx`                         |
-| New/changed env vars   | `apps/docs/docs/advanced/`                                  |
-| New CLI commands       | `apps/docs/docs/advanced/command-line/`                     |
-| Changed auth providers | `apps/docs/docs/advanced/` SSO pages                        |
-| UI/UX changes          | Relevant getting-started or management pages                |
-| New cron job           | `apps/docs/docs/management/tasks.mdx`                       |
-| Changed permissions    | `apps/docs/docs/management/users.mdx`                       |
-
-## Integration doc pattern
-
-Each integration has a folder under `apps/docs/docs/integrations/<slug>/`:
-
-- `index.ts` — exports a typed `IntegrationDefinition` with name, description, iconUrl, path
-- `index.mdx` — uses shared components: `IntegrationHeader`, `IntegrationCapabilites`, `IntegrationSecrets`
-- Import metadata from `@homarr/definitions` where possible
-
-## Widget doc pattern
-
-Each widget has a folder under `apps/docs/docs/widgets/<slug>/`:
-
-- `index.ts` — exports a typed `WidgetDefinition` with icon, name, description, path, configuration
-- `index.mdx` — uses shared components: `WidgetHeader`, `WidgetConfig`, `WidgetAdding`
-
-## Development
-
-- Run docs locally: `pnpm dev:docs` from root
-- Build docs: `pnpm turbo build --filter=@homarr/docs`
-- The docs app can import from `@homarr/definitions` for type-safe integration/widget metadata
-- Docusaurus strict mode throws on broken links — fix any broken references before committing

.agents/skills/mcp-integration/SKILL.md

@@ -1,110 +0,0 @@
----
-name: mcp-integration
-description: Expose tRPC procedures as MCP tools for AI clients. Use when modifying procedures in packages/api/src/router, adding a new tRPC procedure or router, or deciding what to expose via Homarr's MCP interface. Covers .meta({ mcp }), router registration in packages/api/src/mcp.ts, input schema rules, and what to expose vs skip.
----
-
-# MCP Integration
-
-Every new tRPC procedure that provides useful functionality should be exposed as an MCP tool so AI assistants (Claude, Cursor, etc.) can use it. This is a first-class feature of Homarr.
-
-Exposing a procedure makes it callable by any AI client with an API key. Before adding `.meta({ mcp })`, review what the tool exposes: authorization requirements, sensitive data, tenant isolation, auditability, and whether the action is destructive. Prefer exposing read-only queries over mutations unless the mutation is safe and permission-scoped. When in doubt, ask for a security review before shipping a new MCP tool.
-
-## Adding MCP to a procedure
-
-Add `.meta({ mcp: { enabled: true, description: "..." } })` to the procedure chain:
-
-```typescript
-// Read-only tool (query)
-myProcedure: protectedProcedure
-  .meta({ mcp: { enabled: true, description: "Get all items with their status and metadata" } })
-  .input(z.object({ limit: z.number().default(10) }))
-  .query(async ({ ctx, input }) => { ... })
-
-// Write tool (mutation)
-myAction: protectedProcedure
-  .meta({ mcp: { enabled: true, description: "Delete an item by ID. Requires interact permission on the integration" } })
-  .input(z.object({ id: z.string() }))
-  .mutation(async ({ ctx, input }) => { ... })
-
-// No-input procedure (z.void) — works fine, no .input() needed
-getAll: protectedProcedure
-  .meta({ mcp: { enabled: true, description: "List all resources" } })
-  .query(async ({ ctx }) => { ... })
-```
-
-The `.meta()` call must come **before** `.input()` and `.query()`/`.mutation()` in the chain.
-
-## Writing good descriptions
-
-The description is the **only thing** an AI sees to decide when and how to use the tool. Write it like you're explaining to a colleague who has never used Homarr.
-
-**Must include:**
-
-- What the tool returns or does
-- Which integrations/services it works with (if applicable)
-- How to get required IDs (e.g., "Use integration_all to get the integrationId")
-- Permission requirements (if non-obvious)
-
-**Good:**
-
-```text
-"Get calendar events for upcoming and recent media releases. Fetches from all connected Sonarr (TV), Radarr (movies), Lidarr (music), and Readarr (books) integrations. Requires integrationIds from integration_all"
-```
-
-**Bad:**
-
-```text
-"Get calendar events"
-```
-
-**For tools that return permission fields**, explain what they mean:
-
-```text
-"List all integrations. Returns permissions.hasUseAccess (read) and permissions.hasInteractAccess (actions) — false means the API key lacks that permission, not an error"
-```
-
-## Registering in the MCP router
-
-After adding `.meta()` to procedures, you must register the router in `packages/api/src/mcp.ts`. This file uses **eager imports** (no `lazy()`) because MCP tool extraction requires synchronous access to all procedure definitions.
-
-```typescript
-// packages/api/src/mcp.ts
-import { myNewRouter } from "./router/my-new-feature";
-
-export const mcpRouter = createTRPCRouter({
-  // ... existing routers
-  myFeature: myNewRouter,
-});
-```
-
-**If your router is nested** (e.g., widget sub-routers), import and register the sub-router directly — do not import a parent that uses `lazy()`.
-
-## What to expose vs. what to skip
-
-**Expose:**
-
-- Data queries (list, search, get by ID)
-- Actions users would ask an AI to do (toggle, create, delete, approve)
-- Status checks (health, stats, summaries)
-
-**Skip:**
-
-- Subscriptions (WebSocket-only, not supported by MCP)
-- Internal procedures (session management, onboarding steps)
-- File upload/download procedures
-- Procedures that return non-serializable data (streams, blobs)
-
-## Input schema rules
-
-- Use `z.object({...})` for inputs — this maps cleanly to MCP tool parameters
-- `z.void()` (no `.input()`) works — the MCP handler patches these to accept empty objects
-- Avoid `z.union()` or `z.discriminatedUnion()` at the top level — AI clients struggle with these
-- Use `.default()` on optional fields so the AI doesn't need to guess values
-
-## Checklist for new features
-
-1. Add `.meta({ mcp: { enabled: true, description: "..." } })` to relevant procedures
-2. Import and register the router in `packages/api/src/mcp.ts` (eager, no lazy)
-3. Write descriptions that explain what the tool does, what it needs, and what it returns
-4. If the tool requires an ID from another tool, say which one in the description
-5. Test with `curl` against `/api/mcp/mcp` to verify the tool appears in `tools/list`

.claude/skills

@@ -1 +0,0 @@
-../.agents/skills

.deepsource.toml

@@ -3,6 +3,9 @@ version = 1
 [[analyzers]]
 name = "javascript"
 
-[analyzers.meta]
-plugins = ["react"]
-environment = ["nodejs"]
+  [analyzers.meta]
+  plugins = ["react"]
+  environment = ["nodejs"]
+
+[[transformers]]
+name = "prettier"

.dockerignore

@@ -6,20 +6,7 @@ npm-debug.log
 README.md
 .next
 .turbo
-.pnpm-store
-**/.pnpm-store
-coverage
-**/coverage
-**/.docusaurus
-**/build
 .git
-.github
 dev
 .build
-e2e
-apps/docs/*
-!apps/docs/package.json
-apps/nextjs/.next
-.env
-.env.*
-!.env.example
+e2e

.env.example

@@ -12,6 +12,10 @@ AUTH_SECRET="supersecret"
 # or starting the project without any (which will show a randomly generated one).
 SECRET_ENCRYPTION_KEY=0000000000000000000000000000000000000000000000000000000000000000
 
+# Cron job API key is generated every time the container starts as it is required for communication between nextjs-api and tasks-api
+# export CRON_JOB_API_KEY=$(openssl rand -base64 32)
+# CRON_JOB_API_KEY="your-generated-api-key"
+
 LOG_LEVEL='info'
 
 # This is how you can use the sqlite driver:
@@ -41,29 +45,8 @@ DB_URL='FULL_PATH_TO_YOUR_SQLITE_DB_FILE'
 
 TURBO_TELEMETRY_DISABLED=1
 
-# Turborepo remote cache (optional, for faster CI/local builds)
-# Uncomment and fill in to enable remote caching locally.
-# CI uses GitHub secrets for these values automatically.
-# TURBO_API=https://your-cache-worker.workers.dev
-# TURBO_TEAM=team_your_team
-# TURBO_TOKEN=your-turbo-token
-# TURBO_REMOTE_CACHE_SIGNATURE_KEY=your-signature-key
-
-# Comma-separated paths to Docker-compatible Unix sockets.
-# Useful for connecting to multiple runtimes (Docker + Podman) simultaneously.
-# When unset and no TCP hosts configured, defaults to /var/run/docker.sock.
-# Example: DOCKER_SOCKET_PATHS=/var/run/docker.sock,/run/user/1000/podman/podman.sock
-# DOCKER_SOCKET_PATHS=
-
 # Enable kubernetes tool
 # ENABLE_KUBERNETES=true
 
 # Enable mock integration
-UNSAFE_ENABLE_MOCK_INTEGRATION=true
-
-# Enable demo mode (seeds a demo user "demo"/"demo", a sample board and a mock integration)
-# DEMO_MODE=true
-
-# Whether demo mode is read-only. Defaults to true (the public demo blocks all mutations).
-# Set to false for writable preview deployments so the demo user can modify the dashboard.
-# DEMO_READ_ONLY=false
+UNSAFE_ENABLE_MOCK_INTEGRATION=true

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -33,37 +33,6 @@ body:
       options:
         # The below comment is used to insert a new version with on-release.yml
         #NEXT_VERSION#
-        - 1.77.0
-        - 1.76.2
-        - 1.76.1
-        - 1.76.0
-        - 1.75.0
-        - 1.74.0
-        - 1.73.0
-        - 1.72.0
-        - 1.71.0
-        - 1.70.0
-        - 1.69.2
-        - 1.69.0
-        - 1.68.0
-        - 1.67.0
-        - 1.66.1
-        - 1.66.0
-        - 1.65.0
-        - 1.64.0
-        - 1.62.0
-        - 1.61.0
-        - 1.60.1-beta.1
-        - 1.60.0
-        - 1.59.3
-        - 1.59.2
-        - 1.59.1
-        - 1.59.0
-        - 1.58.1
-        - 1.58.0
-        - 1.57.1
-        - 1.57.0
-        - 1.56.1
         - 1.56.0
         - 1.55.0
         - 1.54.0

.github/ISSUE_TEMPLATE/integration.yml

@@ -25,16 +25,16 @@ body:
       label: Public API available?
       description: Is there a public API available, that we can consume in Homarr?
       options:
-        - "Yes, available on a website"
-        - "Yes, available in the application itself"
-        - "No"
+        - Yes, available on a website
+        - Yes, available in the application itself
+        - No
     validations:
       required: true
   - type: dropdown
     attributes:
       label: Are you willing to contribute this yourself?
       options:
-        - "Yes"
-        - "No"
+      - Yes
+      - No
     validations:
       required: true

.github/ISSUE_TEMPLATE/widget.yml

@@ -24,7 +24,7 @@ body:
     attributes:
       label: Are you willing to contribute this yourself?
       options:
-        - "Yes"
-        - "No"
+        - Yes
+        - No
     validations:
       required: true

.github/act/.gitignore

@@ -1,2 +0,0 @@
-.secrets
-!.secrets.example

.github/act/.secrets.example

@@ -1,4 +0,0 @@
-TURBO_API=
-TURBO_TEAM=
-TURBO_TOKEN=
-TURBO_REMOTE_CACHE_SIGNATURE_KEY=

.github/act/README.md

@@ -1,36 +0,0 @@
-# Running CI locally
-
-Install [Act](https://nektosact.com/installation/index.html) and ensure Docker is running, then use:
-
-```bash
-pnpm ci:act:fast
-pnpm ci:act:docker
-pnpm ci:act:all
-pnpm ci:act:cleanup
-```
-
-`fast` runs the quality gate. `docker` and `all` run the gate followed by the single container build, E2E suite, and memory regression test. `cleanup` validates the manual cleanup path without calling GitHub. The wrapper supports regular clones and Git worktrees, including non-default Docker contexts. Linux dependencies are kept in Docker volumes instead of overwriting host `node_modules`. The first run downloads the Act runner and Playwright browser dependencies.
-
-Remote caching is optional locally. Copy `.github/act/.secrets.example` to `.github/act/.secrets`, populate it with rotated credentials, and run with:
-
-```bash
-ACT_SECRET_FILE=.github/act/.secrets pnpm ci:act:all
-```
-
-Act never publishes or deletes GHCR images. The secret file is ignored by Git.
-
-## PR preview images
-
-Successful non-draft pull requests from this repository publish an amd64 image:
-
-```bash
-docker pull ghcr.io/homarr-labs/homarr-test:pr-<number>
-```
-
-The tag is replaced when the pull request is updated and deleted when it closes. Production Homarr images remain the supported multi-architecture releases. The `homarr-test` package must be configured as public in GHCR for unauthenticated testers.
-
-## Dokploy preview cache
-
-Keep `needs-demo` as the Dokploy preview label. Under the application's **Preview Build-time Secrets**, configure `TURBO_API`, `TURBO_TEAM`, `TURBO_TOKEN`, and `TURBO_REMOTE_CACHE_SIGNATURE_KEY`. Dokploy passes these to the Dockerfile as BuildKit secrets. Do not configure the token or signature key as Docker build arguments.
-
-Rotate any credentials that have appeared in chat, logs, or committed configuration before enabling the cache.

.github/actions/prebuilt-debian/action.yaml

@@ -11,15 +11,15 @@ outputs:
 runs:
   using: "composite"
   steps:
-    - uses: actions/checkout@v7
+    - uses: actions/checkout@v6
       with:
         persist-credentials: false
     - name: Set up Docker Buildx
-      uses: docker/setup-buildx-action@v4
+      uses: docker/setup-buildx-action@v3
 
     - name: Build docker image for ${{ inputs.architecture }}
       id: build
-      uses: docker/build-push-action@v7
+      uses: docker/build-push-action@v6
       with:
         push: false
         load: true

.github/pull_request_template.md

@@ -11,11 +11,3 @@
 - [ ] Commits follow the [conventional commits guideline](https://www.conventionalcommits.org/en/v1.0.0/)
 - [ ] No shorthand variable names are used (eg. `x`, `y`, `i` or any abbrevation)
 - [ ] Documentation is up to date. Create a pull request [here](https://github.com/homarr-labs/documentation/).
-- [ ] When using AI; No temp files are checked in, the code style follows the rest of the project
-
-**When contributing a new integration or widget:**
-
-- [ ] I confirmed manually that the integration or widget is working with a real system and performed basic smoke
-  tests (e.g. what happens if it is offline)
-- [ ] Optional but recommended: I confirm that I am willing to be added to the `CODEOWNERS` of this feature and will
-  provide support and maintain the integration (e.g. in case of breaking or failure)

.github/renovate.json5

@@ -1,6 +1,6 @@
 {
   $schema: "https://docs.renovatebot.com/renovate-schema.json",
-  extends: ["config:recommended", ":dependencyDashboardApproval"],
+  extends: ["config:recommended"],
   packageRules: [
     {
       matchPackageNames: ["^@homarr/"],
@@ -11,18 +11,12 @@
       matchPackageNames: ["tsx"],
       enabled: false,
     },
-    // Reenable once bug with undici v8 is fixed (https://github.com/homarr-labs/homarr/issues/5467)
-    {
-      matchPackageNames: ["undici"],
-      matchNewValue: "8.*",
-      enabled: false,
-    },
     {
       matchUpdateTypes: ["minor", "patch", "pin", "digest"],
       automerge: true,
     },
     {
-      // disallow automerge for allowBuilds dependencies (native builds need manual verification)
+      // disallow automerge for onlyBuiltDependencies
       matchPackageNames: [
         "@tree-sitter-grammars/tree-sitter-yaml",
         "bcrypt",
@@ -37,17 +31,11 @@
       automerge: false,
     },
   ],
-  // Updates lockfile for prebuilt-debian after if package.json is updated, otherwise only root lockfile is updated
-  postUpgradeTasks: {
-    commands: ["cd deployments/prebuilt-debian && pnpm install --ignore-workspace --lockfile-only"],
-    fileFilters: ["deployments/prebuilt-debian/pnpm-lock.yaml"],
-    executionMode: "update",
-  },
   updateInternalDeps: true,
   rangeStrategy: "bump",
   automerge: false,
-  baseBranchPatterns: ["dev"],
-  dependencyDashboard: true,
+  baseBranches: ["dev"],
+  dependencyDashboard: false,
   // prevent special characters in branch names (otherwise git errors occur on windows)
   branchNameStrict: true,
 }

.github/workflows/autofix.yml

@@ -1,47 +0,0 @@
-name: Auto-fix lint and format
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened]
-    branches: ["*"]
-
-permissions:
-  contents: write
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
-  cancel-in-progress: true
-
-jobs:
-  autofix:
-    name: Auto-fix
-    if: github.event.pull_request.head.repo.id == github.repository_id
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    steps:
-      - uses: actions/checkout@v7
-        with:
-          fetch-depth: 0
-          ref: ${{ github.head_ref }}
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Get changed files
-        id: changed
-        env:
-          BASE_REF: ${{ github.base_ref }}
-        run: |
-          git diff --name-only --diff-filter=ACMR "origin/${BASE_REF}...HEAD" -- '*.ts' '*.tsx' '*.js' '*.jsx' > /tmp/changed-files
-          echo "count=$(wc -l < /tmp/changed-files | tr -d '[:space:]')" >> $GITHUB_OUTPUT
-
-      - name: Auto-fix lint + format
-        if: steps.changed.outputs.count != '0'
-        run: |
-          xargs -r -a /tmp/changed-files pnpm exec oxlint --fix || true
-          xargs -r -a /tmp/changed-files pnpm exec oxfmt --write
-
-      - name: Commit fixes
-        uses: stefanzweifel/git-auto-commit-action@v7
-        with:
-          commit_message: "style: auto-fix lint and format"

.github/workflows/automatic-approval.yml

@@ -0,0 +1,30 @@
+name: "[Dependency Updates] Auto Approve"
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+permissions: {}
+
+jobs:
+  approve-automatic-prs:
+    runs-on: ubuntu-latest
+    timeout-minutes: 2
+    if: github.actor_id == 158783068 || github.actor_id == 190541745 || github.actor_id == 210161987 # Id of renovate bot and crowdin bot see https://api.github.com/users/homarr-renovate%5Bbot%5D and https://api.github.com/users/homarr-crowdin%5Bbot%5D and https://api.github.com/users/homarr-update-contributors%5Bbot%5D
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v6
+      - name: Obtain token
+        id: obtainToken
+        uses: actions/create-github-app-token@v2
+        with:
+          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
+          app-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
+          permission-pull-requests: write # required to approve pull request
+
+      - name: Install GitHub CLI
+        run: sudo apt-get install -y gh
+      - name: Approve automatic PRs
+        env:
+          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
+        run: |
+          gh pr review ${{github.event.pull_request.number}} --approve --body "Automatically approved by GitHub Action"

.github/workflows/bot-auto-merge-reconcile.yml

@@ -1,43 +0,0 @@
-name: "[Bots] Reconcile Auto-merge"
-
-on:
-  schedule:
-    - cron: "*/30 * * * *"
-  workflow_dispatch:
-
-permissions: {}
-
-jobs:
-  reconcile:
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v7
-
-      - name: Obtain token
-        id: obtainToken
-        uses: actions/create-github-app-token@v3
-        with:
-          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
-          permission-pull-requests: write # required to enable auto-merge
-
-      - name: Install GitHub CLI
-        run: sudo apt-get install -y gh
-
-      - name: Re-enable auto-merge for prepared bot PRs
-        env:
-          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
-        run: |
-          # 158783068: homarr-renovate[bot]
-          # 190541745: homarr-crowdin[bot]
-          # 210161987: homarr-update-contributors[bot]
-          # 175441: homarr-releases[bot]
-          gh pr list --repo "${{ github.repository }}" --base dev --state open --limit 100 \
-            --json number,author,reviewDecision,mergeStateStatus,autoMergeRequest \
-            --jq '.[] | select(.author.login as $login | ["app/homarr-renovate", "app/homarr-crowdin", "app/homarr-update-contributors", "app/homarr-releases"] | index($login)) | select(.reviewDecision == "APPROVED") | select(.mergeStateStatus == "CLEAN") | select(.autoMergeRequest == null) | .number' \
-          | while read -r pr; do
-              echo "Re-enabling auto-merge on PR #$pr"
-              gh pr merge "$pr" --auto --squash
-            done

.github/workflows/bot-pr-automerge.yml

@@ -1,47 +0,0 @@
-name: "[Bots] Approve and Auto-merge"
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened, ready_for_review]
-
-permissions: {}
-
-jobs:
-  approve-and-automerge:
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    # 158783068: homarr-renovate[bot]
-    # 190541745: homarr-crowdin[bot]
-    # 210161987: homarr-update-contributors[bot]
-    # 175441: homarr-releases[bot]
-    # Extracted from https://api.github.com/users/<username>
-    if: |
-      (github.actor_id == 158783068 || github.actor_id == 190541745 || github.actor_id == 210161987 || github.actor_id == 175441) &&
-      github.event.pull_request.head.repo.full_name == github.repository &&
-      github.event.pull_request.base.ref == 'dev'
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v7
-
-      - name: Obtain token
-        id: obtainToken
-        uses: actions/create-github-app-token@v3
-        with:
-          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
-          permission-pull-requests: write # required to approve a pull request and enable auto-merge
-
-      - name: Install GitHub CLI
-        run: sudo apt-get install -y gh
-
-      - name: Approve and enable auto-merge
-        env:
-          GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
-        run: |
-          PR_NUMBER="${{ github.event.pull_request.number }}"
-          if [ "$(gh pr view "$PR_NUMBER" --json reviewDecision --jq .reviewDecision)" != "APPROVED" ]; then
-            gh pr review "$PR_NUMBER" --approve --body "Automatically approved by Homarr bot policy"
-          fi
-          if [ "$(gh pr view "$PR_NUMBER" --json autoMergeRequest --jq '.autoMergeRequest != null')" != "true" ]; then
-            gh pr merge "$PR_NUMBER" --auto --squash
-          fi

.github/workflows/ci.yml

@@ -1,264 +0,0 @@
-name: CI
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened, ready_for_review]
-    branches: ["*"]
-  pull_request_target:
-    types: [closed]
-    branches: ["*"]
-  push:
-    branches: [main, dev, beta, next]
-  merge_group:
-  workflow_dispatch:
-    inputs:
-      operation:
-        description: Operation to run
-        required: true
-        default: validate
-        type: choice
-        options:
-          - validate
-          - publish
-          - cleanup
-      pr_number:
-        description: PR number for publish or cleanup
-        required: false
-        type: number
-      ref:
-        description: Git ref to validate or publish
-        required: false
-        type: string
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.event.pull_request.number || inputs.pr_number || github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-env:
-  FORCE_COLOR: 3
-  SKIP_ENV_VALIDATION: true
-  TURBO_TELEMETRY_DISABLED: 1
-  REGISTRY: ghcr.io
-  PREVIEW_IMAGE: ghcr.io/homarr-labs/homarr-test
-
-jobs:
-  fast-gate:
-    name: Fast gate
-    if: github.event_name != 'pull_request_target' && (github.event_name != 'workflow_dispatch' || inputs.operation != 'cleanup')
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    env:
-      TURBO_API: ${{ secrets.TURBO_API }}
-      TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-      TURBO_REMOTE_CACHE_SIGNATURE_KEY: ${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
-      TURBO_SCM_BASE: ${{ github.event.pull_request.base.sha || github.event.merge_group.base_sha || github.event.before || 'HEAD~1' }}
-      TURBO_SCM_HEAD: ${{ github.sha }}
-      TURBO_PLATFORM: linux/amd64
-    steps:
-      - uses: actions/checkout@v7
-        if: "!env.ACT"
-        with:
-          fetch-depth: 0
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Validate manual inputs
-        if: github.event_name == 'workflow_dispatch' && inputs.operation == 'publish'
-        env:
-          PR_NUMBER: ${{ inputs.pr_number }}
-          BUILD_REF: ${{ inputs.ref }}
-        run: |
-          test -n "$PR_NUMBER" || { echo "pr_number is required for publish"; exit 1; }
-          test -n "$BUILD_REF" || { echo "ref is required for publish"; exit 1; }
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Copy environment defaults
-        run: cp .env.example .env
-
-      - name: Lint, typecheck, and build affected workspaces
-        run: pnpm turbo run lint typecheck build --affected --continue=dependencies-successful --concurrency=2
-
-      - name: Validate workspace configuration
-        run: pnpm lint:ws
-
-      - name: Run unit tests
-        run: pnpm test
-
-  container:
-    name: Container and E2E
-    needs: fast-gate
-    if: |
-      github.event_name == 'merge_group' ||
-      (github.event_name == 'pull_request' && github.event.pull_request.draft == false) ||
-      (github.event_name == 'workflow_dispatch' && (inputs.operation == 'validate' || inputs.operation == 'publish'))
-    runs-on: ubuntu-latest
-    timeout-minutes: 30
-    permissions:
-      contents: read
-      packages: write
-    steps:
-      - uses: actions/checkout@v7
-        if: "!env.ACT"
-        with:
-          persist-credentials: false
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || '' }}
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Set up Docker Buildx
-        if: "!env.ACT"
-        uses: docker/setup-buildx-action@v4
-
-      - name: Build container once
-        if: "!env.ACT"
-        uses: docker/build-push-action@v7
-        with:
-          context: .
-          network: host
-          platforms: linux/amd64
-          load: true
-          push: false
-          tags: |
-            homarr-ci
-            homarr-e2e
-          labels: |
-            org.opencontainers.image.source=${{ github.server_url }}/${{ github.repository }}
-            org.opencontainers.image.revision=${{ github.sha }}
-            org.opencontainers.image.ref.name=pr-${{ github.event.pull_request.number || inputs.pr_number || 'none' }}
-          cache-from: type=gha,scope=homarr-linux-amd64
-          cache-to: type=gha,scope=homarr-linux-amd64,mode=max
-          secrets: |
-            TURBO_API=${{ secrets.TURBO_API }}
-            TURBO_TEAM=${{ secrets.TURBO_TEAM }}
-            TURBO_TOKEN=${{ secrets.TURBO_TOKEN }}
-            TURBO_REMOTE_CACHE_SIGNATURE_KEY=${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
-
-      - name: Build container once with Act
-        if: env.ACT
-        env:
-          TURBO_API: ${{ secrets.TURBO_API }}
-          TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
-          TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-          TURBO_REMOTE_CACHE_SIGNATURE_KEY: ${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
-        run: |
-          secret_args=()
-          for secret in TURBO_API TURBO_TEAM TURBO_TOKEN TURBO_REMOTE_CACHE_SIGNATURE_KEY; do
-            if [ -n "${!secret:-}" ]; then
-              secret_args+=(--secret "id=${secret},env=${secret}")
-            fi
-          done
-          DOCKER_BUILDKIT=1 docker build --platform linux/amd64 \
-            --tag homarr-ci --tag homarr-e2e "${secret_args[@]}" .
-
-      - name: Cache Playwright browsers
-        if: "!env.ACT"
-        id: playwright-cache
-        uses: actions/cache@v6
-        with:
-          path: ~/.cache/ms-playwright
-          key: playwright-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}
-
-      - name: Install Playwright Chromium
-        if: steps.playwright-cache.outputs.cache-hit != 'true' || env.ACT
-        run: pnpm exec playwright install --with-deps chromium
-
-      - name: Install Playwright system deps
-        if: steps.playwright-cache.outputs.cache-hit == 'true'
-        run: pnpm exec playwright install-deps chromium
-
-      - name: Run E2E tests
-        run: pnpm test:e2e
-
-      - name: Upload E2E artifacts
-        if: failure() && !env.ACT
-        uses: actions/upload-artifact@v7
-        with:
-          name: playwright-report
-          path: e2e/test-results/
-          retention-days: 7
-
-      - name: Determine preview tag
-        id: preview
-        if: |
-          !env.ACT &&
-          (
-            (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository) ||
-            (github.event_name == 'workflow_dispatch' && inputs.operation == 'publish')
-          )
-        env:
-          PR_NUMBER: ${{ github.event.pull_request.number || inputs.pr_number }}
-        run: echo "tag=pr-${PR_NUMBER}" >> "$GITHUB_OUTPUT"
-
-      - name: Log in to GHCR
-        if: steps.preview.outputs.tag != ''
-        uses: docker/login-action@v4
-        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Push preview image
-        if: steps.preview.outputs.tag != ''
-        env:
-          PREVIEW_TAG: ${{ steps.preview.outputs.tag }}
-        run: |
-          docker tag homarr-ci "${PREVIEW_IMAGE}:${PREVIEW_TAG}"
-          docker push "${PREVIEW_IMAGE}:${PREVIEW_TAG}"
-
-      - name: Show Act publication result
-        if: env.ACT
-        run: echo "Act validated the publication path; external GHCR writes are disabled locally."
-
-  cleanup:
-    name: Clean up preview image
-    if: github.event_name == 'pull_request_target' || (github.event_name == 'workflow_dispatch' && inputs.operation == 'cleanup')
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    permissions:
-      packages: write
-    env:
-      IMAGE_TAG: pr-${{ github.event.pull_request.number || inputs.pr_number }}
-    steps:
-      - name: Validate cleanup input
-        if: github.event_name == 'workflow_dispatch'
-        env:
-          PR_NUMBER: ${{ inputs.pr_number }}
-        run: test -n "$PR_NUMBER" || { echo "pr_number is required for cleanup"; exit 1; }
-
-      - name: Delete GHCR package version
-        if: "!env.ACT"
-        uses: actions/github-script@v8
-        with:
-          script: |
-            const packageName = "homarr-test";
-            const org = context.repo.owner;
-            const tag = process.env.IMAGE_TAG;
-            const versions = await github.paginate(
-              github.rest.packages.getAllPackageVersionsForPackageOwnedByOrg,
-              { package_type: "container", package_name: packageName, org, per_page: 100 },
-            );
-            const target = versions.find((version) =>
-              version.metadata?.container?.tags?.includes(tag),
-            );
-            if (!target) {
-              core.info(`No package version found with tag "${tag}"`);
-              return;
-            }
-            await github.rest.packages.deletePackageVersionForOrg({
-              package_type: "container",
-              package_name: packageName,
-              org,
-              package_version_id: target.id,
-            });
-            core.info(`Deleted package version ${target.id} (${tag})`);
-
-      - name: Show Act cleanup result
-        if: env.ACT
-        run: echo "Act validated cleanup for ${IMAGE_TAG}; external GHCR writes are disabled locally."

.github/workflows/code-quality.yml

@@ -0,0 +1,118 @@
+name: "[Quality] Code Analysis"
+permissions:
+  contents: read
+
+on:
+  pull_request:
+    branches: ["*"]
+  push:
+    branches: ["main"]
+  merge_group:
+
+concurrency:
+  group: "${{ github.workflow }}-${{ github.ref }}"
+  cancel-in-progress: ${{ github.ref != 'refs/heads/master' }}
+
+# You can leverage Vercel Remote Caching with Turbo to speed up your builds
+# @link https://turborepo.org/docs/core-concepts/remote-caching#remote-caching-on-vercel-builds
+env:
+  FORCE_COLOR: 3
+  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
+  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Copy env
+        shell: bash
+        run: cp .env.example .env
+
+      - name: Lint
+        run: pnpm lint && pnpm lint:ws
+
+  format:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Format
+        run: pnpm format
+
+  typecheck:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Typecheck
+        run: turbo typecheck
+
+  test:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Setup
+        uses: ./tooling/github/setup
+
+      - name: Test
+        run: pnpm test
+
+      - name: "Report Coverage"
+        # Set if: always() to also generate the report if tests are failing
+        # Only works if you set `reportOnFailure: true` in your vite config as specified above
+        if: always()
+        uses: davelosert/vitest-coverage-report-action@v2
+
+  e2e:
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+
+    steps:
+      - uses: actions/checkout@v6
+      - name: Setup
+        uses: ./tooling/github/setup
+      - name: Build docker image
+        id: build-docker-image
+        uses: docker/build-push-action@v6
+        with:
+          platforms: linux/amd64
+          context: .
+          push: false
+          tags: homarr-e2e
+          network: host
+        env:
+          SKIP_ENV_VALIDATION: true
+      - name: Install playwright browsers
+        run: pnpm exec playwright install chromium
+      - name: Run E2E Tests
+        shell: bash
+        run: pnpm test:e2e
+
+  build:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v6
+      - name: Setup
+        uses: ./tooling/github/setup
+      - name: Copy env
+        shell: bash
+        run: cp .env.example .env
+      - name: Build
+        run: pnpm build

.github/workflows/crowdin-schedule-download.yml

@@ -15,14 +15,14 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
 
       - name: Obtain token
         id: obtainToken
-        uses: actions/create-github-app-token@v3
+        uses: actions/create-github-app-token@v2
         with:
           private-key: ${{ secrets.CROWDIN_APP_PRIVATE_KEY }}
-          client-id: ${{ secrets.CROWDIN_APP_ID }}
+          app-id: ${{ secrets.CROWDIN_APP_ID }}
           permission-contents: write # required to commit to crowdin branch
           permission-pull-requests: write # required to create pull request
 

.github/workflows/crowdin-upload.yml

@@ -18,7 +18,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
 
       - name: Upload Crowdin translations
         uses: crowdin/github-action@v2

.github/workflows/deployment-beta-release.yml

@@ -1,104 +0,0 @@
-name: "[Deployment] Beta Release"
-
-on:
-  workflow_dispatch:
-    inputs:
-      send-notifications:
-        type: boolean
-        required: false
-        default: true
-        description: Send notifications
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  create-and-merge-pr:
-    runs-on: ubuntu-latest
-    timeout-minutes: 2
-    steps:
-      - name: Discord notification
-        if: ${{ github.event.inputs.send-notifications }}
-        env:
-          DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
-        with:
-          args: "Beta release has been triggered: [run ${{ github.run_number }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
-      - name: Checkout repository
-        uses: actions/checkout@v7
-        with:
-          fetch-depth: 0
-      - name: Get Next Version
-        id: semver
-        uses: ietf-tools/semver-action@v1
-        with:
-          token: ${{ github.token }}
-          branch: next
-      - name: Create pull request
-        id: create-pull-request
-        run: 'gh pr create --title "chore(release): release ${{ steps.semver.outputs.next }}-beta" --body "Detected change to be ``${{ steps.semver.outputs.bump }}``<br/>Bump version from ``${{ steps.semver.outputs.current }}`` to ``${{ steps.semver.outputs.next }}-beta``" --base beta --head next --label automerge'
-        env:
-          GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
-      - name: Discord notification
-        if: ${{ github.event.inputs.send-notifications }}
-        env:
-          DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
-        with:
-          args: "Created a release PR ${{ steps.create-pull-request.outputs.url }} for version ${{ steps.semver.outputs.next }}-beta (new behaviour: ${{ steps.semver.outputs.bump }})"
-      - name: Obtain token
-        id: obtainApprovalToken
-        uses: actions/create-github-app-token@v3
-        with:
-          private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
-          permission-pull-requests: write
-      - name: Approve PR
-        env:
-          GITHUB_TOKEN: ${{ steps.obtainApprovalToken.outputs.token }}
-        run: |
-          gh pr review --approve --body "Automatically approved by GitHub Action"
-      - name: Obtain token
-        id: obtainMergeToken
-        uses: actions/create-github-app-token@v3
-        with:
-          private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
-          permission-contents: write # write to beta branch (due to merge)
-          permission-pull-requests: write # merge pull request
-      - id: automerge
-        if: ${{ steps.semver.outputs.bump != 'major' }}
-        name: automerge
-        uses: "pascalgn/automerge-action@v0.16.4"
-        env:
-          GITHUB_TOKEN: ${{ steps.obtainMergeToken.outputs.token }}
-          MERGE_METHOD: merge # we prefer merge commits for merging to beta
-          MERGE_COMMIT_MESSAGE: "chore(release): release ${{ steps.semver.outputs.next }}-beta"
-          MERGE_DELETE_BRANCH: false # never set to true!
-          PULL_REQUEST: "${{ steps.create-pull-request.outputs.pr_number }}"
-          MERGE_RETRIES: 20 # 20 retries * MERGE_RETRY_SLEEP until step fails
-          MERGE_RETRY_SLEEP: 10000 # 10 seconds * MERGE_RETRIES until step fails
-          MERGE_REQUIRED_APPROVALS: 0 # do not require approvals
-
-      - name: Merged Discord notification
-        if: ${{ steps.automerge.outputs.mergeResult == 'merged' && github.event.inputs.send-notifications }}
-        env:
-          DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
-        with:
-          args: "Merged PR ${{ steps.create-pull-request.outputs.url }} for release ${{ steps.semver.outputs.next }}-beta"
-      - name: Major Bump Discord notification
-        if: ${{ steps.semver.outputs.bump == 'major' && github.event.inputs.send-notifications }}
-        env:
-          DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
-        with:
-          args: "The release PR must be manually merged because the next version is a major version: ${{ steps.create-pull-request.outputs.url }} for release ${{ steps.semver.outputs.next }}-beta"
-      - name: Discord Fail Notification
-        if: failure() && github.event.inputs.send-notifications
-        env:
-          DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
-        with:
-          args: "The beta release workflow [run ${{ github.run_number }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) has failed"

.github/workflows/deployment-docker-image.yml

@@ -5,7 +5,6 @@ on:
     branches:
       - main
       - beta
-      - next
       - dev
   workflow_dispatch:
     inputs:
@@ -35,7 +34,7 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 5
     env:
-      SKIP_RELEASE: ${{ github.event_name == 'workflow_dispatch' || github.ref_name == 'dev' || github.ref_name == 'next' }}
+      SKIP_RELEASE: ${{ github.event_name == 'workflow_dispatch' || github.ref_name == 'dev' }}
     outputs:
       version: ${{ steps.read-semver.outputs.version || steps.version-fallback.outputs.version }}
       git_ref: ${{ steps.read-git-ref.outputs.ref || github.ref }}
@@ -51,23 +50,25 @@ jobs:
       - name: Obtain token
         if: env.SKIP_RELEASE == 'false'
         id: obtainToken
-        uses: actions/create-github-app-token@v3
+        uses: actions/create-github-app-token@v2
         with:
           private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
-          permission-contents: write # required to commit package.json & changelog changes, merge them to dev / next and publish the release
+          app-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
+          permission-contents: write # required to commit package.json & changelog changes, merge them to dev and publish the release
 
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
         if: env.SKIP_RELEASE == 'false'
         with:
           persist-credentials: false
-      - uses: pnpm/action-setup@v6
+      - uses: pnpm/action-setup@v4
         if: env.SKIP_RELEASE == 'false'
       - uses: actions/setup-node@v6
         if: env.SKIP_RELEASE == 'false'
         with:
-          node-version: 24.18.0
-          package-manager-cache: false
+          node-version: 24.14.0
+          cache: "pnpm"
+      - run: npm i -g pnpm
+        if: env.SKIP_RELEASE == 'false'
       - name: Install dependencies
         if: env.SKIP_RELEASE == 'false'
         run: |
@@ -94,21 +95,20 @@ jobs:
         id: read-git-ref
         run: |
           echo "ref=$(git rev-parse HEAD)" >> "$GITHUB_OUTPUT"
-      - name: Update dev / next branch
+      - name: Update dev branch
         if: env.SKIP_RELEASE == 'false'
         continue-on-error: true # Prevent pipeline from failing when merge fails
         env:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
-          UPSTREAM_BRANCH: ${{ github.ref_name == 'main' && 'dev' || 'next' }}
         run: |
           git config user.name "Releases Homarr"
           git config user.email "175486441+homarr-releases[bot]@users.noreply.github.com"
           git remote set-url origin https://x-access-token:${{ steps.obtainToken.outputs.token }}@github.com/${{ github.repository }}.git
-          git fetch origin ${{ env.UPSTREAM_BRANCH }}
-          git checkout ${{ env.UPSTREAM_BRANCH }}
-          git pull origin ${{ env.UPSTREAM_BRANCH }}
+          git fetch origin dev
+          git checkout dev
+          git pull origin dev
           git rebase ${{ github.ref_name }}
-          git push origin ${{ env.UPSTREAM_BRANCH }}
+          git push origin dev
   build-amd64:
     name: Build docker image for amd64
     needs: release
@@ -117,13 +117,13 @@ jobs:
     outputs:
       digest: ${{ steps.build.outputs.digest }}
     steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
         with:
           ref: ${{ needs.release.outputs.git_ref }}
 
       - name: Docker meta
         id: meta
-        uses: docker/metadata-action@v6
+        uses: docker/metadata-action@v5
         with:
           images: "${{ env.GHCR_REPO }}"
 
@@ -135,22 +135,17 @@ jobs:
           password: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v4
+        uses: docker/setup-buildx-action@v3
 
       - name: Build and push by digest
         id: build
-        uses: docker/build-push-action@v7
+        uses: docker/build-push-action@v6
         with:
           context: .
           network: host
           platforms: linux/amd64
           labels: ${{ steps.meta.outputs.labels }}
           outputs: type=image,"name=${{ env.GHCR_REPO }}",push-by-digest=true,name-canonical=true,push=true
-          secrets: |
-            TURBO_API=${{ secrets.TURBO_API }}
-            TURBO_TEAM=${{ secrets.TURBO_TEAM }}
-            TURBO_TOKEN=${{ secrets.TURBO_TOKEN }}
-            TURBO_REMOTE_CACHE_SIGNATURE_KEY=${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
         env:
           SKIP_ENV_VALIDATION: true
   build-arm64:
@@ -161,13 +156,13 @@ jobs:
     outputs:
       digest: ${{ steps.build.outputs.digest }}
     steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
         with:
           ref: ${{ needs.release.outputs.git_ref }}
 
       - name: Docker meta
         id: meta
-        uses: docker/metadata-action@v6
+        uses: docker/metadata-action@v5
         with:
           images: "${{ env.GHCR_REPO }}"
 
@@ -179,29 +174,24 @@ jobs:
           password: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v4
+        uses: docker/setup-buildx-action@v3
 
       - name: Build and push by digest
         id: build
-        uses: docker/build-push-action@v7
+        uses: docker/build-push-action@v6
         with:
           context: .
           network: host
           platforms: linux/arm64
           labels: ${{ steps.meta.outputs.labels }}
           outputs: type=image,"name=${{ env.GHCR_REPO }}",push-by-digest=true,name-canonical=true,push=true
-          secrets: |
-            TURBO_API=${{ secrets.TURBO_API }}
-            TURBO_TEAM=${{ secrets.TURBO_TEAM }}
-            TURBO_TOKEN=${{ secrets.TURBO_TOKEN }}
-            TURBO_REMOTE_CACHE_SIGNATURE_KEY=${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
         env:
           SKIP_ENV_VALIDATION: true
   extract-asset-amd64:
     name: Extract amd64 asset from docker image
     needs: [release, build-amd64]
     runs-on: ubuntu-latest
-    timeout-minutes: 5
+    timeout-minutes: 2
     steps:
       - name: Extract amd64
         if: needs.release.outputs.skipped == 'false'
@@ -217,7 +207,7 @@ jobs:
     name: Extract arm64 asset from docker image
     needs: [release, build-arm64]
     runs-on: ubuntu-24.04-arm
-    timeout-minutes: 5
+    timeout-minutes: 2
     steps:
       - name: Extract arm64
         if: needs.release.outputs.skipped == 'false'
@@ -241,10 +231,10 @@ jobs:
       - name: Obtain token
         if: needs.release.outputs.skipped == 'false'
         id: obtainToken
-        uses: actions/create-github-app-token@v3
+        uses: actions/create-github-app-token@v2
         with:
           private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
+          app-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
           permission-contents: write # required to publish the release
 
       - name: Log in to the Container registry
@@ -284,6 +274,6 @@ jobs:
       - name: Discord notification
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
+        uses: Ilshidur/action-discord@master
         with:
           args: "Successfully deployed images for branch **${{ github.ref_name }}**. Tagged as **${{env.NEXT_VERSION}}**."

.github/workflows/deployment-docs.yml

@@ -1,56 +0,0 @@
-name: "[Deployment] Documentation"
-
-on:
-  push:
-    branches: ["dev"]
-    paths:
-      - "apps/docs/**"
-      - "packages/definitions/src/docs/**"
-      - ".github/workflows/deployment-docs.yml"
-  workflow_dispatch:
-
-permissions:
-  contents: read
-  pages: write
-  id-token: write
-
-concurrency:
-  group: "pages"
-  cancel-in-progress: false
-
-env:
-  SKIP_ENV_VALIDATION: true
-  TURBO_API: ${{ secrets.TURBO_API }}
-  TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
-  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-  TURBO_REMOTE_CACHE_SIGNATURE_KEY: ${{ secrets.TURBO_REMOTE_CACHE_SIGNATURE_KEY }}
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@v7
-      - name: Setup
-        uses: ./tooling/github/setup
-      - name: Build docs
-        run: pnpm turbo build --filter=@homarr/docs
-        env:
-          CI: "true"
-      - name: Setup Pages
-        uses: actions/configure-pages@v6
-      - name: Upload pages artifact
-        uses: actions/upload-pages-artifact@v5
-        with:
-          path: "apps/docs/build"
-
-  deploy:
-    runs-on: ubuntu-latest
-    needs: build
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    steps:
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v5

.github/workflows/deployment-weekly-release.yml

@@ -3,7 +3,6 @@ name: "[Deployment] Automatic Weekly Release"
 on:
   schedule:
     - cron: "0 19 * * 5" # https://crontab.guru/#0_19_*_*_5
-      timezone: Europe/Zurich
   workflow_dispatch:
     inputs:
       send-notifications:
@@ -22,14 +21,14 @@ jobs:
     timeout-minutes: 2
     steps:
       - name: Discord notification
-        if: ${{ github.event.inputs.send-notifications }}
+        if: ${{ github.events.inputs.send-notifications }}
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
+        uses: Ilshidur/action-discord@master
         with:
           args: "Automatic release has been triggered: [run ${{ github.run_number }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
       - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
       - name: Get Next Version
@@ -39,23 +38,22 @@ jobs:
           token: ${{ github.token }}
           branch: dev
       - name: Create pull request
-        id: create-pull-request
         run: 'gh pr create --title "chore(release): automatic release ${{ steps.semver.outputs.next }}" --body "**This is an automatic release**.<br/>Manual action may be required for major bumps.<br/>Detected change to be ``${{ steps.semver.outputs.bump }}``<br/>Bump version from ``${{ steps.semver.outputs.current }}`` to ``${{ steps.semver.outputs.next }}``" --base main --head dev --label automerge'
         env:
           GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
       - name: Discord notification
-        if: ${{ github.event.inputs.send-notifications }}
+        if: ${{ github.events.inputs.send-notifications }}
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
+        uses: Ilshidur/action-discord@master
         with:
           args: "Created a release PR ${{ steps.create-pull-request.outputs.url }} for version ${{ steps.semver.outputs.next }} (new behaviour: ${{ steps.semver.outputs.bump }})"
       - name: Obtain token
         id: obtainApprovalToken
-        uses: actions/create-github-app-token@v3
+        uses: actions/create-github-app-token@v2
         with:
           private-key: ${{ secrets.RENOVATE_APPROVE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
+          app-id: ${{ secrets.RENOVATE_APPROVE_APP_ID }}
           permission-pull-requests: write
       - name: Approve PR
         env:
@@ -64,10 +62,10 @@ jobs:
           gh pr review --approve --body "Automatically approved by GitHub Action"
       - name: Obtain token
         id: obtainMergeToken
-        uses: actions/create-github-app-token@v3
+        uses: actions/create-github-app-token@v2
         with:
           private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
+          app-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
           permission-contents: write # write to main branch (due to merge)
           permission-pull-requests: write # merge pull request
       - id: automerge
@@ -76,7 +74,7 @@ jobs:
         uses: "pascalgn/automerge-action@v0.16.4"
         env:
           GITHUB_TOKEN: ${{ steps.obtainMergeToken.outputs.token }}
-          MERGE_METHOD: merge # we prefer merge commits for merging to main
+          MERGE_METHOD: merge # we prefer merge commits for merging to master
           MERGE_COMMIT_MESSAGE: "chore(release): automatic release ${{ steps.semver.outputs.next }}"
           MERGE_DELETE_BRANCH: false # never set to true!
           PULL_REQUEST: "${{ steps.create-pull-request.outputs.pr_number }}"
@@ -85,23 +83,23 @@ jobs:
           MERGE_REQUIRED_APPROVALS: 0 # do not require approvals
 
       - name: Merged Discord notification
-        if: ${{ steps.automerge.outputs.mergeResult == 'merged' && github.event.inputs.send-notifications }}
+        if: ${{ steps.automerge.outputs.mergeResult == 'merged' && github.events.inputs.send-notifications }}
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
+        uses: Ilshidur/action-discord@master
         with:
           args: "Merged PR ${{ steps.create-pull-request.outputs.url }} for release ${{ steps.semver.outputs.next }}"
       - name: Major Bump Discord notification
-        if: ${{ steps.semver.outputs.bump == 'major' && github.event.inputs.send-notifications }}
+        if: ${{ steps.semver.outputs.bump == 'major' && github.events.inputs.send-notifications }}
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
+        uses: Ilshidur/action-discord@master
         with:
           args: "The release PR must be manually merged because the next version is a major version: ${{ steps.create-pull-request.outputs.url }} for release ${{ steps.semver.outputs.next }}"
       - name: Discord Fail Notification
-        if: failure() && github.event.inputs.send-notifications
+        if: failure() && github.events.inputs.send-notifications
         env:
           DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-        uses: Ilshidur/action-discord@0.4.0
+        uses: Ilshidur/action-discord@master
         with:
           args: "The automatic release workflow [run ${{ github.run_number }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) has failed"

.github/workflows/docs-algolia-recrawl.yml

@@ -1,58 +0,0 @@
-name: "[Docs] Algolia Recrawl"
-
-on:
-  workflow_run:
-    workflows: ["[Deployment] Documentation"]
-    types: [completed]
-    branches: [dev]
-  workflow_dispatch:
-
-permissions:
-  contents: read
-
-jobs:
-  recrawl:
-    if: >-
-      ${{
-        (github.event.workflow_run.conclusion == 'success' && github.event.workflow_run.event != 'pull_request')
-        || github.event_name == 'workflow_dispatch'
-      }}
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@v7
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Check Algolia crawler secrets
-        run: |
-          missing=0
-          for secret in ALGOLIA_CRAWLER_ID ALGOLIA_CRAWLER_USER_ID ALGOLIA_CRAWLER_API_KEY; do
-            if [ -z "${!secret}" ]; then
-              echo "::warning::Missing repository secret: $secret"
-              missing=1
-            fi
-          done
-          if [ "$missing" -eq 1 ]; then
-            echo "Add crawler secrets to enable automatic recrawls."
-            exit 1
-          fi
-        env:
-          ALGOLIA_CRAWLER_ID: ${{ secrets.ALGOLIA_CRAWLER_ID }}
-          ALGOLIA_CRAWLER_USER_ID: ${{ secrets.ALGOLIA_CRAWLER_USER_ID }}
-          ALGOLIA_CRAWLER_API_KEY: ${{ secrets.ALGOLIA_CRAWLER_API_KEY }}
-
-      - name: Wait for GitHub Pages to serve the new deployment
-        run: sleep 60
-
-      - name: Trigger Algolia DocSearch recrawl
-        uses: cssnr/algolia-crawler-action@v2
-        with:
-          crawler_id: ${{ secrets.ALGOLIA_CRAWLER_ID }}
-          crawler_user_id: ${{ secrets.ALGOLIA_CRAWLER_USER_ID }}
-          crawler_api_key: ${{ secrets.ALGOLIA_CRAWLER_API_KEY }}
-
-      - name: Verify search index
-        working-directory: apps/docs
-        run: pnpm verify:search

.github/workflows/docs-update-contributors.yml

@@ -1,39 +0,0 @@
-name: "[Docs] Update Contributors"
-
-on:
-  schedule:
-    - cron: "0 12 * * FRI"
-  workflow_dispatch:
-
-permissions:
-  contents: write
-
-env:
-  GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
-  HOMARR_CROWDIN_TOKEN: "${{ secrets.HOMARR_CROWDIN_TOKEN }}"
-  HOMARR_LABS_CROWDIN_TOKEN: "${{ secrets.HOMARR_LABS_CROWDIN_TOKEN }}"
-  SKIP_ENV_VALIDATION: true
-
-jobs:
-  dump:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@v7
-        with:
-          ref: dev
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Dump contributors
-        working-directory: apps/docs
-        run: pnpm api-dump-contributors
-
-      - name: Commit updated contributors
-        uses: EndBug/add-and-commit@v10
-        with:
-          add: "apps/docs/static"
-          default_author: github_actor
-          message: "chore(docs): update contributors"
-          push: true

.github/workflows/docs-update-openapi.yml

@@ -1,66 +0,0 @@
-name: "[Docs] Update OpenAPI Spec"
-
-on:
-  schedule:
-    - cron: "0 0 * * *"
-  workflow_dispatch:
-
-permissions:
-  contents: write
-
-env:
-  SKIP_ENV_VALIDATION: true
-
-jobs:
-  update-spec:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@v7
-        with:
-          ref: dev
-
-      - name: Setup
-        uses: ./tooling/github/setup
-
-      - name: Copy env
-        run: cp .env.example .env
-
-      - name: Start dev server
-        run: pnpm --filter @homarr/nextjs dev &
-        env:
-          TURBO_TELEMETRY_DISABLED: 1
-          DISABLE_TELEMETRY: 1
-
-      - name: Wait for server and fetch spec
-        run: |
-          set -euo pipefail
-          for i in $(seq 1 30); do
-            if curl -fsS http://localhost:3000/api/openapi -o /tmp/openapi.json 2>/dev/null; then
-              echo "Server is up, spec fetched"
-              break
-            fi
-            echo "Waiting for server... ($i/30)"
-            sleep 3
-          done
-
-          if [ ! -f /tmp/openapi.json ]; then
-            echo "::error::Server failed to start within timeout"
-            exit 1
-          fi
-
-          jq -e '.openapi and .paths' /tmp/openapi.json > /dev/null || {
-            echo "::error::Fetched file is not a valid OpenAPI spec"
-            exit 1
-          }
-
-          cp /tmp/openapi.json apps/docs/static/api/open-api-schema.json
-          echo "OpenAPI spec updated ($(jq '.paths | length' /tmp/openapi.json) paths)"
-
-      - name: Commit updated spec
-        uses: EndBug/add-and-commit@v10
-        with:
-          add: "apps/docs/static/api/"
-          default_author: github_actor
-          message: "chore(docs): update OpenAPI spec"
-          push: true

.github/workflows/on-pr-prebuilt-debian-validate.yml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 5
     steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
       - name: Validate prebuilt dependencies for amd64
         id: validate-amd64
         uses: ./.github/actions/prebuilt-debian
@@ -30,7 +30,7 @@ jobs:
     runs-on: ubuntu-24.04-arm
     timeout-minutes: 5
     steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
       - name: Validate prebuilt dependencies for arm64
         id: validate-arm64
         uses: ./.github/actions/prebuilt-debian

.github/workflows/on-pr-renovate-validate.yml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 2
     steps:
-      - uses: actions/checkout@v7
+      - uses: actions/checkout@v6
       - run: |
           npx --yes --package renovate -- \
               renovate-config-validator --strict .github/renovate.json5

.github/workflows/on-release.yml

@@ -12,10 +12,10 @@ jobs:
     steps:
       - name: Obtain token
         id: obtainToken
-        uses: actions/create-github-app-token@v3
+        uses: actions/create-github-app-token@v2
         with:
           private-key: ${{ secrets.HOMARR_DOCS_RELEASE_APP_PRIVATE_KEY }}
-          client-id: ${{ vars.HOMARR_DOCS_RELEASE_APP_ID }}
+          app-id: ${{ vars.HOMARR_DOCS_RELEASE_APP_ID }}
           owner: homarr-labs
           repositories: |
             documentation
@@ -45,14 +45,14 @@ jobs:
     steps:
       - name: Obtain token
         id: obtainToken
-        uses: actions/create-github-app-token@v3
+        uses: actions/create-github-app-token@v2
         with:
           private-key: ${{ secrets.RENOVATE_MERGE_PRIVATE_KEY }}
-          client-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
+          app-id: ${{ secrets.RENOVATE_MERGE_APP_ID }}
           permission-contents: write # required to commit to branch
           permission-pull-requests: write # required to create pr & enable automerge
       - name: Checkout code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         with:
           token: ${{ steps.obtainToken.outputs.token }}
           ref: dev

.github/workflows/skip-renovate-stability-days.yml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   skip-stability-days:
-    if: ${{ !startsWith(github.head_ref, 'renovate/') && github.event.pull_request.head.repo.full_name == github.repository }}
+    if: ${{ !startsWith(github.head_ref, 'renovate/') }}
     name: Skip Stability Days
     runs-on: ubuntu-latest
     timeout-minutes: 1

.github/workflows/update-contributors.yml

@@ -21,19 +21,19 @@ jobs:
     steps:
       - name: Obtain token
         id: obtainToken
-        uses: actions/create-github-app-token@v3
+        uses: actions/create-github-app-token@v2
         with:
           private-key: ${{ secrets.HOMARR_UPDATE_CONTRIBUTORS_PRIVATE_KEY }}
-          client-id: ${{ vars.HOMARR_UPDATE_CONTRIBUTORS_APP_ID }}
+          app-id: ${{ vars.HOMARR_UPDATE_CONTRIBUTORS_APP_ID }}
           permission-contents: write # required to commit to branch
           permission-pull-requests: write # required to create pr & enable automerge
 
       - name: Checkout repository
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         env:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
 
-      - uses: pnpm/action-setup@v6
+      - uses: pnpm/action-setup@v4
       - name: Use Node.js ${{ matrix.node-version }}
         uses: actions/setup-node@v6
         with:

.github/workflows/update-integration-list.yml

@@ -21,14 +21,14 @@ jobs:
     steps:
       - name: Obtain token
         id: obtainToken
-        uses: actions/create-github-app-token@v3
+        uses: actions/create-github-app-token@v2
         with:
           private-key: ${{ secrets.HOMARR_UPDATE_CONTRIBUTORS_PRIVATE_KEY }}
-          client-id: ${{ vars.HOMARR_UPDATE_CONTRIBUTORS_APP_ID }}
+          app-id: ${{ vars.HOMARR_UPDATE_CONTRIBUTORS_APP_ID }}
           permission-contents: write # required to commit to branch
           permission-pull-requests: write # required to create pr & enable automerge
       - name: Checkout code
-        uses: actions/checkout@v7
+        uses: actions/checkout@v6
         env:
           GITHUB_TOKEN: ${{ steps.obtainToken.outputs.token }}
       - name: Setup

.gitignore

@@ -2,7 +2,6 @@
 
 # dependencies
 node_modules
-.pnpm-store/
 .pnp
 .pnp.js
 .idea/
@@ -58,6 +57,7 @@ apps/tasks/tasks.cjs
 apps/tasks/tasks.css
 apps/websocket/wssServer.cjs
 apps/websocket/wssServer.css
+apps/nextjs/customServer.cjs
 apps/nextjs/.million/
 packages/cli/cli.cjs
 
@@ -67,16 +67,8 @@ e2e/shared/tmp
 #personal backgrounds
 apps/nextjs/public/images/background.png
 
+# next-intl
+en.d.json.ts
 
-
-# personal agent config
-.opencode
-.agents/*
-!.agents/skills/
-skills-lock.json
-
-# docusaurus
-apps/docs/.docusaurus
-apps/docs/build
-.pnpm-store
-benchmark-results
+# Custom server build artifacts
+apps/nextjs/customServer.css

.mcp.json

@@ -1,8 +0,0 @@
-{
-  "mcpServers": {
-    "mantine": {
-      "command": "npx",
-      "args": ["-y", "@mantine/mcp-server"]
-    }
-  }
-}

.mise.toml

@@ -1,2 +0,0 @@
-[tools]
-node = "24.18.0"

.npmrc

@@ -1,2 +1,6 @@
-# pnpm v11: non-auth settings moved to pnpm-workspace.yaml
-# Keep this file for any future registry/auth configuration
+# Expo doesn't play nice with pnpm by default. 
+# The symbolic links of pnpm break the rules of Expo monorepos.
+# @link https://docs.expo.dev/guides/monorepos/#common-issues
+node-linker=hoisted
+strict-peer-dependencies=false
+engine-strict=true

.nvmrc

@@ -1 +1 @@
-24.18.0
+24.14.0

.oxfmtrc.json

@@ -1,7 +0,0 @@
-{
-  "$schema": "./node_modules/oxfmt/configuration_schema.json",
-  "printWidth": 120,
-  "endOfLine": "lf",
-  "sortPackageJson": true,
-  "ignorePatterns": ["**/*.cjs", "**/lang/**", "static-data/**", "CHANGELOG.md", "apps/docs/.docusaurus/**", "apps/docs/build/**", "apps/docs/blog/**"]
-}

.oxlintrc.json

@@ -1,37 +0,0 @@
-{
-  "$schema": "./node_modules/oxlint/configuration_schema.json",
-  "plugins": ["eslint", "typescript", "unicorn", "oxc", "react", "import", "jsx-a11y"],
-  "categories": {
-    "correctness": "error",
-    "suspicious": "warn",
-    "pedantic": "off",
-    "perf": "off",
-    "style": "off",
-    "restriction": "off",
-    "nursery": "off"
-  },
-  "rules": {
-    "eslint/no-unused-vars": ["error", { "argsIgnorePattern": "^_", "varsIgnorePattern": "^_" }],
-    "typescript/consistent-type-imports": ["warn", { "prefer": "type-imports", "fixStyle": "separate-type-imports" }],
-    "typescript/no-non-null-assertion": "error",
-    "import/consistent-type-specifier-style": ["error", "prefer-top-level"],
-    "unicorn/no-new-array": "warn",
-    "unicorn/no-useless-spread": "warn",
-    "unicorn/no-useless-length-check": "warn",
-    "unicorn/no-useless-fallback-in-spread": "warn",
-    "jsx-a11y/prefer-tag-over-role": "warn",
-    "oxc/const-comparisons": "warn",
-    "react-hooks/exhaustive-deps": "warn",
-    "react/no-children-prop": "warn",
-    "jsx-a11y/no-autofocus": "warn",
-    "jsx-a11y/img-redundant-alt": "warn",
-    "react/react-in-jsx-scope": "off"
-  },
-  "options": {
-    "reportUnusedDisableDirectives": "off"
-  },
-  "ignorePatterns": ["**/*.config.js", "**/*.config.mjs", "**/*.cjs", "**/lang/*.d.json.ts", ".next/**", "apps/docs/.docusaurus/**", "apps/docs/build/**"],
-  "settings": {
-    "react": { "version": "19" }
-  }
-}

.vscode/extensions.json

@@ -1,7 +1,7 @@
 {
   "recommendations": [
     "dbaeumer.vscode-eslint",
-    "oxc.oxc-vscode",
+    "esbenp.prettier-vscode",
     "yoavbls.pretty-ts-errors",
     "million.million-lint",
     "lokalise.i18n-ally"

.vscode/i18n-ally-custom-framework.yml

@@ -31,5 +31,6 @@ scopeRangeRegex: "(?:const|let|var)\\s+t\\s*=\\s*(?:await\\s+)?(?:getScopedI18n|
 # refactorTemplates:
 #  - i18n.get("$1")
 
+
 # If set to true, only enables this custom framework (will disable all built-in frameworks)
-monopoly: true
+monopoly: true

.vscode/launch.json

@@ -15,7 +15,9 @@
       "request": "launch",
       "command": "pnpm docker:dev",
       "cwd": "${workspaceFolder}",
-      "skipFiles": ["<node_internals>/**"]
+      "skipFiles": [
+        "<node_internals>/**"
+      ]
     },
     {
       "name": "lint fix",
@@ -23,7 +25,9 @@
       "request": "launch",
       "command": "pnpm lint:fix",
       "cwd": "${workspaceFolder}",
-      "skipFiles": ["<node_internals>/**"]
+      "skipFiles": [
+        "<node_internals>/**"
+      ]
     },
     {
       "name": "format fix",
@@ -31,7 +35,9 @@
       "request": "launch",
       "command": "pnpm format:fix",
       "cwd": "${workspaceFolder}",
-      "skipFiles": ["<node_internals>/**"]
+      "skipFiles": [
+        "<node_internals>/**"
+      ]
     },
     {
       "name": "db push",
@@ -63,7 +69,9 @@
       "request": "launch",
       "command": "pnpm test",
       "cwd": "${workspaceFolder}",
-      "skipFiles": ["<node_internals>/**"]
+      "skipFiles": [
+        "<node_internals>/**"
+      ]
     },
     {
       "name": "test ui",
@@ -71,7 +79,9 @@
       "request": "launch",
       "command": "pnpm test:ui",
       "cwd": "${workspaceFolder}",
-      "skipFiles": ["<node_internals>/**"]
+      "skipFiles": [
+        "<node_internals>/**"
+      ]
     }
   ]
 }

.vscode/settings.json

@@ -1,6 +1,13 @@
 {
-  "js/ts.tsdk.path": "node_modules\\typescript\\lib",
+  "eslint.workingDirectories": [
+    {
+      "mode": "auto"
+    }
+  ],
+  "eslint.experimental.useFlatConfig": true,
+  "typescript.tsdk": "node_modules\\typescript\\lib",
   "js/ts.implicitProjectConfig.experimentalDecorators": true,
+  "prettier.configPath": "./tooling/prettier/index.mjs",
   "cSpell.words": [
     "ajnart",
     "cqmin",
@@ -27,7 +34,11 @@
   ],
   "i18n-ally.dirStructure": "auto",
   "i18n-ally.displayLanguage": "en",
-  "i18n-ally.enabledFrameworks": ["custom"],
-  "i18n-ally.localesPaths": ["packages/translation/src/lang"],
-  "i18n-ally.keystyle": "nested"
+  "i18n-ally.enabledFrameworks": [
+    "custom"
+  ],
+  "i18n-ally.localesPaths": [
+    "packages/translation/src/lang",
+  ],
+  "i18n-ally.keystyle": "nested",
 }

AGENTS.md

@@ -1,102 +0,0 @@
-# Homarr Agent Rules
-
-## Repository Structure
-
-```
-homarr/
-├── apps/
-│   ├── nextjs/          # Main Next.js application (port 3000)
-│   ├── docs/            # Docusaurus 3 documentation site (@homarr/docs)
-│   ├── tasks/           # Cron job runner + Fastify tRPC API (port 3002)
-│   └── websocket/       # Standalone tRPC WebSocket server (port 3001)
-├── packages/
-│   ├── api/             # tRPC appRouter, procedures, OpenAPI
-│   ├── auth/            # NextAuth config, providers, session, API keys
-│   ├── db/              # Drizzle schema (3 DB drivers), migrations, queries
-│   ├── core/            # Env validation, DB/Redis driver factories, logging
-│   ├── definitions/     # Domain enums: WidgetKind, IntegrationKind, permissions
-│   ├── widgets/         # All 39 dashboard widgets (definitions + components)
-│   ├── integrations/    # Integration classes (HTTP clients to external apps)
-│   ├── redis/           # Redis pub/sub channels, caching abstractions
-│   ├── translation/     # next-intl setup, locale configs, lang JSON files
-│   ├── ui/              # Shared Mantine components, theme, hooks
-│   ├── validation/      # Shared zod schemas for API/forms
-│   ├── common/          # Shared utilities, IDs, errors
-│   ├── cron-jobs/       # Cron job implementations (25+ jobs)
-│   ├── cron-jobs-core/  # Cron scheduling primitives
-│   ├── cron-job-status/ # Cron status via Redis
-│   ├── boards/          # Board context, edit mode, cache updater
-│   ├── modals/          # Modal primitives on Mantine
-│   ├── modals-collection/ # Feature modals (apps, boards, docker, etc.)
-│   ├── form/            # useZodForm (Mantine + zod resolver)
-│   ├── forms-collection/# Reusable form UIs (new app, icon picker, upload)
-│   ├── spotlight/       # Command palette / search with multiple modes
-│   ├── request-handler/ # Server request handlers (feeds, integrations)
-│   ├── notifications/   # Mantine notifications wrapper
-│   ├── docker/          # Dockerode-based Docker access
-│   ├── icons/           # Icon DB/repo integration
-│   ├── image-proxy/     # Image proxy + caching
-│   ├── ping/            # Reachability / ping utilities
-│   ├── analytics/       # Server-side analytics (Umami)
-│   ├── server-settings/ # Server setting keys/types
-│   ├── settings/        # User-facing settings UI context
-│   ├── old-import/      # Legacy Homarr import
-│   ├── old-schema/      # Legacy Homarr zod schemas
-│   └── cli/             # Node CLI for ops (brocli)
-├── tooling/
-│   ├── typescript/      # Base tsconfig
-│   └── github/          # CI setup action
-├── tools/
-│   └── homarr-dev/      # Go CLI for local and PR Docker images
-├── development/         # Dev docker-compose (Redis, MySQL, PostgreSQL)
-├── e2e/                 # E2E test specs
-└── Dockerfile           # Multi-stage production build
-```
-
-## Documentation Sync
-
-The documentation site lives at `apps/docs/` (Docusaurus 3, `@homarr/docs`).
-
-When modifying user-facing code, you MUST also update the corresponding documentation:
-
-- New integration → `apps/docs/docs/integrations/<slug>/index.mdx` + `index.ts`
-- New widget → `apps/docs/docs/widgets/<slug>/index.mdx` + `index.ts`
-- Changed API → `apps/docs/docs/management/api.mdx`
-- New/changed env vars → `apps/docs/docs/advanced/`
-- New CLI commands → `apps/docs/docs/advanced/command-line/`
-- Auth changes → `apps/docs/docs/advanced/` SSO pages
-- New cron job → `apps/docs/docs/management/tasks.mdx`
-
-## Monorepo Commands
-
-- `pnpm dev` — Next.js app only
-- `pnpm dev:cli -- dev` — run the developer CLI without installing a global binary
-- `pnpm db:seed` — seed default database data explicitly
-- `pnpm docker:dev:up` — start the Redis development service in the background
-- `pnpm dev:docs` — Docusaurus docs site only
-- `pnpm turbo build` — build all packages
-- `pnpm turbo build --filter=@homarr/docs` — build docs only
-- `pnpm turbo typecheck` — typecheck all packages
-- `pnpm lint` / `pnpm format` — oxlint / oxfmt
-
-## Code Style
-
-- Lint: oxlint (not ESLint)
-- Format: oxfmt (not Prettier)
-- UI: Mantine (not Tailwind) — Tailwind is only used in docs app
-- Mantine: use the `mantine` MCP server (configured in `.mcp.json`; tools `get_item_doc` / `get_item_props` / `search_docs`) for current v9 APIs before writing component code. Prefer built-in primitives (`Combobox`/`useCombobox` for selects, the polymorphic `component` prop, `@mantine/hooks`) over hand-rolled equivalents. Check `packages/ui/` for existing conventions first.
-
-## MCP servers
-
-`.mcp.json` at the repo root declares project-scoped MCP servers (the standard Claude Code layout; other tools can import the same `mcpServers` block). See the `mantine` entry there for the Mantine v9 server, and the upstream docs at https://mantine.dev/guides/llms/ for per-tool setup (OpenCode: `.opencode/opencode.json`, Codex: `.codex/config.toml`). Only keyless server definitions belong in `.mcp.json`; anything needing secrets stays in local dotfiles.
-
-## Agent Skills
-
-Portable agent skills live in `.agents/skills/` (the Agent Skills open standard). Cursor, Codex, and OpenCode read `.agents/skills/` natively. Claude Code does not scan it, so `.claude/skills/` is a symlink back to `.agents/skills/`. Install skills at `.agents/skills/<name>/SKILL.md` — that single copy is used everywhere. See `.agents/skills/` for available skills (documentation-sync, mcp-integration, codebase-context, datatable-migration).
-
-- Icons: @tabler/icons-react
-- Docs app can import from `@homarr/definitions` for shared types
-- Run `pnpm dev:cli -- dev` to browse local `homarr:*` images and remote PR images.
-- Run `pnpm dev:cli -- build <name>` from a Homarr checkout to build `homarr:<name>` with rebuild provenance.
-- Run `pnpm dev:cli -- build --pr <number>` to build a PR locally from a temporary checkout.
-- Run Go checks from `tools/homarr-dev` with `go test ./...` and `go vet ./...`.

APPROACHES.md

@@ -0,0 +1,369 @@
+# Memory Optimization Approaches
+
+This document describes the approaches tried and considered for reducing the RAM footprint of Homarr's server processes.
+
+## Baseline Architecture (Before)
+
+Homarr runs **three separate Node.js processes**:
+
+| Process | Port | Purpose |
+|---|---|---|
+| `apps/nextjs` (Next.js) | 3000 | Web UI + API routes |
+| `apps/websocket` (WS server) | 3001 | tRPC WebSocket subscriptions |
+| `apps/tasks` (Tasks/Cron server) | 3002 | Cron job scheduling + management API |
+
+Each process loads its own V8 heap, duplicates shared dependencies (`@homarr/db`, `@homarr/auth`, etc.), and runs its own event loop.
+
+**Measured baseline (dev mode, idle):** ~2,954 MB total RSS
+
+---
+
+## Approach 1: Integrate WebSocket Server into Next.js Custom Server
+
+**Status:** ✅ Implemented
+
+Eliminates `apps/websocket` by handling WebSocket upgrades inside a [Next.js custom server](https://nextjs.org/docs/pages/guides/custom-server):
+
+```ts
+const app = next({ dev, hostname, port, dir });
+const upgradeHandler = app.getUpgradeHandler();
+
+server.on("upgrade", (req, socket, head) => {
+  if (req.url?.startsWith("/websockets")) {
+    wss.handleUpgrade(req, socket, head, (ws) => wss.emit("connection", ws, req));
+  } else {
+    upgradeHandler(req, socket, head); // HMR, etc.
+  }
+});
+```
+
+### PROs
+- Eliminates one V8 heap (~208 MB)
+- WebSocket runs on same port as HTTP (simpler networking/proxying)
+- Shared `@homarr/db` connection pool and module cache
+- `getUpgradeHandler()` properly delegates HMR to Next.js in dev mode
+
+### CONs
+- Custom server disables some Next.js optimizations (automatic static optimization still works with `output: "standalone"`)
+- WebSocket errors could affect the main server process
+- Slightly more complex startup code
+
+---
+
+## Approach 2: Integrate Tasks/Cron Server into Next.js Custom Server
+
+**Status:** ✅ Implemented (combined with Approach 1)
+
+Eliminates `apps/tasks` by running the Fastify tRPC cron API and job scheduler inside the same process:
+
+```ts
+async function startTasksServer() {
+  const tasksServer = fastify({ maxParamLength: 5000 });
+  tasksServer.register(fastifyTRPCPlugin, { ... });
+  await cleanupSessionsAsync();
+  await invalidateUpdateCheckerCacheAsync();
+  await jobGroup.initializeAsync();
+  await jobGroup.startAllAsync();
+  await tasksServer.listen({ port: CRON_JOB_API_PORT });
+  return tasksServer;
+}
+```
+
+### PROs
+- Eliminates another V8 heap (~328 MB)
+- Shared database connection pool across Next.js API routes and cron jobs
+- Single process to manage (simpler Docker, `run.sh`, monitoring)
+- Cron jobs can directly share in-memory state with the web server
+
+### CONs
+- A misbehaving cron job could affect web request latency
+- Fastify still binds to port 3002 for internal tRPC communication (minor overhead)
+- More dependencies in the custom server bundle
+
+---
+
+## Combined Result (Approaches 1 + 2)
+
+| Component | Separate (before) | Integrated (after) |
+|---|---|---|
+| WebSocket server | ~208 MB | — |
+| Tasks/Cron server | ~328 MB | — |
+| Next.js (incl. workers) | ~2,418 MB | — |
+| Custom Server (all-in-one) | — | ~2,007 MB |
+| **Total RSS** | **~2,954 MB** | **~2,007 MB** |
+| **Savings** | — | **~947 MB (~32%)** |
+
+---
+
+## Approach 3: Eliminate Fastify — Direct Function Calls for Cron API
+
+**Status:** 📋 Considered, not implemented
+
+Since the cron job API client (`cronJobApi`) is only used from Next.js API routes (same process now), we could replace the HTTP+tRPC client with direct function calls to `JobManager`:
+
+```ts
+// Before: HTTP call to localhost:3002/trpc
+await cronJobApi.trigger.mutate({ name: "myJob" });
+
+// After: direct call in same process
+await jobManager.triggerAsync("myJob");
+```
+
+### PROs
+- Eliminates Fastify dependency and port 3002 listener entirely
+- Zero network overhead for cron API calls
+- Simpler architecture (no internal HTTP, no API key needed)
+
+### CONs
+- Requires refactoring `packages/api/src/router/cron-jobs.ts` and `packages/cron-job-api`
+- Breaks the clean separation between Next.js API and tasks concerns
+- If the architecture ever splits back to separate processes, this would need to be reverted
+- API key authentication for cron operations would need a different mechanism
+
+---
+
+## Approach 4: Node.js `--max-old-space-size` Flag
+
+**Status:** 📋 Considered, available as user override
+
+Setting `NODE_OPTIONS=--max-old-space-size=N` limits V8 heap growth and forces more aggressive garbage collection.
+
+```dockerfile
+# Example: limit heap to 512 MB
+ENV NODE_OPTIONS="--max-old-space-size=512"
+```
+
+### PROs
+- Can reduce peak memory usage in constrained environments
+- Easy to configure via environment variable
+- No code changes required
+
+### CONs
+- Too low a value causes OOM crashes under load
+- Doesn't reduce actual memory *needed*, just forces earlier GC
+- Default Node.js behavior (~1.7 GB limit on 64-bit) is reasonable for most deployments
+- Different deployments have different memory constraints — no single good default
+
+**Recommendation:** Don't set a default in the Dockerfile. Document as a tuning option for users running on low-memory hosts (e.g., `docker run -e NODE_OPTIONS="--max-old-space-size=512"`).
+
+---
+
+## Approach 5: Next.js `output: "standalone"` (Already in Use)
+
+**Status:** ✅ Already configured
+
+The `next.config.ts` already uses `output: "standalone"`, which:
+- Traces only the files needed for production
+- Creates a minimal `.next/standalone` directory
+- Avoids shipping full `node_modules`
+
+This is already optimized and no further action needed.
+
+---
+
+## Approach 6: Shared Redis Connection Pooling
+
+**Status:** 📋 Considered, not implemented
+
+With all services in one process, Redis connection pools could be shared. Currently, each module may create its own Redis client instance.
+
+### PROs
+- Fewer open connections to Redis
+- Slightly less memory for connection buffers
+
+### CONs
+- Marginal memory savings (Redis connections are lightweight)
+- Requires auditing all Redis usage across packages
+- Risk of connection contention under high load
+
+---
+
+## Summary of Recommendations
+
+| Approach | Impact | Effort | Status |
+|---|---|---|---|
+| 1. Integrate WS server | ~208 MB saved | Low | ✅ Done |
+| 2. Integrate Tasks server | ~328 MB saved | Medium | ✅ Done |
+| 3. Eliminate Fastify | ~10-30 MB saved | High | 📋 Future |
+| 4. `--max-old-space-size` | Configurable | None | 📋 User option |
+| 5. Standalone output | Already optimal | None | ✅ Already done |
+| 6. Shared Redis pools | ~5-10 MB saved | Medium | 📋 Future |
+| 7. Redis-backed initial query data | Faster page loads | Medium | 📋 POC documented |
+| 8. Client-side rendering with ISR shell | Faster TTFB | High | 📋 POC documented |
+
+---
+
+## Approach 7: Redis-Backed TanStack Query Initial Data
+
+**Status:** 📋 POC documented
+
+### Problem
+
+Currently, the dashboard page (`/`) is fully server-rendered on every request:
+
+1. Server calls `api.board.getHomeBoard()` (database query)
+2. Server prefetches all widget data via `prefetchForKindAsync()` (multiple database/integration queries)
+3. Server renders the full React tree with hydration boundary
+4. Client hydrates and takes over
+
+Each page load triggers a cascade: **Client → Next.js Server → tRPC → Database → Back**. For data that doesn't change often (board layout, widget configurations), this is wasteful.
+
+### Approach
+
+Use Redis as a shared cache layer between cron jobs and page loads. Cron jobs already populate Redis with integration data. The idea is to:
+
+1. **Cron jobs write to Redis** (already happening via `createItemAndIntegrationChannel`)
+2. **Server reads from Redis first** instead of hitting the database for widget data
+3. **Pass Redis data as `initialData`** to TanStack Query on the client
+4. **Client-side queries take over** with stale-while-revalidate behavior
+
+```tsx
+// POC: In _creator.tsx, read from Redis cache first for widget prefetching
+import { createItemAndIntegrationChannel } from "@homarr/redis";
+
+// Instead of always calling the database:
+const cachedData = await redisChannel.getAsync();
+if (cachedData) {
+  // Use cached data as initial query data - skip the database call
+  queryClient.setQueryData(queryKey, cachedData.data);
+} else {
+  // Fall back to normal prefetch
+  await prefetchForKindAsync(kind, queryClient, items);
+}
+```
+
+On the client side, TanStack Query's `initialData` option lets us hydrate from cache:
+
+```tsx
+// Client component using cached initial data
+const { data } = useQuery({
+  queryKey: ["widget", widgetId],
+  queryFn: () => fetchWidgetData(widgetId),
+  initialData: cachedWidgetData, // From Redis via server props
+  staleTime: 30_000, // Consider fresh for 30s
+});
+```
+
+### How TanStack Query Initial Data Works
+
+From the [TanStack Query docs](https://tanstack.com/query/v5/docs/framework/react/guides/initial-query-data):
+
+- `initialData` pre-populates the query cache before the component mounts
+- The query still revalidates in the background (stale-while-revalidate)
+- Combined with `staleTime`, the query won't refetch until the data is considered stale
+- This means the page renders instantly with cached data, then silently updates
+
+### PROs
+- **Faster page loads**: Redis reads are ~1ms vs ~50-200ms for database queries with joins
+- **Reduced database load**: Most page views hit Redis instead of SQLite/MySQL/PostgreSQL
+- **Leverages existing infrastructure**: Cron jobs already write widget data to Redis channels
+- **Graceful degradation**: Falls back to normal database queries on cache miss
+- **Non-breaking**: Can be adopted incrementally per widget type
+- **Shared across users**: Non-personal data (board layout, widget data) is the same for all users viewing the same board
+
+### CONs
+- **Cache staleness**: Data may be up to one cron interval old (typically 1-5 minutes)
+- **Cache invalidation complexity**: Need to invalidate Redis when boards are edited
+- **Memory usage**: More data stored in Redis (marginal since it's already stored for pub/sub)
+- **Serialization overhead**: superjson parse/stringify on every cache read
+- **Testing complexity**: Need to test cache hit/miss/stale scenarios
+
+### Estimated Impact
+
+| Metric | Before | After (cache hit) | Improvement |
+|---|---|---|---|
+| Dashboard TTFB | ~200-500ms | ~50-100ms | 2-5x faster |
+| Database queries per page load | 5-20 (depending on widgets) | 0-2 (board + auth only) | ~90% reduction |
+| Redis reads per page load | 0 | 5-20 | Acceptable (~1ms each) |
+
+### Implementation Path
+
+1. Create a `createBoardCacheChannel(boardId)` in `@homarr/redis`
+2. Populate it when boards are saved and when cron jobs update widget data
+3. In `_creator.tsx`, check cache before `prefetchForKindAsync()`
+4. Set `staleTime` to match cron interval for each widget type
+5. Add cache invalidation when boards are edited (`board.saveBoard` mutation)
+
+---
+
+## Approach 8: Client-Side Rendering with ISR Static Shell
+
+**Status:** 📋 POC documented (not recommended for Homarr's use case)
+
+### Concept
+
+Instead of server-rendering the entire dashboard on each request, serve a **static HTML shell** via Next.js ISR (Incremental Static Regeneration) and let the client fetch all dynamic content via TanStack Query.
+
+```tsx
+// Hypothetical ISR dashboard page
+export const revalidate = 60; // Regenerate every 60 seconds
+
+export default function DashboardPage() {
+  // Return a static shell - no server-side data fetching
+  return (
+    <DashboardShell>
+      <Suspense fallback={<BoardSkeleton />}>
+        <ClientBoard /> {/* Fetches via useQuery on mount */}
+      </Suspense>
+    </DashboardShell>
+  );
+}
+```
+
+The client component would then fetch everything:
+
+```tsx
+"use client";
+
+function ClientBoard() {
+  const { data: board, isLoading } = clientApi.board.getHomeBoard.useQuery(undefined, {
+    initialData: undefined, // Could be populated from Redis via API route
+  });
+
+  if (isLoading) return <BoardSkeleton />;
+  return <BoardContent board={board} />;
+}
+```
+
+### How Next.js ISR Works
+
+- On first request, Next.js generates the page and caches it
+- Subsequent requests serve the cached HTML instantly (TTFB ~0ms for CDN)
+- After `revalidate` seconds, the next request triggers background regeneration
+- The stale page is served until the new one is ready (stale-while-revalidate)
+
+### PROs
+- **Near-instant TTFB**: Static HTML served from disk/CDN cache
+- **Reduced server CPU**: No React SSR on every request
+- **Scalable**: Static pages can be served by any CDN or reverse proxy
+- **Good for public boards**: Shared boards viewed by many users benefit most
+
+### CONs
+- **Layout shift (CLS)**: Dashboard appears empty then fills in — bad UX for dashboards
+- **No SSR for SEO**: Not relevant for Homarr (it's a private dashboard app)
+- **Slower perceived load**: Users see a skeleton for 200-500ms while queries run
+- **Authentication complexity**: ISR pages must be the same for all users. Homarr's dashboard is user-specific (permissions, board access), making ISR caching ineffective for the page itself
+- **Breaks existing hydration pattern**: The current `HydrationBoundary` + `dehydrate()` pattern works well and ensures no layout shift
+- **WebSocket subscriptions delayed**: Real-time updates don't start until client JS loads and connects
+
+### Benchmark Comparison (Theoretical)
+
+| Metric | Current (SSR) | Approach 7 (Redis initial data) | Approach 8 (ISR + CSR) |
+|---|---|---|---|
+| TTFB | 200-500ms | 50-100ms | ~10ms (static) |
+| Time to Interactive | 200-500ms | 50-100ms | 200-500ms (same) |
+| Largest Contentful Paint | 200-500ms | 50-100ms | 400-800ms (worse) |
+| Cumulative Layout Shift | ~0 | ~0 | 0.1-0.3 (worse) |
+| Server CPU per request | High | Low | Near zero |
+
+### Recommendation
+
+**Approach 7 (Redis-backed initial data) is recommended over Approach 8 (ISR)** for Homarr because:
+
+1. **Dashboards are personalized**: Board access depends on user permissions, making ISR page-level caching ineffective
+2. **No layout shift**: Users expect the dashboard to appear fully rendered
+3. **Existing infrastructure**: Redis + cron jobs already provide the cache layer needed
+4. **Incremental adoption**: Can be applied per-widget without changing the overall rendering strategy
+5. **ISR is designed for content sites**: Blog posts, documentation pages, product pages — not interactive dashboards with real-time WebSocket subscriptions
+
+ISR could still be useful for specific Homarr pages like `/manage/about` or documentation pages that don't depend on user state, but the main dashboard is not a good candidate.

CHANGES.md

@@ -1,96 +0,0 @@
-# Changes
-
-## Goal
-
-Remove widget-only services from Homarr's global Integration system.
-
-The affected services are release providers and Search.ch. They are only used by specific widgets, so keeping them as global integrations added unnecessary setup, UI, database rows, docs pages, and integration package code.
-
-ArchiveTeam Warrior remains a proper integration but is no longer auto-seeded on first install.
-
-## Why
-
-These services do not need shared integration state.
-
-- Release providers are selected per Releases widget repository.
-- Search.ch is only used by the Timetable widget.
-
-Moving them into widget options makes configuration simpler and removes dead-weight integration code from `packages/integrations`.
-
-## What Changed
-
-### Release Providers
-
-- Added release provider definitions in `packages/definitions/src/release-provider.ts`.
-- Removed release providers from `IntegrationKind`.
-- Moved release-fetching code out of `packages/integrations` and into `packages/request-handler/src/release-providers.ts`.
-- Updated the Releases widget to store provider configuration directly in widget options:
-  - `provider`
-  - `identifier`
-  - `versionFilter`
-  - `providerUrl`
-- Updated the Releases widget editor to use a provider select instead of an integration select.
-- Updated Docker import mapping so `ghcr.io` maps to `gitHubContainerRegistry`.
-- GitHub Container Registry now uses the public OCI registry API and accepts full image references such as `ghcr.io/homarr-labs/homarr:latest`.
-
-### Timetable / Search.ch
-
-- Removed Search.ch as an integration.
-- Added a Timetable widget `baseUrl` option, defaulting to `https://search.ch`.
-- Moved Search.ch request/parsing logic into `packages/request-handler/src/timetable.ts`.
-- Updated the Timetable API to receive `baseUrl` directly from widget options.
-
-### ArchiveTeam Warrior
-
-- Kept as a proper integration (not removed).
-- Removed `defaultUrl` from the integration definition to prevent auto-seeding on first install.
-
-### Integration Cleanup
-
-- Removed creators, exports, docs references, and implementation files for the deleted integrations.
-- Removed unused dependencies from `packages/integrations/package.json`.
-
-### Database Migration
-
-- Added `packages/db/migrations/custom/0003_remove_widget_only_integrations.ts`.
-- The migration moves old integration-linked widget config into widget options, then deletes the old widget-only integration rows.
-- Updated the earlier release widget migration to use the new `provider` field instead of `providerIntegrationId`.
-
-### Docs
-
-- Updated Releases widget docs to describe providers instead of integrations.
-- Updated Timetable docs to remove Search.ch integration setup.
-- Removed obsolete integration docs pages for the deleted integration kinds.
-- Updated docs sitemap and integration docs mappings.
-
-### Translations
-
-- Added English labels for the new widget options:
-  - `widget.timetable.option.baseUrl.label`
-  - `widget.releases.option.repositories.providerUrl.label`
-
-## How It Works Now
-
-Release provider configuration lives on each Releases widget repository entry. The request handler resolves provider metadata and fetches releases directly from the provider-specific endpoint. GHCR uses anonymous OCI registry access for public packages.
-
-Timetable passes its widget URL option directly to its API router and request handler. No global integration lookup is needed.
-
-ArchiveTeam Warrior continues to use the standard integration system, but users must manually add the integration (it is not auto-created on install).
-
-## Deliberate Non-Goals
-
-- No provider secret/token support was added.
-- No new secret storage model was introduced.
-- No compatibility layer was kept in `packages/integrations`.
-
-Widget options are client-visible, so storing provider credentials there would be wrong. If authenticated provider requests are needed later, they need a separate secret-storage design.
-
-## Verification So Far
-
-- Focused typechecks passed for affected packages.
-- Full `pnpm turbo typecheck` passed.
-- Full `pnpm lint` passed with existing warnings.
-- Focused release provider normalization tests passed.
-- Widget translation test passed.
-- Live GHCR smoke checks passed for `ghcr.io/muchobien/pocketbase:latest` and `ghcr.io/homarr-labs/homarr:latest`.
-- `pnpm test packages/integrations/test/pi-hole.spec.ts` passed earlier, but failed on rebased reruns because Pi-hole reported `domainsBeingBlocked` as `-2`/`0` instead of `> 1`.

CODEOWNERS

@@ -1,234 +1,9 @@
 # ── CODEOWNERS ───────────────────────────────────────
 * @homarr-labs/maintainers
 
-# Specific features / integrations
-# These owners come from the PR that introduced each integration implementation.
-# Specific rules override the global fallback because CODEOWNERS uses the last
-# matching pattern; do not include @homarr-labs/maintainers here unless they
-# should also be requested for that integration.
-
-# AdGuard Home - introduced in https://github.com/homarr-labs/homarr/pull/929 by @hillaliy
-apps/docs/docs/integrations/adguard-home @hillaliy
-packages/integrations/src/adguard-home @hillaliy
-
-# Anchor - introduced in https://github.com/homarr-labs/homarr/pull/5040 by @ohmzi
-apps/docs/docs/integrations/anchor @ohmzi
-packages/integrations/src/anchor @ohmzi
-
-# ArchiveTeam Warrior - introduced in https://github.com/homarr-labs/homarr/pull/5784 by @darbyjack
-apps/docs/docs/integrations/archive-team-warrior @darbyjack
-packages/integrations/src/archive-team-warrior @darbyjack
-
-# Bazarr - introduced in https://github.com/homarr-labs/homarr/pull/6156 by @Ayush7614
-apps/docs/docs/integrations/bazarr @Ayush7614
-apps/docs/docs/widgets/bazarr @Ayush7614
-packages/api/src/router/widgets/bazarr.ts @Ayush7614
-packages/integrations/src/bazarr @Ayush7614
-packages/request-handler/src/bazarr.ts @Ayush7614
-packages/widgets/src/bazarr @Ayush7614
-
-# Audiobookshelf - introduced in https://github.com/homarr-labs/homarr/pull/5910 by @ajnart
-apps/docs/docs/integrations/audiobookshelf @ajnart
-packages/integrations/src/audiobookshelf @ajnart
-
-# Beszel - introduced in https://github.com/homarr-labs/homarr/pull/5900 by @ajnart
-apps/docs/docs/integrations/beszel @ajnart
-packages/integrations/src/beszel @ajnart
-
-# Codeberg - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/codeberg @Aandree5
-packages/integrations/src/codeberg @Aandree5
-
-# Coolify - introduced in https://github.com/homarr-labs/homarr/pull/4789 by @Rhiz3K
-apps/docs/docs/integrations/coolify @Rhiz3K
-packages/integrations/src/coolify @Rhiz3K
-
-# Dash. - introduced in https://github.com/homarr-labs/homarr/pull/1541 by @manuel-rw
-apps/docs/docs/integrations/dash-dot @manuel-rw
-packages/integrations/src/dashdot @manuel-rw
-
-# Docker Hub - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/docker-hub @Aandree5
-packages/integrations/src/docker-hub @Aandree5
-
-# Emby - introduced in https://github.com/homarr-labs/homarr/pull/2466 by @Meierschlumpf
-apps/docs/docs/integrations/emby @Meierschlumpf
-packages/integrations/src/emby @Meierschlumpf
-
-# GitHub - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/github @Aandree5
-packages/integrations/src/github @Aandree5
-
-# GitHub Container Registry - introduced in https://github.com/homarr-labs/homarr/pull/3727 by @Aandree5
-apps/docs/docs/integrations/github-containerregistry @Aandree5
-packages/integrations/src/github-container-registry @Aandree5
-
-# GitLab - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/gitlab @Aandree5
-packages/integrations/src/gitlab @Aandree5
-
-# Glances - introduced in https://github.com/homarr-labs/homarr/pull/5102 by @manuel-rw
-apps/docs/docs/integrations/glances @manuel-rw
-packages/integrations/src/glances @manuel-rw
-
-# Gluetun - introduced in https://github.com/homarr-labs/homarr/pull/5812 by @Lok3sh-kumar
-apps/docs/docs/integrations/gluetun @Lok3sh-kumar
-packages/integrations/src/gluetun @Lok3sh-kumar
-
-# Gotify - introduced in https://github.com/homarr-labs/homarr/pull/5847 by @Nerdy-Technician
-apps/docs/docs/integrations/gotify @Nerdy-Technician
-packages/integrations/src/gotify @Nerdy-Technician
-
-# Home Assistant - introduced in https://github.com/homarr-labs/homarr/pull/578 by @manuel-rw
-apps/docs/docs/integrations/home-assistant @manuel-rw
-packages/integrations/src/homeassistant @manuel-rw
-
-# ICal - introduced in https://github.com/homarr-labs/homarr/pull/3980 by @NicolasNewman
-apps/docs/docs/integrations/ical @NicolasNewman
-packages/integrations/src/ical @NicolasNewman
-
-# Immich - introduced in https://github.com/homarr-labs/homarr/pull/5165 by @manuel-rw
-apps/docs/docs/integrations/immich @manuel-rw
-packages/integrations/src/immich @manuel-rw
-
-# Jellyfin - introduced in https://github.com/homarr-labs/homarr/pull/672 by @manuel-rw
-apps/docs/docs/integrations/jellyfin @manuel-rw
-packages/integrations/src/jellyfin @manuel-rw
-
-# Jellyseerr - introduced in https://github.com/homarr-labs/homarr/pull/774 by @manuel-rw
-apps/docs/docs/integrations/jellyseerr @manuel-rw
-packages/integrations/src/jellyseerr @manuel-rw
-
-# LinuxServer.io - introduced in https://github.com/homarr-labs/homarr/pull/3607 by @Aandree5
-apps/docs/docs/integrations/linux-server-io @Aandree5
-packages/integrations/src/linuxserverio @Aandree5
-
-# Navidrome - introduced in https://github.com/homarr-labs/homarr/pull/5910 by @ajnart
-apps/docs/docs/integrations/navidrome @ajnart
-packages/integrations/src/navidrome @ajnart
-
-# Nextcloud - introduced in https://github.com/homarr-labs/homarr/pull/2501 by @manuel-rw
-apps/docs/docs/integrations/nextcloud @manuel-rw
-packages/integrations/src/nextcloud @manuel-rw
-
-# npm - introduced in https://github.com/homarr-labs/homarr/pull/3253 by @Aandree5
-apps/docs/docs/integrations/npm @Aandree5
-packages/integrations/src/npm @Aandree5
-
-# ntfy - introduced in https://github.com/homarr-labs/homarr/pull/2900 by @itzTheMeow
-apps/docs/docs/integrations/ntfy @ajnart @manuel-rw
-packages/integrations/src/ntfy @ajnart @manuel-rw
-
-# OpenMediaVault - introduced in https://github.com/homarr-labs/homarr/pull/1142 by @hillaliy
-apps/docs/docs/integrations/open-media-vault @hillaliy
-packages/integrations/src/openmediavault @hillaliy
-
-# OPNsense - introduced in https://github.com/homarr-labs/homarr/pull/3424 by @Oupsman
-apps/docs/docs/integrations/opnsense @Oupsman
-packages/integrations/src/opnsense @Oupsman
-
-# Overseerr - introduced in https://github.com/homarr-labs/homarr/pull/774 by @manuel-rw
-apps/docs/docs/integrations/overseerr @manuel-rw
-packages/integrations/src/overseerr @manuel-rw
-
-# Paperless-ngx - introduced in https://github.com/homarr-labs/homarr/pull/5910 by @ajnart
-apps/docs/docs/integrations/paperless-ngx @ajnart
-packages/integrations/src/paperless-ngx @ajnart
-
-# PatchMon - introduced in https://github.com/homarr-labs/homarr/pull/6119 by @mrjoshuap
-apps/docs/docs/integrations/patchmon @mrjoshuap
-packages/integrations/src/patchmon @mrjoshuap
-packages/widgets/src/patchmon @mrjoshuap
-packages/api/src/router/widgets/patchmon.ts @mrjoshuap
-packages/request-handler/src/patchmon.ts @mrjoshuap
-
-# PeaNUT - introduced in https://github.com/homarr-labs/homarr/pull/5862 by @afonsojramos
-apps/docs/docs/integrations/peanut @afonsojramos
-packages/integrations/src/peanut @afonsojramos
-
-# Pi-hole - introduced in https://github.com/homarr-labs/homarr/pull/521 by @Meierschlumpf
-apps/docs/docs/integrations/pi-hole @Meierschlumpf
-packages/integrations/src/pi-hole @Meierschlumpf
-
-# Plex - introduced in https://github.com/homarr-labs/homarr/pull/1342 by @hillaliy
-apps/docs/docs/integrations/plex @hillaliy
-packages/integrations/src/plex @hillaliy
-
-# Prowlarr - introduced in https://github.com/homarr-labs/homarr/pull/965 by @hillaliy
-apps/docs/docs/integrations/prowlarr @hillaliy
-packages/integrations/src/prowlarr @hillaliy
-
-# Proxmox - introduced in https://github.com/homarr-labs/homarr/pull/1969 by @Meierschlumpf
-apps/docs/docs/integrations/proxmox @Meierschlumpf
-packages/integrations/src/proxmox @Meierschlumpf
-
-# Quay - introduced in https://github.com/homarr-labs/homarr/pull/3607 by @Aandree5
-apps/docs/docs/integrations/quay @Aandree5
-packages/integrations/src/quay @Aandree5
-
-# search.ch - introduced in https://github.com/homarr-labs/homarr/pull/5180 by @Meierschlumpf
-apps/docs/docs/integrations/search-ch @Meierschlumpf
-packages/integrations/src/search-ch @Meierschlumpf
-
-# Speedtest Tracker - introduced in https://github.com/homarr-labs/homarr/pull/5363 by @kylegrieder
-apps/docs/docs/integrations/speedtest-tracker @kylegrieder
-packages/integrations/src/speedtest-tracker @kylegrieder
-
-# Synology - introduced in https://github.com/homarr-labs/homarr/pull/6121 by @mrjoshuap
-apps/docs/docs/integrations/synology @mrjoshuap
-packages/integrations/src/synology @mrjoshuap
-
-# Technitium DNS - introduced in https://github.com/homarr-labs/homarr/pull/5832 by @lopsch
-apps/docs/docs/integrations/technitium-dns @lopsch
-packages/integrations/src/technitium @lopsch
-
-# Tracearr - introduced in https://github.com/homarr-labs/homarr/pull/5060 by @StrandedTurtle
-apps/docs/docs/integrations/tracearr @StrandedTurtle
-packages/integrations/src/tracearr @StrandedTurtle
-
-# TrueNAS - introduced in https://github.com/homarr-labs/homarr/pull/3745 by @manuel-rw
-apps/docs/docs/integrations/truenas @manuel-rw @afonsojramos
-packages/integrations/src/truenas @manuel-rw @afonsojramos
-
-# Umami - introduced in https://github.com/homarr-labs/homarr/pull/5362 by @febrile42
-apps/docs/docs/integrations/umami @febrile42
-packages/integrations/src/umami @febrile42
-
-# UniFi Controller - introduced in https://github.com/homarr-labs/homarr/pull/2236 by @pitschi
-apps/docs/docs/integrations/unifi-controller @pitschi
-packages/integrations/src/unifi-controller @pitschi
-
-# Unraid - introduced in https://github.com/homarr-labs/homarr/pull/4439 by @manuel-rw
-apps/docs/docs/integrations/unraid @manuel-rw
-packages/integrations/src/unraid @manuel-rw
-
-# Uptime Kuma - introduced in https://github.com/homarr-labs/homarr/pull/5910 by @ajnart
-apps/docs/docs/integrations/uptime-kuma @ajnart
-packages/integrations/src/uptime-kuma @ajnart
-
-# What's Up Docker (WUD) - introduced in https://github.com/homarr-labs/homarr/pull/6523 by @tiimonn
-apps/docs/docs/integrations/whats-up-docker @tiimonn
-apps/docs/docs/widgets/whats-up-docker @tiimonn
-packages/api/src/router/widgets/wud.ts @tiimonn
-packages/integrations/src/wud @tiimonn
-packages/request-handler/src/wud.ts @tiimonn
-packages/widgets/src/wud @tiimonn
-
-# Traefik - by @Nerdy-Technician
-apps/docs/docs/integrations/traefik @Nerdy-Technician
-apps/docs/docs/widgets/traefik @Nerdy-Technician
-packages/api/src/router/widgets/traefik.ts @Nerdy-Technician
-packages/integrations/src/traefik @Nerdy-Technician
-packages/request-handler/src/traefik.ts @Nerdy-Technician
-packages/widgets/src/traefik @Nerdy-Technician
-
-# Exempt Renovate-managed files (no owners)
+# Exempt Renovate‑managed files (no owners)
 package.json
-**/package.json
 package-lock.json
-**/package-lock.json
 pnpm-lock.yaml
-**/pnpm-lock.yaml
-pnpm-workspace.yaml
 Dockerfile
 docker-compose.yml

Dockerfile

@@ -1,53 +1,24 @@
-# syntax=docker/dockerfile:1.25
-
-FROM node:24.18.0-alpine AS base
+FROM node:24.14.0-alpine AS base
 
 FROM base AS builder
-ARG TARGETPLATFORM
+RUN apk add --no-cache libc6-compat
+RUN apk update
+
+# Set working directory
 WORKDIR /app
-# Native dependencies normally use prebuilds, but the build must remain
-# reproducible when a prebuild download times out and compilation is required.
-RUN apk add --no-cache libc6-compat curl bash python3 make g++
-
-RUN corepack enable pnpm
-COPY .npmrc pnpm-lock.yaml pnpm-workspace.yaml package.json ./
-COPY patches ./patches
-COPY --parents ./apps/*/package.json ./packages/*/package.json ./tooling/*/package.json ./
-# @homarr/definitions generates documentation types during install.
-COPY --parents ./packages/definitions/src ./
-# Workaround for pnpm/pnpm#5268: pnpm fetch crashes when patchedDependencies
-# are configured with nodeLinker: hoisted. The applyPatchToDir function tries
-# to chdir into node_modules/<pkg> which doesn't exist during fetch (only the
-# content-addressable store is populated). By temporarily switching to the
-# isolated linker, patches apply inside the virtual store (node_modules/.pnpm/...)
-# which IS created by pnpm fetch. The original hoisted linker is restored
-# before the install step so the final node_modules layout stays flat.
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
-    pnpm config set store-dir /pnpm/store && \
-    sed -i 's/nodeLinker: hoisted/nodeLinker: isolated/' pnpm-workspace.yaml && \
-    pnpm fetch --ignore-scripts && \
-    sed -i 's/nodeLinker: isolated/nodeLinker: hoisted/' pnpm-workspace.yaml
-
-# Install only from the fetched, committed lockfile so local and Docker builds
-# resolve the same dependency graph. Serial lifecycle builds avoid esbuild's
-# atomic binary replacement racing across the hoisted workspace (pnpm/pnpm#8200).
-RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
-    npm_config_nodedir=/usr/local pnpm install --recursive --offline --frozen-lockfile --child-concurrency=1
-
+RUN apk add --no-cache libc6-compat curl bash
+RUN apk update
 COPY . .
 
+RUN corepack enable pnpm && pnpm install --recursive --frozen-lockfile
+
+# Copy static data as it is not part of the build
+COPY static-data ./static-data
 ARG SKIP_ENV_VALIDATION='true'
 ARG CI='true'
 ARG DISABLE_REDIS_LOGS='true'
-ARG TARGETPLATFORM
 
-RUN --mount=type=secret,id=TURBO_API,env=TURBO_API \
-    --mount=type=secret,id=TURBO_TEAM,env=TURBO_TEAM \
-    --mount=type=secret,id=TURBO_TOKEN,env=TURBO_TOKEN \
-    --mount=type=secret,id=TURBO_REMOTE_CACHE_SIGNATURE_KEY,env=TURBO_REMOTE_CACHE_SIGNATURE_KEY \
-    --mount=type=cache,id=homarr-next-build-${TARGETPLATFORM},target=/app/apps/nextjs/.next/cache,sharing=locked \
-    TURBO_PLATFORM="${TARGETPLATFORM:-linux/amd64}" \
-    pnpm turbo build --filter=@homarr/nextjs... --filter=@homarr/cli
+RUN corepack enable pnpm && pnpm build
 
 FROM base AS runner
 WORKDIR /app
@@ -71,8 +42,8 @@ RUN mkdir -p /var/cache/nginx && \
 
 COPY --from=builder /app/apps/nextjs/next.config.ts .
 COPY --from=builder /app/apps/nextjs/package.json .
-COPY --from=builder /app/pnpm-workspace.yaml ./pnpm-workspace.yaml
 
+COPY --from=builder /app/apps/nextjs/customServer.cjs ./apps/nextjs/customServer.cjs
 COPY --from=builder /app/node_modules/better-sqlite3/build/Release/better_sqlite3.node /app/build/better_sqlite3.node
 
 COPY --from=builder /app/packages/db/migrations ./db/migrations
@@ -95,6 +66,5 @@ ENV AUTH_PROVIDERS='credentials'
 ENV REDIS_IS_EXTERNAL='false'
 ENV NODE_ENV='production'
 
-EXPOSE 7575
 ENTRYPOINT [ "/app/entrypoint.sh" ]
 CMD ["sh", "run.sh"]

apps/docs/.dockerignore

@@ -1,6 +0,0 @@
-Dockerfile
-.dockerignore
-node_modules
-npm-debug.log
-README.md
-.git

apps/docs/.gitattributes

@@ -1 +0,0 @@
-* text=auto eol=lf

apps/docs/.gitignore

@@ -1,58 +0,0 @@
-# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
-.idea/
-
-# dependencies
-/node_modules
-/.pnp
-.pnp.js
-.pnpm-store/
-
-# testing
-/coverage
-
-# next.js
-/.next/
-/out/
-
-# production
-/build
-
-# misc
-.DS_Store
-*.pem
-
-# debug
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-
-# local env files
-.env.local
-.env.development.local
-.env.test.local
-.env.production.local
-
-# vercel
-.vercel
-*.tsbuildinfo
-
-# storybook
-storybook-static
-static/data/configs
-
-# https://yarnpkg.com/getting-started/qa#which-files-should-be-gitignored
-# Yarn v2
-.pnp.*
-.yarn/*
-!.yarn/patches
-!.yarn/plugins
-!.yarn/releases
-!.yarn/sdks
-!.yarn/versions
-
-# docusaurus
-.docusaurus
-
-# CI Stuff
-screenshots
-test-results

apps/docs/.oxlintrc.json

@@ -1,30 +0,0 @@
-{
-  "$schema": "../../node_modules/oxlint/configuration_schema.json",
-  "plugins": ["eslint", "typescript", "unicorn", "oxc", "react", "import", "jsx-a11y"],
-  "categories": {
-    "correctness": "error",
-    "suspicious": "warn",
-    "pedantic": "off",
-    "perf": "off",
-    "style": "off",
-    "restriction": "off",
-    "nursery": "off"
-  },
-  "rules": {
-    "eslint/no-unused-vars": ["warn", { "argsIgnorePattern": "^_", "varsIgnorePattern": "^_" }],
-    "typescript/consistent-type-imports": "off",
-    "typescript/no-non-null-assertion": "warn",
-    "import/consistent-type-specifier-style": "off",
-    "jsx-a11y/alt-text": "warn",
-    "jsx-a11y/control-has-associated-label": "warn",
-    "jsx-a11y/prefer-tag-over-role": "warn",
-    "react/jsx-key": "warn",
-    "react/react-in-jsx-scope": "off",
-    "react-hooks/exhaustive-deps": "warn",
-    "eslint/no-unused-expressions": "warn"
-  },
-  "ignorePatterns": ["**/*.config.js", "**/*.config.mjs", "**/*.cjs", ".docusaurus/**", "build/**"],
-  "settings": {
-    "react": { "version": "19" }
-  }
-}

apps/docs/.vscode/settings.json

@@ -1,10 +0,0 @@
-{
-    "cSpell.words": [
-        "Homarr",
-        "Lidarr",
-        "Nextcloud",
-        "Radarr",
-        "Readarr",
-        "Sonarr"
-    ]
-}

apps/docs/LICENSE

@@ -1,201 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright (c) 2025 Meier Lukas, Thomas Camlong and Homarr Labs
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

apps/docs/README.md

@@ -1,105 +0,0 @@
-# Homarr Documentation (`@homarr/docs`)
-
-The official [homarr.dev](https://homarr.dev) documentation site, built with [Docusaurus 3](https://docusaurus.io/) and living inside the Homarr monorepo.
-
-## Why it's in the monorepo
-
-Having documentation alongside the application code enables:
-
-- **Two-way linking** — the docs app imports from `@homarr/definitions` for type-safe integration/widget metadata, and the main app references doc paths via generated sitemap types
-- **Atomic PRs** — code changes and their documentation updates ship in the same pull request
-- **Shared tooling** — same Node version, pnpm catalog, oxlint/oxfmt, CI pipeline
-- **Build-time validation** — Docusaurus strict mode catches broken links and references at build time
-
-## Development
-
-From the **monorepo root**:
-
-```bash
-# Start the docs dev server (port 3003)
-pnpm dev:docs
-
-# Or from within this directory
-pnpm dev
-```
-
-## Build
-
-```bash
-# Build docs only
-pnpm turbo build --filter=@homarr/docs
-
-# Build everything (docs + main app + tasks + websocket)
-pnpm build
-```
-
-## Lint & Format
-
-Uses oxlint and oxfmt (same as the rest of the monorepo):
-
-```bash
-pnpm lint        # oxlint
-pnpm format      # oxfmt (check)
-pnpm format -- --write  # oxfmt (fix)
-```
-
-## Typecheck
-
-```bash
-pnpm typecheck
-```
-
-## Content Structure
-
-```
-docs/
-├── getting-started/    # Installation guides, glossary, prerequisites
-├── management/         # Boards, apps, users, integrations, settings, tasks, API
-├── integrations/       # 56 integration guides (one folder each)
-├── widgets/            # 43 widget guides (one folder each)
-├── advanced/           # SSO, env vars, proxy, styling, CLI, development
-└── community/          # FAQ, donate, license, translations, get-in-touch
-```
-
-Each integration/widget doc follows a consistent pattern:
-
-- `index.ts` — typed metadata (`IntegrationDefinition` / `WidgetDefinition`)
-- `index.mdx` — content using shared React components (`IntegrationHeader`, `WidgetHeader`, etc.)
-
-## Importing from homarr packages
-
-The docs app has `@homarr/definitions` as a workspace dependency. You can import integration kinds, widget kinds, and other definitions directly:
-
-```typescript
-import { IntegrationKind } from '@homarr/definitions';
-```
-
-This enables type-safe references to homarr domain concepts within documentation code.
-
-## Search (Algolia DocSearch)
-
-Search uses the `Docusaurus` Algolia index (crawler `cd77a285-2756-4557-bf21-ee703748df15`). A separate `markdown` index is built for LLM markdown indexing.
-
-Crawler reference config: [`docsearch.config.js`](docsearch.config.js).
-
-**Verify search health:**
-
-```bash
-pnpm verify:search
-```
-
-## Tech Stack
-
-| Layer | Technology |
-|---|---|
-| Site generator | Docusaurus 3 (`@docusaurus/preset-classic`) |
-| Styling | Tailwind CSS 3 + Docusaurus Infima |
-| Icons | `@tabler/icons-react` |
-| Diagrams | Mermaid (`@docusaurus/theme-mermaid`) |
-| Search | Algolia DocSearch |
-| Analytics | PostHog |
-| Charts | @nivo/line |
-
-## Contributing
-
-When making changes to the homarr codebase that affect user-facing behavior, **always update the corresponding documentation in this app**. See `.cursor/rules/documentation-sync.mdc` for the complete mapping of code changes to doc locations.

apps/docs/blog/2022/06-22-documentation/index.mdx

@@ -1,35 +0,0 @@
----
-slug: documentation-migration
-title: Migration of Documentation
-authors:
-  - ajnart
-  - manuel-rw
-tags: [documentation, migration]
----
-
-We are happy to announce that the documentation of Homarr has been migrated to Docusaurus - An opensource documentation tool.
-The documentation has been re-written partly and includes now many animations, guides and additional crucial information.
-
-We are still figuring things out and highly depend on your feedback.
-
-<!-- truncate -->
-
-## Why we migrated
-
-The default GitHub Wiki feature is decent - but very confusing to read.
-Our possibilites for searching the documentation in the Wiki are highly limited.
-Additionally, Users are unable to contribute to the documentation if they have not sufficient permissions.
-
-We could not review any chanegs made to the documentation. This is why we migrated to Docusaurus.
-
-## How you can contribute
-
-The documentation will soon be merged into the master branch of Homarr.
-You'll find a ``doc/`` directory in the root of Homarr.
-We'll obviously not include this in our Docker images.
-In the future, everyone may modify the documentation by creating a pull request.
-After we've reviewed your changes, we'll merge your PR and this documentation will automatically update.
-
-## TL;DR
-
-The documentation on GitHub Wiki will soon disappear. It will be replaced with this Docusaurus-powered website. You'll find much more information here with higher detail and searchability.

apps/docs/blog/2022/08-28-translation/index.mdx

@@ -1,20 +0,0 @@
----
-slug: translations
-title: Help us make Homarr multilingual
-authors:
-  - ajnart
-  - manuel-rw
-tags: [translations, homarr, update, contributions]
----
-
-We've been working hard to offer Homarr in many languages. The next update of Homarr will be using [i18next](https://www.i18next.com/) to translate almost any part of your Dashboard.
-
-### We need your help
-![](img/homarr-we-need-you.webp) <br/>
-Yes, we need **YOU**! We want to make Homarr accessible to as many people as possible. Thus, we need to translate all content into many different languages. We need your help for that! [You can help us now to translate Homarr into as many languages as possible](/docs/community/translations).
-
-<!-- truncate -->
-
-### About global translations / translations per user
-
-We are aware that many people would like to configure translations globally or configure language per user. Currently, translations are stored in the Cookies, which will expire after some time (currently, it's set to 30 days). We will implement more granular language settings in future versions of Homarr, since it requires major changes to Homarr. Stay tuned! 😎

apps/docs/blog/2023/01-11-version0.11/index.mdx

@@ -1,67 +0,0 @@
----
-title: "We present: Homarr 0.11 - the most complex Homarr version yet!"
-authors:
-  - ajnart
-  - manuel-rw
-  - walkx
-  - meierschlumpf
-tags: [homarr, update, breaking changes, version, gridstack, dnd, documentation]
----
-
-We are *incredibly* proud to serve you Homarr 0.11!
-It contains many breaking changes and huge improvements to your favourite dashboard app:
-
-- Integration of Gridstack for much more complex dashboard configuration and drag and drop
-- Added icon picker with smart search and automatic icons
-- Complete overhaul of the module system
-- Added an edit mode for making changes easier
-- Form validation for better user experience
-- Better security with new built-in credentials system
-- Huge design and usability improvements to older components to Homarr
-- Better handeling of exceptions and unexpected issues
-
-<!-- truncate -->
-
-## Complete implementation of highly customizable drag and drop library "Gridstack"
-
-In 0.11, we have replaced our quite limited drag and drop system with Gridstack.
-Gridstack enables you to create much more complex and advanced dashboards while keeping everything organized.
-
-<video style={{ maxWidth: "min(100%, 600px)", borderRadius: "0.5rem"}} controls preload='auto' autoplay >
-  <source src="https://user-images.githubusercontent.com/30572287/217098893-5880e7de-13d0-42c5-b505-f7921593396f.mp4" type="video/mp4" />
-    <p>
-      To view this video please enable JavaScript, and consider upgrading to a
-      web browser that
-      <a href="https://videojs.com/html5-video-support/" target="_blank">
-        supports HTML5 video
-      </a>
-  </p>
-</video>
-
-We've also introduced more advanced categories this time:
-
-![](../../../docs/getting-started/img/category-menu.webp)
-
-We'll continute to improve this system according to your feedback.
-
-## Modules have been overhauled and renamed to widgets
-
-Widgets are now much snappier and have been completely recoded.
-This fixes some of the bugs a few users have previously experienced and improves overall customization.
-
-![](./img/choose-widget-in-modal.webp)
-
-## Fancy icon picker for speeding up your creation process
-
-We've also added a new fancy icon picker, you can use to get access to any icons much faster.
-We will add more icon sources in the future, as we made this icon picker very modular, and we plan to make local icons accessible via this picker very soon.
-
-![](../../../docs/advanced/customizations/img/icons/icons-picker.gif)
-
-## Design and documentation improvements to homarr.dev
-
-https://homarr.dev has been overhauled with better design, updated documentation, more images and better explanations.
-
-## Download Homarr now!
-
-Homarr is completly free, even for commercial usage!

apps/docs/blog/2023/04-16-version0.12-more-widgets/index.mdx

@@ -1,75 +0,0 @@
----
-title: "We present: Homarr 0.12 - The fastest homarr version ever!"
-authors:
-  - ajnart
-  - manuel-rw
-  - walkx
-  - meierschlumpf
-tags: [homarr, update, breaking changes, version, dnd, documentation]
----
-
-## Multiple widgets of the same type
-**It's finally here!** You can decorate your dashboard now with as many widgets as you want.
-This applies to all widgets, but in the case of the IFrame widget, it enables you to:
-- Integrate as many websites as you want
-- Integrate monitoring tools like Grafana, Splunk or Elasticsearch
-- Integrate your services (for example Sonarr, Radarr and Overseerr) directly into Homarr
-
-![](https://media.discordapp.net/attachments/988335098493542410/1094665745226539168/update-teaser.png?width=1046&height=666)
-
-## Edit mode password
-We've added a setting to disable editing completely. This will allow you to restrict edit access without password-protection.
-use the `EDIT_MODE_PASSWORD` ENV variable to set a password for edit mode. 
-turn on `DISABLE_EDIT_MODE=TRUE` to disable edit mode on startup.
-
-<!-- truncate -->
-
-## 😎 Blazingly fast
-We've implemented a new caching system, that will cache all data in your browser, meaning that Homarr will load within milliseconds, as if it was *powered by rust and blazingly fast* !!!
-
-## Media request widgets (Overseerr & Jellyseerr)
-We've implemented a new widget, that displays a history of all requests.
-You can't approve from the widget yet, but we plan to add this in the future.
-
-![image](https://user-images.githubusercontent.com/30572287/231829411-f61f03e9-79a0-45fc-9a87-94d69ea3ea84.png)
-
-## Multiple RSS feeds
-You can now consume multiple RSS feeds at the same time:
-
-![image](https://user-images.githubusercontent.com/30572287/231829886-69133a84-3ae7-4fa3-a6d2-c582f4cc9eea.png)
-
-## Tab refresh / close confirmation
-Since some have lost their changes, by refreshing the page in the edit mode. We've added a popup that will ask you to confirm you want to reload the page :
-
-![image](https://user-images.githubusercontent.com/30572287/231823776-9cbb12d4-3cb3-422e-b2e8-f9917bb3f8cc.png)
-
-## Environment variable for default theme
-You can now set the default color scheme using environment variables:
-
-``DEFAULT_COLOR_SCHEME`` = ``[dark, light]``
-
-## Global error catching for widgets
-Previously, widgets were able to crash your entire dashboard and just a blank page would be displayed.
-Now, users will still be able to use their dashboard and an information message will be displayed instead.
-
-## Migration to Mantine V6
-We've migrated Mantine to version 6. This will bring some upstream changes for responsiveness and usability.
-
-## Fix width and height in the calendar
-In 0.11.5 and previous versions, the calendar scaled poorly if the widget was resized.
-Now, the calendar will fill out the entire available space and scale nicely with your dashboard.
-
-![](https://cdn.discordapp.com/attachments/988335098493542410/1095416419816067175/homarr-calendar-scaling.gif)
-
-## Performance improvements
-We now use several methods to improve performance and reduce network requests.
-Homarr will load now within milliseconds and cache data in your browser.
-
-## Docker Socket via TCP
-Previously, it was not possible to mount sockets via TCP (eg. ``tcp://traefik-docker-socket-proxy:2375``).
-Now, you can use the following environment variables to configure this:
-
-- ``DOCKER_HOST``
-- ``DOCKER_PORT``
-
-**Full Changelog**: https://github.com/ajnart/homarr/compare/v0.11.5...v0.12.0

apps/docs/blog/2023/11-10-authentication/index.mdx

@@ -1,86 +0,0 @@
----
-title: "Authentication in Homarr - 0.14 is here!"
-authors:
-  - ajnart
-  - manuel-rw
-  - tagashi
-  - meierschlumpf
-tags: [homarr, update, breaking changes, version, authentication, notepad, security]
----
-
-One of the most requested features ever has arrived.
-We worked for months to prepare Homarr for this update and we're happy that we can finally
-provide you a viable solution today.
-
-## Highlights at a glance
-
-- :rocket: Completly overhauled authentication system with user management
-- :sparkles: Improved UI for boards (renamed dashboards to boards).
-- :computer: Server side preferences -> Dark mode and language are not synced accross all your devices
-- :link: Invitation links to easily onboard new users
-- :busts_in_silhouette: Overhauled board management with easy control if anonymous users can view your board
-- :brain:  AI assistant on the documentation to answer your questions: https://homarr.dev/
-- 📝 Overhauled notepad widget with a complex graphical editor that enables easy editing right from your browser.
-- :globe_with_meridians:  Live Translation on Crowdin that enable you to directly translate using images to see what exactly you're translating
-
-<!-- truncate -->
-
-## Breaking changes
-
-- Removed ``PASSWORD`` environment variable
-- Removed ``DISABLE_EDIT_MODE`` environment variable
-- Removed ``EDIT_MODE_PASSWORD`` environment variable
-- Added mounting point ``/data`` for your database
-- Require at least one administrator account on your instance. An onboarding process will automatically set this up.
-- We've added analytics to the documentation and Homarr itself. We use [Umami Analytics](https://umami.is/) which collects anonymous data exclusively and protects your personal data rights. You can disable this using the environment variable ``DISABLE_ANALYTICS``.
-
-## Changes in detail
-
-### Management pages
-![image](https://github.com/ajnart/homarr/assets/30572287/b325eb92-57a6-4b07-a281-f10f7471642e)
-One of the most requested features ever has been ___authentication___. We've completely *removed* the ``PASSWORD``, ``DISABLE_EDIT_MODE`` and ``EDIT_MODE_PASSWORD`` and replaced it by [a secure authentication system](https://next-auth.js.org/) that enables you to manage multiple users easily. We will allow for more detailed permission and user management soon. LDAP and OIDC integrations are currently also in progress and will arrive in a future version.
-
-### New dashboard layout
-![image](https://github.com/ajnart/homarr/assets/30572287/3396da13-816a-434f-a4c1-0efc7f86154c)
-
-We've updated the dashboard user interface slightly to an updated design.
-
-### Server side preferences page
-![image](https://github.com/ajnart/homarr/assets/30572287/2c1f4dbe-7aa7-4c56-aaa3-d6c49e2beeec)
-
-Previously, preferences were stored per dashboard and applied to all users.
-In this release, we moved this page to a separate link and store this on the server.
-This means that regardless what device your on - your preferences will stay the same when you're logged in.
-
-### Invitations for new users
-![image](https://github.com/ajnart/homarr/assets/30572287/a929b345-c014-48fb-aef9-ea2c3c581376)
-
-Tired of creating user accounts by yourself? With the new "invites" feature you can invite new users by simply sending them a link.
-This link is valid only once and must have an expiration date - more info on that in our documentation.
-
-Additionally, you can deny users, that are not logged into an account, to access your board with a simple toggle:
-
-![image](https://github.com/ajnart/homarr/assets/30572287/aa3ff3fb-66fc-4f88-93fb-b2dd819599a8)
-
-### New "boards" page
-Previously, dashboards were managed in an ugly and hard to control popup.
-We've moved this now to the new management pages as well and it's now much easier to control:
-
-![image](https://github.com/ajnart/homarr/assets/30572287/2b24222e-da33-45eb-a54f-89a33a21881d)
-
-
-### Read-only for non-administrators and guests
-Yes, managing access to your dashboard is now much easier!
-Guests and non-administrators cannot edit your dashboard in any way (edit is hidden):
-
-![image](https://github.com/ajnart/homarr/assets/30572287/01c48beb-5453-4626-ac4d-f8d7177e999b)
-
-This is not an definite solution and will be significantly improved in an upcoming update.
-
------
-
-We are aware that this update has many breaking changes and may confuse some users.
-For that reason, we updated our documentation and will enhance it further within the next few weeks.
-We've also added this small button at the bottom of the page were you can ask **your questions** to an AI assistant:
-
-![image](https://github.com/ajnart/homarr/assets/30572287/a56f721a-d022-42ad-813a-d85c89462a8c)

apps/docs/blog/2023/12-22-updated-documentation/index.mdx

@@ -1,21 +0,0 @@
----
-title: "Updated documentation with better organization & design"
-authors:
-  - manuel-rw
-tags: [homarr, documentation, design, docs]
----
-
-We'd like to let you know that we've updated our documentation and reorganized the pages.
-This means, that some links may no longer be valid - we apologise if this causes any inconvenience for you.
-
-<!-- truncate -->
-
-A few highlights include:
-
-- Updated navigation bar for much easier navigation
-- Improvements to the landing page
-- Completely revamped [about us page.](/about-us)
-- Bug fixes for image zoom
-- Added documentation for management pages and [new CLI tool](/docs/advanced/command-line/password-recovery/)
-
-Please [let us know](/docs/community/get-in-touch) is something is not working as expected.

apps/docs/blog/2024/09-23-version-1.0/index.mdx

@@ -1,88 +0,0 @@
----
-authors:
-  - manuel-rw
----
-
-# Homarr 1.0 - complete rewrite of all systems
-We proudly present to you - Homarr ``1.0``.
-We have started work on this new version back in 2023 and have worked tirelessly for months on this brand-new dashboard.
-
-This isn't our usual update. ``1.0`` doesn't use the same code from previous versions, but has been written from the ground up.
-Therefore, this version contains an unusual amount of breaking changes.
-This will be a one time occurrence and version > ``1.0`` will have less breaking changes.
-This time more important than every; **read the breaking changes** list and **create a backup** before updating.
-Some third party installation methods may take multiple days or weeks to update to the new version.
-
-See [this guide on how to import your previous Homarr dashboard](/docs/getting-started/after-the-installation#importing-a-zip-from-version-before-100)
-
-## Changes at a glance
-- **Asynchronous integrations system**: In versions prior to ``1.0``, we fetched data upon each request synchronously.
-This means that the user had to wait for the requests to finish so any data would appear.
-A page reload will trigger another request - and worse, this will happen for every user accessing your dashboard.
-In ``1.0``, we have implemented a new system that gets rid of this system and scales linearly.
-It will fetch data in background, even if you are not on the page.
-- **Permissions system**: You can now use detailed permissions to allow or prohibit users from certain actions.
-For easier management, you can organize users into groups and manage them all at the same time.
-- **Integration testing**: Starting from ``1.0``, we will require you to test the integration before you can use it.
-This guarantees that you've configured your integration correctly and helps you find errors faster.
-- **Re-imagined widgets**: All widgets have been rewritten & improved. They offer much better performance,
-reliability and scalability compared to < ``1.0``.
-- **Improved performance**: We have upgraded the underlying framework of Homarr and take advantage
-of an in-memory message bus and websockets to deliver data near realtime to you.
-
-<!-- truncate -->
-
-## Breaking changes
-:::warning
-
-Please consult the breaking changes list & upgrade guide if you used third-party installation methods.
-
-:::
-
-- Docker Image
-  - Removed support for ``arm/v7`` -> upgrade to newer architectures as an alternative
-  - Renamed image from ``ghcr.io/ajnart/homarr`` to ``ghcr.io/homarr-labs/homarr``. We now use semantic versioning for our release numbers.
-- Environment Variables
-  - New required env variable ``SECRET_ENCRYPTION_KEY`` used for encryption of secrets in the database
-  - Removed ``DISABLE_ANALYTICS``, can now be configured via UI
-  - Renamed ``AUTH_PROVIDER`` to ``AUTH_PROVIDERS``
-  - Renamed ``DATABASE_URL`` to ``DB_URL`` and made it optional conditionally. If ``DB_HOST`` is set, this is optional - otherwise it's required.
-  - Changed ``DOCKER_HOST`` to two new variables for hostnames (``DOCKER_HOSTNAMES``) and ports (``DOCKER_PORTS``). This allows for multiple docker integrations to be configured.
-  - ``AUTH_LOGOUT_REDIRECT_URL`` must now be a valid Url
-  - Increased minimum length of ``AUTH_OIDC_CLIENT_ID`` to 1
-  - Increased minimum length of ``AUTH_OIDC_CLIENT_SECRET`` to 1
-  - Removed ``AUTH_OIDC_TIMEOUT``
-  - Removed ``AUTH_LDAP_ADMIN_GROUP``, ``AUTH_LDAP_OWNER_GROUP``, ``AUTH_OIDC_ADMIN_GROUP`` and ``AUTH_OIDC_OWNER_GROUP`` -> groups are now managed without manual env binding
-  - ``CI`` will now also trigger an env validation skip like ``SKIP_ENV_VALIDATION``
-- Mounts
-  - Removed ``/app/data/configs`` -> JSON configs have been removed in favour of relation databases
-  - Removed ``/app/public/icons`` -> Images can not be uploaded via the [media management](/docs/management/media/) in the UI
-  - Moved ``/data`` to ``/appdata`` and restructured contents (not backwards compatible!) -> Create a backup before migration of the entire directory to copy data to new Homarr
-- Widgets:
-  - Calendar:
-    - Removed option ``Use Sonarr v4 API``
-    - Removed option ``Use Sonarr v5 API``
-    - Removed option ``Font Size``
-    - Removed option ``Hide week days``
-  - Download speed: We have removed this widget in favour of the brand new download widget which will also display this data.
-  - Dash. widget: We have removed this widget in favour of the System Health Widget. It will also display all data and some more than the old widget.
-- Database:
-  - Changed schema of the database to a completely new schema. They are not backwards compatible. Please export the data from old Homarr in the UI and import it in ``1.0``
-  - Removed all usage of JSON files to store data. Import JSON files in Homarr ``1.0`` to import your dashboards.
-  - Removed ``schemaVersion`` from JSON and use the drizzle migrations to keep track of schema versions and take care of migrations.
-- Web Server:
-  - Added an internal Nginx proxy to forward requests to two servers inside the container for technical reasons.
-  This could impact edge cases with iframes, cookies and custom setups.
-- Dependencies
-  - We now depend on [Redis](https://redis.io/) as a real time messaging bus
-- Development (relevant for contributors):
-  - Migrated to [pnpm](https://pnpm.io/)
-  - Migrated to a mono-repository
-  - All source code has been migrated to the [homarr-labs GitHub organization](https://github.com/homarr-labs)
-- Platform specific breaking changes:
-  - TrueNAS
-    - The TrueCharts app chart is permanently deprecated and no longer maintained / supported. Please migrate to Electric Eel or a different Kubernetes platform.
-  - Unraid
-    - The Homarr app must be reinstalled. The existing directories on your disk are not compatible with Homarr 1.0. Export your old data in < `` 1.0`` and install using different file system locations.
-  - Kubernetes
-    - The official Helm chart has moved from https://github.com/oben01/charts to https://github.com/homarr-labs/charts

apps/docs/blog/2024/12-17-open-beta-1.0/index.mdx

@@ -1,39 +0,0 @@
----
-authors:
-  - meierschlumpf
----
-
-# Open Beta 1.0
-
-We are proud to announce the open beta of Homarr 1.0. This is a major milestone for us and we are excited to share it with you.
-The open beta allows us to polish the last rough edges and gather feedback from you.
-We are looking forward to your feedback and hope you enjoy the new features.
-Let us know throgh discord or a [github issues](https://github.com/homarr-labs/homarr/issues/new/choose) if you encounter any issues.
-
-<!-- truncate -->
-
-## How to use the beta with docker
-
-To use the beta with docker you can use the following docker-compose.yml configuration:
-
-```yml title="docker-compose.yml"
-#---------------------------------------------------------------------#
-#     Homarr - A simple, yet powerful dashboard for your server.      #
-#---------------------------------------------------------------------#
-services:
-  homarr:
-    container_name: homarr
-    image: ghcr.io/homarr-labs/homarr:beta
-    restart: unless-stopped
-    volumes:
-      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
-      - ./homarr/appdata:/appdata
-    environment:
-      - SECRET_ENCRYPTION_KEY=your_64_character_hex_string # <--- can be generated with `openssl rand -hex 32`
-    ports:
-      - '7575:7575'
-```
-
-Then, run `docker compose up -d` in the same directory. This will start the Homarr container in the background.
-Please note that the mounts have changed and it's not backwards compatible with versions before 1.0.0-beta.1.
-You can find a list of all breaking changes [here](/blog/2024/09/23/version-1.0)

apps/docs/blog/2025/01-19-migration-guide-1.0/index.mdx

@@ -1,55 +0,0 @@
----
-authors:
-  - meierschlumpf
----
-
-# Migrate from 0.15.10+ to 1.0.0
-
-In this guide, we will show you how to migrate from Homarr 0.15.10+ to 1.0.0.
-If you are still on a version before 0.15.10, please update to 0.15.10 where we introduced the migration export page.
-
-<!-- truncate -->
-
-## Export your data
-
-As 1.0 is a complete rewrite of Homarr and therefor not compatible with the old docker mounts, we need to export your data first.
-For this you can navigate to the `Migrate to 1.0` page which you can find under `Management` > `Tools` > `Migrate to 1.0`.
-Here you can select which things you want to export and download the zip file.
-It will also show you a secret key which you will need to import the secret data like user password hashes, salts and integration secrets.
-
-![Export page](./img/old-homarr-export-data.png)
-
-## Create a parallel installation
-
-We highly recommend to create a parallel installation of Homarr 1.0.0.
-So if something with for example the import does not quite work, the data in the old installation is still available.
-To do this you can follow the appropriate [installation guide](https://homarr.dev/docs/category/installation-1) for your system.
-Please note that if you are using docker you need to specify a diffrent external port for the new installation as the old one had the same port.
-So in your compose file the ports would be `7576:7575` instead of `7575:7575`.
-
-## Import your data
-Once the installation is completed you can access the new installation. During the onboarding you'll need to select `Import from Homarr before 1.0`.
-
-![Onboarding initial step](./img/onboarding-step-1.png)
-
-After that you can upload the zip file you downloaded in the first step.
-
-![Onboarding import dropzone](./img/old-homarr-import-dropzone.png)
-
-After that you'll get a list with all your boards that can be imported. You can configure how it should be imported and can select which screensizes it should import.
-
-![Onboarding import list](./img/old-homarr-import-choose-imported-data.png)
-
-Once you have selected everything you can click on `Confirm import and continue` which will open the encryption key input dialog where you can input the secret key you got during the export.
-
-![Onboarding import key input](./img/old-homarr-import-decryption-token.png)
-
-After that you can continue the onboarding and you should see all your boards and data in the new installation.
-
-See [After the installation](https://homarr.dev/docs/getting-started/after-the-installation) for more information.
-
-## Remove the old installation
-
-After you are happy with the new installation and everything is working as expected you can remove the old installation.
-Please make sure to backup the data before you remove the old installation.
-Also once the port 7575 is free again you can change the port mapping of the new installation to `7575:7575` if you want to.

apps/docs/blog/2025/08-02-using-argus/index.mdx

@@ -1,67 +0,0 @@
----
-authors:
-  - meierschlumpf
----
-
-# How to use Argus with Homarr
-
-In `v1.32.0` we added the endpoint `/api/info` which returns the current version of Homarr and can therefore be used in Argus to watch for updates.
-This guide will show you how to set up a user with apiKey to access the endpoint without providing admin access through it.
-
-<!-- truncate -->
-
-![Argus](./img/argus.png)
-
-Currently an apiKey has the same permissions as the user who created it, however you can only create an apiKey with admin permissions.
-This means we have to do some extra steps to create a user with only the permissions we need for Argus.
-
-## Create a group
-
-In a first step we have to create a group which will allow us to restrict the permissions of the user we will create later.
-
-1. Go to `Management` > `Users` > `Groups`
-2. Click on `Create group`
-3. Enter a name for the group, e.g. `Argus`
-4. Click on `Create group`
-5. Click on the newly created group to edit it
-6. In the `Permissions` tab, select the admin permission and save the changes
-
-## Create a user
-
-Now we can create a user which will be used by Argus to access the `/api/info` endpoint.
-
-1. Go to `Management` > `Users` > `Manage`
-2. Click on `Create new user`
-3. Enter a username, e.g. `argus`, click next
-4. Enter a password for the user, click next
-5. Add previously created group `Argus` to the user, click next
-6. Click on next to confirm the user creation
-
-## Create an apiKey
-
-Now we want to create therefore we have to log in with the user we just created.
-
-1. Log out of Homarr
-2. Log in with the user we just created
-3. Go to `Management` > `Tools` > `API Keys`
-4. Click on `Create API Key`
-5. Copy the generated API key and save it somewhere, you will not be able to see it again
-6. Logout of Homarr
-
-## Reduce permissions of the user
-
-Now we can reduce the permissions of the user to only allow access to general authenticated, but not permission restricted endpoints.
-
-1. Log in with your admin user
-2. Go to `Management` > `Users` > `Groups`
-3. Click on the `Argus` group
-4. In the `Permissions` tab, remove all permissions
-5. Save the changes
-
-## Configure Argus
-
-Now you can configure Argus to use the user and apiKey we created.
-
-![Argus configuration](./img/argus-configuration.png)
-
-Replace the `<secret>` with the apiKey you created and the deployed version url with the url of your Homarr instance.

apps/docs/blog/authors.yml

@@ -1,37 +0,0 @@
-manuel-rw:
-  name: Manuel
-  page: true
-  url: https://github.com/manuel-rw
-  image_url: https://avatars.githubusercontent.com/u/30572287?v=4
-  socials:
-    github: manuel-rw
-  description: >
-    Junior .NET developer from Switzerland. 🌌 .NET, Next.js, Node.js, Angular
-ajnart:
-  name: Ajnart
-  page: true
-  url: https://github.com/ajnart
-  image_url: https://avatars.githubusercontent.com/u/49837342?v=4
-  socials:
-    github: ajnart
-meierschlumpf:
-  name: Meierschlumpf
-  page: true
-  url: https://github.com/Meierschlumpf
-  image_url: https://avatars.githubusercontent.com/u/63781622?v=4
-  socials:
-    github: Meierschlumpf
-tagashi:
-  name: Tagashi
-  page: true
-  url: https://github.com/tagaishi
-  image_url: https://avatars.githubusercontent.com/u/26098587?v=4
-  socials:
-    github: tagaishi
-walkx:
-  name: Walkx
-  page: true
-  url: https://github.com/walkxcode
-  image_url: https://avatars.githubusercontent.com/u/71191962?v=4
-  socials:
-    github: walkxcode

apps/docs/docs/advanced/_category_.json

@@ -1,9 +0,0 @@
-{
-  "label": "Advanced",
-  "collapsed": true,
-  "position": 4,
-  "link": {
-    "type": "generated-index",
-    "title": "Advanced Concepts or features"
-  }
-}

apps/docs/docs/advanced/command-line/_category_.json

@@ -1,4 +0,0 @@
-{
-  "collapsed": true,
-  "label": "Command line interface"
-}

apps/docs/docs/advanced/command-line/development/index.mdx

@@ -1,41 +0,0 @@
-# Developer Docker CLI
-
-The host-side developer CLI builds and runs local Homarr images and pull-request previews. Run it directly from a checkout with `pnpm dev:cli -- ...`; no shell-specific setup script is required. It is separate from the recovery CLI included in production images.
-
-To install an optional `homarr` binary, run `pnpm dev:cli:install` and make your Go bin directory available on `PATH`. GitHub CLI authentication is only needed for pull-request features.
-
-## Browse development images
-
-```bash
-pnpm dev:cli --
-```
-
-The main screen combines local `homarr:*` images with open pull requests and their GHCR preview status. Select an image to start or stop it, use `R` to build a remote pull request locally in the background or rebuild a local image, or use `p` to force a remote preview pull. Press `d` to switch to the instance dashboard and `d` again to return without losing the browser state. The explicit `dev` and `dash` subcommands start on either screen.
-
-A locally built PR image is folded into its remote PR row only when its recorded revision exactly matches the current GitHub head SHA. The row is marked `◆ local`, and starting it prefers that local image without a registry pull. Outdated local builds remain separate rows. Navigation and dashboard switching remain available during background builds.
-
-## Build images
-
-```bash
-pnpm dev:cli -- build <name>
-pnpm dev:cli -- build --pr <number> [name]
-```
-
-The first command builds the current checkout as `homarr:<name>`. The pull-request form uses a depth-one clone in a temporary directory and defaults to `homarr:pr-<number>` when `name` is omitted.
-
-## Rebuild images
-
-```bash
-pnpm dev:cli -- rebuild <name>
-```
-
-Images built by this CLI record their source checkout, revision, and optional pull-request number. Rebuild uses that provenance to select the original checkout or create a fresh temporary pull-request checkout.
-
-## Run images
-
-```bash
-homarr run <name>
-homarr run --pr <number>
-```
-
-Add `--detach` to run in the background, `--demo` to enable demo data, or repeat `--env KEY=VALUE` to provide additional environment variables.

apps/docs/docs/advanced/command-line/fix-usernames/index.mdx

@@ -1,17 +0,0 @@
-# Fix usernames
-
-:::info
-
-This guide requires that you understand [how to access the CLI](../).
-
-:::
-
-If you somehow get into a situation where you have users with usernames that contain uppercase characters and you are no longer able to log in, you can use the following command to fix the usernames.
-
-```bash
-homarr fix-usernames
-```
-
-This will convert all credential usernames to lowercase and update the database accordingly.
-
-![](./img/screenshot-cli.png)

apps/docs/docs/advanced/command-line/index.mdx

@@ -1,27 +0,0 @@
-# Command line interface
-
-The Homarr image ships with a built-in recovery tool. This can be useful, if you do not have access to Homarr or if something is not working.
-Please note that the CLI is an *emergency tool*, not an API tool.
-
-:::caution
-
-Using the recovery CLi tool can cause problems when requests are being sent to Homarr while the tool is running. \
-You should also create a backup of the database, in case you break something.
-
-:::
-
-## Execute CLI with Docker
-
-1. Execute ``docker ps | grep homarr`` on the root system with Docker to find the container ID of your Homarr container.
-2. Run ``docker exec -it <container-id> /bin/bash homarr <your-command-goes-here>``. \
-Replace ``<container-id>`` with your container ID from step 1. \
-Replace ``<your-command-goes-here>`` with the command you want to execute (see sub-pages).
-
-## Execute CLI with QNAP
-
-1. Open Container Station in the QNAP Web Interface ![](img/334116069-e7ec4726-3df7-4dc6-a3e0-b745e7eef17f.png)
-2. Select Containers in the menu bar on the left ![](img/334116205-aa09ce40-0701-4f7d-b9f9-b431b9d207c5.png)
-3. Select your Homarr Container ![](img/334116303-714b5e07-b9de-4ec0-a2bc-def7ee38750f.png)
-4. Click "Execute" in the top right of the Window. ![](img/334116411-df1482f9-3aa9-4686-b77f-e0dca09e60b2.png)
-5. Select /bin/bash and click Execute ![](img/334116518-e1ddb515-99c7-4159-81bf-76e889d1e808.png)
-6. Run the Homarr command and press enter (eg. homarr reset-owner-password) ![](img/334116642-08c4f204-5cd0-4e4e-a785-0142e1b279ca.png)

apps/docs/docs/advanced/command-line/integrations/index.mdx

@@ -1,60 +0,0 @@
-# Integrations
-
-:::info
-
-This guide requires that you understand [how to access the CLI](../).
-
-:::
-
-Using these commands, you can manage the integrations from the CLI:
-```bash
-Group of commands to manage integrations
-
-Usage:
-  homarr integrations [command]
-
-Available Commands:
-  list     List all integrations (id and name)
-  delete   Delete an integration by id or name
-
-Flags:
-  -h, --help      help for integrations
-  -v, --version   version for homarr-cli
-
-Use "homarr integrations [command] --help" for more information about a command.
-```
-
-## List Integrations
-
-- Requires a database connection
-- Lists all configured integrations
-
-```bash
-List all integrations (id and name)
-
-Usage:
-  homarr integrations list [flags]
-
-Flags:
-  -h, --help      help for integrations list
-  -v, --version   version for homarr-cli
-```
-
-## Delete Integration
-
-- Requires a database connection
-- Requires one parameter: ``id`` or ``name``
-- Deletes an integration permanently from the database
-
-```bash
-Delete an integration by id or name
-
-Usage:
-  homarr integrations delete [flags]
-
-Flags:
-  -i, --id string     ID of the integration
-  -n, --name string   Name of the integration
-  -h, --help          help for integrations delete
-  -v, --version       version for homarr-cli
-```

apps/docs/docs/advanced/command-line/password-recovery/index.mdx

@@ -1,19 +0,0 @@
-# Password Recovery
-
-:::info
-
-This guide requires that you understand [how to access the CLI](../).
-
-:::
-
-Using this command, you can forcefully reset the password of a user.
-It will be set to a random value and the hash for the user will be updated.
-All sessions for that user will be terminated and the user must re-login.
-
-![](./img/screenshot-cli.png)
-
-Using the ``--username`` parameter, you can specify who you want to reset the password for.
-Executing the command will create a new random password, update the database and display the new password.
-All sessions for this user will be terminated and they must re-login.
-
-![](./img/screenshot-cli-result.png)

apps/docs/docs/advanced/command-line/users/index.mdx

@@ -1,79 +0,0 @@
-# Users
-
-:::info
-
-This guide requires that you understand [how to access the CLI](../).
-
-:::
-
-Using these commands, you can manage the users from the CLI:
-```bash
-Group of commands to manage users
-
-Usage:
-  homarr users [command]
-
-Available Commands:
-  list              List all users (id, username, email)
-  delete            Delete a user by id or username
-  update-password   Update the password for a user (credentials provider only)
-
-Flags:
-  -h, --help      help for users
-  -v, --version   version for homarr-cli
-
-Use "homarr users [command] --help" for more information about a command.
-```
-
-## List Users
-
-- Requires a database connection
-
-```bash
-ID                              Username        Email
-yj52ek5cyb6du4bp4osbkjry        admin           xxxx@example.com
-yj52ek5cyb6du4bp4osbkjry        admin           xxxx@example.com
-yj52ek5cyb6du4bp4osbkjry        admin           xxxx@example.com
-yj52ek5cyb6du4bp4osbkjry        admin           xxxx@example.com
-yj52ek5cyb6du4bp4osbkjry        admin           xxxx@example.com
-yj52ek5cyb6du4bp4osbkjry        admin           xxxx@example.com
-```
-
-## Delete User
-
-- Requires a database connection
-- Requires one parameter: ``id`` or ``username``
-
-```bash
-Delete a user by id or username
-
-Usage:
-  homarr users delete [flags]
-
-Flags:
-  -i, --id string         ID of the user
-  -u, --username string   Name of the user
-  -h, --help              help for users delete
-  -v, --version           version for homarr-cli
-```
-
-## Update Password
-
-- Updates the password of an user
-- Requires database connection
-- Requires either a username or id
-- Requires a password (which will be encrypted by Homarr)
-
-```bash
-Update the password for a user (credentials provider only)
-
-Usage:
-  homarr users update-password [flags]
-
-Flags:
-  -i, --id string         ID of the user
-  -u, --username string   Name of the user
-  -p, --password          New password
-  -h, --help              help for users update-password
-  -v, --version           version for homarr-cli
-```