e3823ce470
Add an end-to-end and unit test suite for the SvelteKit frontend:
- Playwright e2e specs (tests/e2e/spa) with a throwaway container stack,
codegen scenarios, and an Istanbul-based coverage report pipeline.
- Vitest unit tests across API endpoints, components, stores and composables.
- `data-testid` hooks on interactive elements (AppShell, FileViewer,
ShareDialog, search, photos, files breadcrumbs, login/Nextcloud flows,
public share pages) so the e2e suite can target them deterministically.
- Serve the SPA app-shell CSP from a <meta> policy (svelte.config.js) plus a
middleware that skips the CSP header on HTML; move the Nextcloud Login Flow
v2 grant page to the SvelteKit /nextcloud/login route.
- `just front-codegen` recipe and start-server-spa.sh harness.
Make the test environment robust and consistent:
- Install a deterministic in-memory localStorage/sessionStorage in the Vitest
setup so storage behaves identically across Node versions (Node 26 ships a
native Web Storage global that otherwise shadows jsdom's).
- Pin devenv to Node 26 + PostgreSQL 18 and pin every CI job to Node 26.3.0
so the dev shell and CI run the same toolchain versions.
Repair the API/WebDAV (hurl) suite, which had drifted from the backend:
- Migrate the removed `/api/folders/{id}/listing` endpoint to `/resources`
(cursor-paginated `{items:[{resource_type,resource}]}` shape) across the
batch-copy, grants, nested-group, and WebDAV NC tests + the dav_helpers
wipe routine.
- Stop photos_etag from uploading the dedup-tracked fixture so the dedup
blob-lifecycle test can own its content-addressed blob exclusively.
- dedup_create now asserts the idempotent same-content re-upload (201 +
existing file id) instead of the stale 409 expectation.
Generated coverage reports, nyc output and the e2e server runtime data dir
are gitignored rather than committed.
68 lines
1.9 KiB
YAML
68 lines
1.9 KiB
YAML
services:
|
|
postgres:
|
|
image: postgres:18.2-alpine3.23
|
|
restart: always
|
|
environment:
|
|
POSTGRES_USER: postgres
|
|
POSTGRES_PASSWORD: postgres
|
|
POSTGRES_DB: oxicloud
|
|
ports:
|
|
- "5432:5432"
|
|
networks:
|
|
- oxicloud
|
|
volumes:
|
|
- pg_data:/var/lib/postgresql/
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U postgres"]
|
|
interval: 5s
|
|
timeout: 5s
|
|
retries: 5
|
|
|
|
oxicloud:
|
|
image: diocrafts/oxicloud:latest
|
|
restart: always
|
|
environment:
|
|
# Return freed heap pages to the OS promptly. mimalloc retains them by
|
|
# default, so idle RSS clamps at the peak even after the in-memory caches
|
|
# expire; purging immediately makes RSS track the live working set
|
|
# (benchmarked: ~400 MB reclaimed on musl/aarch64) at no throughput cost.
|
|
# Also baked into the Dockerfile; set here so it applies to the prebuilt
|
|
# image too.
|
|
MIMALLOC_PURGE_DELAY: "0"
|
|
build:
|
|
context: .
|
|
dockerfile: Dockerfile
|
|
# Route `docker compose up --build` / `docker compose build` through the
|
|
# cache-mount builder so repeat local builds recompile only changed crates
|
|
# (true incremental). Compose v2 uses BuildKit by default, which the
|
|
# Dockerfile already requires. The image is functionally identical to the
|
|
# default `builder` stage CI uses; only the build path differs.
|
|
args:
|
|
BUILDER: builder-cache
|
|
BIN_DIR: /app/bin
|
|
ports:
|
|
- "8086:8086"
|
|
networks:
|
|
- oxicloud
|
|
depends_on:
|
|
postgres:
|
|
condition: service_healthy
|
|
env_file:
|
|
- .env
|
|
volumes:
|
|
- storage_data:/app/storage
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:8086/ready || exit 1"]
|
|
interval: 30s
|
|
timeout: 5s
|
|
start_period: 30s
|
|
retries: 3
|
|
|
|
networks:
|
|
oxicloud:
|
|
driver: bridge
|
|
|
|
volumes:
|
|
pg_data:
|
|
storage_data:
|